1 |
On Wed, Mar 23, 2022 at 10:20 AM Mark Knecht <markknecht@×××××.com> wrote: |
2 |
> |
3 |
> On Wed, Mar 23, 2022 at 10:15 AM Peter Humphrey <peter@××××××××××××.uk> wrote: |
4 |
> > |
5 |
> <SNIP> |
6 |
> > The machine is ~amd64 running Plasma. I log in via SDDM, but even if, instead, |
7 |
> > I log in first and then startx I still get no sound. I haven't touched ALSA; |
8 |
> > it's whatever Plasma wanted to support its audio process. |
9 |
> > |
10 |
> |
11 |
> So by 'Plasma' you imply KDE to me. Am I correct in that? |
12 |
> |
13 |
> > What floors me is that two users on the same machine get different results. |
14 |
> > |
15 |
> |
16 |
> Agreed but if it's KDE then generally that implies pulseaudio and users can have |
17 |
> different configurations. Assuming generalized KDE for the moment, then |
18 |
> |
19 |
> System Settings -> Audio |
20 |
> |
21 |
> should show your playback devices. Possibly the setting got switched to |
22 |
> an HDMI output on your video card or to the chipset sound device |
23 |
> and isn't USB at the moment? |
24 |
> |
25 |
> HTH, |
26 |
> Mark |
27 |
|
28 |
Also, assuming it's KDE then also run pavucontrol-qt (or whatever it's |
29 |
called on your system) to ensure you see the application generating |
30 |
audio is actually doing what you think it is - there's an app-by-app |
31 |
set of VU meters showing where KDE is sending audio in terms of |
32 |
which hardware output. |
33 |
|
34 |
I.e. - KDE can send audio from different apps to one or more |
35 |
hardware devices at the same time. pavucontrol should allow |
36 |
you to see how this is happening at any time. I have it in my |
37 |
favorites. |
38 |
|
39 |
Good luck, |
40 |
Mark |