Re: [gentoo-user] KDE Plasma sound not working
On Wednesday, 15 June 2022 03:00:16 BST Peter Humphrey wrote: > Something else also changes at the first reboot after creating a new user > account: a dialogue box opens requesting permission to mount a partition - > but that partition is one of several marked 'noauto' in fstab. (Screen shot > attached.) > > What can possibly live under /home/prh and cause all this disruption? I > might suspect I'd been hacked, but I've rebuilt a new system several times, > and I've lost count of the times I've thrown away my user account and > started again. As it has already been commented the udisks points to desktop automounting function doing its thing here. There a number of options to configure for all devices and selected devices. However, I can't recall this pop up on new user accounts here, but I do not run any nvme devices to know if it is any different. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] KDE Plasma sound not working
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. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] KDE Plasma sound not working
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
[SOLVED] Re: [gentoo-user] Sound control in Enlightenment
Dnia 2022-06-12, o godz. 21:04:17 Michael napisał(a): > On Sunday, 12 June 2022 17:13:46 BST w...@op.pl wrote: > > I have just reinstalled my Gentoo and discovered some unwanted > > change. Last time "Mixer" had the ability to: > > 1) choose which sound output to use when connected to my > > bluetooth speaker > > 2) set volume above 100% > > 3) every sound playing app could get configured separately > > from system master volume by app's title bar > > > > Now all those features are missing. I guess it's either some app not > > being installed or some USE flag not set. Another possibility is > > that last time I had ACCEPT_KEYWORDS="~amd64" which now I decided > > to drop. > > I'm on a stable arch, x11-wm/enlightenment-0.25.3 and > dev-libs/efl-1.26.2. With the pulseaudio USE flag not set I get no > sound through the laptop built in speaker. On another system which > has pulseaudio set for efl, I recall sound works, but I have not > tested it lately to confirm. I'll get to it within a week or so and > can check if sound works as it should/used to. > > > Any ideas if there is possibility to get those features back? > > > > -- > > xWK > > In the first instance check efl is compiled with USE="pulseaudio". Hello! I managed to solve it. Just had to rebuild Enlightenment so it can see newly-built EFL. Thanks a lot for help. -- xWK pgpw30F9C87BM.pgp Description: Podpis cyfrowy OpenPGP
Re: [gentoo-user] KDE Plasma sound not working
On Wednesday, 15 June 2022 03:21:51 BST Julien Roy wrote: > A few suggestions to pin point the source of your problem: Thanks for you help. > - Try with a different audio device to test if the issue is localized to > this USB dongle, or if it is "system wide", The evidence points squarely away from the hardware. I can't see this being anything other than a misconfiguration or a coding error. > - Install a different DE (or perhaps a WM would be faster), to see > whether this is KDE-related, or system wide, I may do that. > - Take a copy/backup/snapshot of your new user account before the issue > occurs, and compare it (specifically the config files) to the account > after the issue appears. This may help you find out if KDE is doing > something fishy with a config file somewhere that triggers the problem. > Alternatively, you could also revert to the snapshot and see if that > fixes the problem. If so, then you might want to take more granular > snapshots (specific folders or files), and restore specific folders as > the issue appears, to figure out where exactly the problem is located. 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... > As for the drive that wants to mount itself, I don't think it is related > to this audio problem, but KDE (and DEs in general) have settings to > allow mounting devices (automatically) through the DE itself rather than > fstab, which explains why the noauto setting is being ignored : check > the settings in KDE to see if it's setup to auto mount devices. Setting all devices to no-automount hasn't helped. -- Regards, Peter.
