Volume level drops back to default level when logging out of desktop [Solved]

[siamhie]

@BitterTruth
I don't have xscreensaver installed. Plus, if I had two user accounts on this computer, both would have their volume level reset back to 40 when they log back in from the display manager.


When I log back in I check both Alsamixer and Pulse Volume Control (located in the Multimedia category of fluxbox) and they both report 40 instead of 70.
I then just open PVC from the menu (I've remove the volume icon from the tint2 toolbar) and set it back to my preferred level.

*edited for spelling

[siamhie]

@siamhie , @dolphin_oracle , @CharlesV

Pipewire doesn't use the audio group. It has it's own 'pipewire' group instead. I think alsa-utils sets the audio group membership. How about making yourself part of that group and see if that helps (instead of audio).

alsa-utils is not a group

groups.png

[BitterTruth]

Did you try adding yourself to the pipewire group so that when your applications run and start pipewire, they have permission to access the audio devices?

The 2nd user would be root. It's possible that wireplumber is defaulting to roots volume config settings when you login.

There's a possibility that Bluetooth might be causing a problem with pipewire and wireplumber when you are logging out. You could try disabling that in autostart if you have it enabled.

With xcsreensaver installed you wouldn't need to log out. Just lock your screen.

[BitterTruth]

@siamhe

"alsa-utils is not a group"

I should have been more clearer: alsa-utils added you to the audio group. The audio group has permissions to access the audio devices (microphone etc)

In a perfect world, the user shouldn't need to add themselves to the audio group. The applications, policy should take care of that i.e. they should be able to use them without elevated privileges. But in real life sometimes people who don't have any sound at allfind that they have to add themselves to it.

Pipewire didn't use the audio group. It has its own called pipewire through which it accesses the devices on your behalf. You can try adding yourself to this group.

Just document everything you do, so that it is ready to reverse

[siamhie]

@dolphin_oracle

I installed Gnome 43.6 along side of MX-23 XFCE and it made no difference when I switched to it. Volume dropped to default of 40 (Starship/Matisse HD Audio Controller)

[anticapitalista]

try installing alsa-ucm-conf

[siamhie]

try installing alsa-ucm-conf

@anticapitalista
Already installed

alsa-ucm-conf.png

[dolphin_oracle]

@dolphin_oracle

I installed Gnome 43.6 along side of MX-23 XFCE and it made no difference when I switched to it. Volume dropped to default of 40 (Starship/Matisse HD Audio Controller)

yes, you've already discovered the probably solution of removing the user from the audio group. I do believe something is happening at logout when running systemd that is setting the alsa sound level to 40%, removing the user from the audio group prevents that, but we've had it that way for a long time without an ill effect. If that supposition is true, then likely having pulseaudio installed would do the ame.

I'm running that way at the moment to see if anything negative crops up over time.

[siamhie]

Did you try adding yourself to the pipewire group so that when your applications run and start pipewire, they have permission to access the audio devices?

Made no difference adding myself to the group. Pipewire, Pipewire-Pulse and Wireplumber all get started at boot time per the pipewire-start script with all three desktops.

The 2nd user would be root. It's possible that wireplumber is defaulting to roots volume config settings when you login.

No. All three *wire apps are running as my user.

wire.png

There's a possibility that Bluetooth might be causing a problem with pipewire and wireplumber when you are logging out. You could try disabling that in autostart if you have it enabled.

I've removed all traces of bluetooth when I initially installed the ISO as I have no need for it.

With xcsreensaver installed you wouldn't need to log out. Just lock your screen.

Doesn't help if I want to load a different desktop.

[siamhie]

yes, you've already discovered the probably solution of removing the user from the audio group. I do believe something is happening at logout when running systemd that is setting the alsa sound level to 40%, removing the user from the audio group prevents that, but we've had it that way for a long time without an ill effect. If that supposition is true, then likely having pulseaudio installed would do the ame.

I'm running that way at the moment to see if anything negative crops up over time.

@dolphin_oracle
I didn't see this minor issue when using pulseaudio with MX-21 and multiple desktops with systemd. Volume always stayed at my set level when switching back and forth.

I downloaded the Debian 12.1 XFCE live ISO to see how they may have had pipewire setup but they were using pulseaudio.
I think I'll download Debian 12.1 Gnome next and check it out. There's got to be a simple explanation somewhere.


@MadMax has put together a guide to revert back to pulseaudio for those who are interested.

MX 23 Going back to pulseaudio (step-by-step tutorial) viewtopic.php?t=76405