View previous topic :: View next topic |
Author |
Message |
HuskyDog Tux's lil' helper
Joined: 20 Feb 2003 Posts: 77 Location: Wiltshire, UK
|
Posted: Fri Jan 05, 2024 11:38 pm Post subject: [Solved] Selecting Pipewire Pro Audio kills sound in Plasma |
|
|
I am running Plasma desktop with Pipewire on a Raspberry Pi 5
I have two user accounts on my machine (neither of them is root) which both wish to use the audio system (but not simultaneously). If I log in as user "A" then everything works just fine. I can play multimedia files in - for example - VLC and the sound comes out of the speakers via HDMI correctly.
However, if I log out at user "A" and then log in as user "B" then there is no sound at all! Further more, there aren't even any sound devices! The "Audio Volume" widget on the task bar is crossed through and hovering over it produces a message which reads "No output or input devices found". If I select "Configure Audio Devices" then I get the "Audio - System Settings" dialogue which is basically completely blank. There is a "Show Inactive Devices" button, but this just causes the Dummy playback device to appear.
If I log out of user "B" and back into user "A" and also open "Audio - System Settings" then I can see my "HDMI / DisplayPort" device listed under "Playback Devices" with a volume control and "Test" button, both of which work. There is also an entry for "Inactive Cards" which shows "Built-in Audio" selected "Off".
As an experiment I created a new user "C" and logged in. As expected, sound worked correctly. I opened "Audio - System Settings" and observed that next to the HDMI playback device there was menu which allowed me to select "Off", "HDMI" or "Pro Audio". I selected "Pro Audio" and the entire HDMI playback device immediately disappeared together with the menu which might have allowed me to reverse the effect. I was then in basically the same none-working and apparently unrecoverable state as user "B".
Does anyone know how to reverse the disastrous effect of selecting "Pro Audio"? I imagine that I could delete all of the configuration for user "B", but that sounds a bit drastic! Yes, I have tried re-booting.
SOLUTION (sort of)
By experimenting with newly created users and watching what files changed with 'find' I deduced that the problem seemed to lie in ~/.local/state/wireplumber. If I logged out, deleted this folder and then logged back in again so that it was re-created with a default setting then the HDMI output re-appeared. It still seems to be to be a bug that selecting "Pro Audio" removes the menu which you used to select it so that you can't revert the setting, but for now I have working sound. |
|
Back to top |
|
|
flexibeast Guru
Joined: 04 Apr 2022 Posts: 324 Location: Naarm/Melbourne, Australia
|
Posted: Sun Jan 07, 2024 8:53 am Post subject: |
|
|
Off the top of my head, this sounds like the WirePlumber process(es) not being shut down when a user logs out, which they should be .... How are you logging in? Via a Display Manager, manually from the console, something else? |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6098 Location: Dallas area
|
Posted: Sun Jan 07, 2024 12:54 pm Post subject: |
|
|
are you sure that multiple instances of wireplumber aren't running (per user) _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
Pythagoras1 Guru
Joined: 29 Jul 2002 Posts: 352 Location: Burgas, Bulgaria
|
Posted: Thu Jan 25, 2024 5:36 pm Post subject: |
|
|
exactly the same happened to me right now on manjaro for raspberry pi 4. thanks for pointing to the solution!
i guess that can be reported to upstream
btw, the default-profile config file still listed both hdmi ports as set to "pro audio". the working configuration has no default-profile file at all. it could be sufficient to just remove the default-profile config.
Last edited by Pythagoras1 on Thu Jan 25, 2024 10:46 pm; edited 1 time in total |
|
Back to top |
|
|
szatox Advocate
Joined: 27 Aug 2013 Posts: 3139
|
Posted: Thu Jan 25, 2024 5:59 pm Post subject: |
|
|
Quote: | However, if I log out at user "A" and then log in as user "B" then there is no sound at all! F | Wireplumber in this scenario attempts to pick a different playback device for each user. What you're seeing is most likely controls for _not_the_device_you_expected_.
It can be forcefully overriden after starting audio subsystem, but your playback still needs a hardware mixer in order to produce sound for multiple users at the same time, which consumer devices generally don't.
The actual solution would involve getting a single, system-wide pipewire to accept all users instead of a buch of per-user instances. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|