On Saturday, 26 March 2022 17:14:52 GMT Mark Knecht wrote: > On Sat, Mar 26, 2022 at 10:02 AM Peter Humphrey <pe...@prh.myzen.co.uk> wrote: > > On Saturday, 26 March 2022 15:14:11 GMT ny6p01 wrote: > > > Just a shot in the dark, but is alsasound service starting correctly? > > > > It doesn't run at all, not even while I'm listening after restarting PA. I > > have alsa-lib, alsa-topology-conf, alsa-ucm-conf and alsa-plugins > > installed, but 'ps -ax | grep alsa' finds nothing. Also, I have no > > alsasound service. > > > > I assume that PA doesn't need a running alsa process to function. > > > > -- > > Regards, > > Peter. > > PA might not (or doesn't - my system has no alsa processes) need alsa > processes but it almost certainly using Alsa drivers. > > lsmod | grep snd > lsmod | sound > > However those depend on what you build as modules vs hard code into > your kernel. > > ls /proc/asound would give you a view into what function, if any, alsa is > performing.
I think since this sound problem has been narrowed down to a difference between users on the same machine, it must be a userspace process issue. Kernel driver problems would be universal and dmesg would complain about it. If the same ~./mozilla profile is reproducing the problem on the other user's account, which hitherto played sound without any desktop gymnastics, then the problem is firefox related. Starting with an empty firefox profile on the same user will also help identify if the firefox configuration, addons and its sandboxing, or pa is to blame. Starting both firefox and pa from a terminal may also provide some related output.
signature.asc
Description: This is a digitally signed message part.
