From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE Plasma sound not working
Date: Wed, 15 Jun 2022 18:29:52 +0100 [thread overview]
Message-ID: <2987222.CbtlEUcBR6@lenovo.localdomain> (raw)
In-Reply-To: <3d342c8a-c8d0-7723-6a8b-221350510c1f@jroy.ca>
[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]
On Wednesday, 15 June 2022 17:29:54 BST Julien Roy wrote:
> On 6/15/22 06:52, Peter Humphrey wrote:
> > I do something like that by copying a good user account as a basis for the
> > next iteration. The problem is just the fineness of granularity that's
> > needed, now that a coarse grain hasn't helped. Hey-ho. Here we must go
> > again...
> What is certain is that the issue is caused by a file in your home
> directory, since creating a new user fixes the problem.
>
> What may help you to be more specific with this would be to list what
> files were modified since the last time audio worked; for example, `find
> $HOME -mtime 0` will show files modified in the last 24 hours
>
> You might want to run this command on .config or .kde directories to see
> what could have changed, although it's true that it might take a while
> to pin point it...
>
> Another option, since you mention that you re-created your user multiple
> times, is to just delete specific folders, reboot, and try audio. Maybe
> start with .config as that would be the most obvious culprit. If that
> doesn't work, try .kde (not sure if that folder is in ~/ or ~/.config),
> then other directories.
>
> Also, did you check `dmesg` to see if there are any errors related to
> the audio device/driver? Try `dmesg --level=err,warn`
>
>
> Regards,
>
> Julien
I can't recall if among various things Peter has tried is to boot and login
into Plasma, without the USB audio dongle plugged in. Then plug it in and
check dmesg and syslog, as well as udevadm:
udevadm monitor --subsystem-match=usb --property
Also, if there is some specific audio driver module used with this dongle, try
compiling it as a module and modprobe it manually.
Hopefully, checking differences between the working and non-working user
profiles before/after a reboot will elicit something meaningful.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-15 17:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 2:00 [gentoo-user] KDE Plasma sound not working Peter Humphrey
2022-06-15 2:21 ` Julien Roy
2022-06-15 10:52 ` Peter Humphrey
2022-06-15 16:29 ` Julien Roy
2022-06-15 17:29 ` Michael [this message]
2022-06-16 16:10 ` Peter Humphrey
2022-06-16 16:20 ` Peter Humphrey
2022-06-17 1:28 ` Julien Roy
2022-06-17 6:35 ` Peter Humphrey
2022-06-17 8:55 ` Michael
2022-06-17 11:19 ` Peter Humphrey
2022-06-17 14:27 ` Michael
2022-06-17 14:51 ` Anna “CyberTailor”
2022-06-18 11:53 ` Peter Humphrey
2022-06-18 12:30 ` Julien Roy
2022-06-18 13:51 ` Peter Humphrey
2022-06-15 2:50 ` Julien Roy
2022-06-15 17:42 ` Michael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2987222.CbtlEUcBR6@lenovo.localdomain \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox