[SOLVED] Pipewire .config/pulse conflict

[amc252]

Hello everybody,

I have made the switch from pulseaudio to pipewire and also installed pipewire-pulse.
Now something odd happens.
Sometimes, but not always, when I startup the system, a .config/pulse folder is created and then every audio app (browser or mpv etc) gets stuck.
If I remove the .config/pulse folder , logout and login, the problem is solved, although the same folder is created again.

I use JWM and start pipewire with the following commands:

Code: Select all

   <StartupCommand>pipewire</StartupCommand>
   <StartupCommand>wireplumber</StartupCommand>
   <StartupCommand>pipewire-pulse</StartupCommand>   

I also tried to add:

Code: Select all

   <StartupCommand>rm -rf /home/mac/.config/pulse</StartupCommand>

but the problem subsists.

Any suggestion as to what I am missing?

[Axel-Erfurt]

If you have installed pipewire, you don't need to start with any commands. It starts automatically.
And it does not create a folder .config/pulse

[amc252]

If you have installed pipewire, you don't need to start with any commands. It starts automatically.
And it does not create a folder .config/pulse

On my system (devuan) pipewire does not seem to start automatically.
I disabled the startup commands and there's no sound at all.
If I start pipewire and wireplumber manually, still no sound. Then, if I try to launch alsamixer, I get:

Code: Select all

$ alsamixer
cannot open mixer: Host is down

EDIT:

I might have found the problem.
I saw a devuan specific post where it was indicated that, athouugh pipewire needs to be started somehow (.xsessionrc, .bash, etc) the order should be:
wireplumber
pipewire
pipewire-pulse

I changed the order in my startup commands and it seems to work.