You are not logged in.
Hi!
Recently, my audio broke. I realized that I must mute and unmute (with e.g. `wpctl`) after each reboot, even tough they (sound and microphone) appears in `wpctl status` as unmuted from the start.
Things got worse, because a few days ago it started defaulting to hdmi instead of speakers despite the hdmi not being plugged in. I can resolve that with `pactl` to set default source and sink. However the issue with sound not being captured / outputted after each system startup remains.
For the record, when I plug in an HDMI cable the Pipewire switch back to the speakers but all the time I still need to mute and unmute audio to restore the sound.
Could you suggest anything?
Last edited by kibi (2024-07-15 10:20:25)
Offline
Same things happens to me on both my computers since last Pipewire updates
Offline
Work around for muted sound arch linux
open file explorer
go into /usr/bin right click on empty space and select “open as administrator”
then highlight “create new” and click on “empty file” and name it "automute"
once created open it. It will ask you to select a program to open it with.. I used kwrite
but you can use whatever text editor will let you do it.
Paste the following and yes paste that one line twice.. it has a purpose.
#!/bin/bash
pactl set-sink-mute 0 toggle
pactl set-sink-mute 0 toggle
save and close the file. Right click on it and go to “permissions tab” and put a checkmark
in “is executable” and hit ok.
Now open settings app, scroll to bottom and click on “autostart” then at top right corner click
“+ add” and click “+add login script” then navigate to the file you just made in /usr/bin/
called automute and open it. Click the white little square box now to the right of the entry you
just made. (when you hover over it with mouse it will say “see properties” click it. Then click on
“permissions” tab and make sure “is executable” is checked. Then go to “applications” tab and on
the bottom click on “advanced options” put a check mark in “run in terminal” and hit ok. Reboot and you should be all fixed up.
This took me a saturday to figure out as im a newb. It works for me. It’s a work around not a fix but you wont have to do anything after starting up. I tried to write this from the perspective of a newb and not skip anything.
im sure i probably have extra steps in here or will make veteran linux users scratch their head but hey it worked for me. lol. again.. linux newb here. Good luck.
Last edited by methadus (2024-07-27 19:49:09)
Offline
Same things happens to me on both my computers since last Pipewire updates
Temporary workaround
systemctl --user stop wireplumber.service
rm -r ~/.local/state/wireplumber # these deletes your settings
systemctl --user start wireplumber.serviceIf this fixes it (needs maybe done after every boot/reboot) please report here. Or at least here.
I know that reporting bugs has become a little bit bigger hurdle with the new accounts, manual registration and 2FA ![]()
Offline
superjcvd wrote:Same things happens to me on both my computers since last Pipewire updates
Temporary workaround
systemctl --user stop wireplumber.service rm -r ~/.local/state/wireplumber # these deletes your settings systemctl --user start wireplumber.serviceIf this fixes it (needs maybe done after every boot/reboot) please report here. Or at least here.
I know that reporting bugs has become a little bit bigger hurdle with the new accounts, manual registration and 2FA
Hi!
Thank you! It helped me. Also, when I reboot, my output and microphone are unmuted. Here’s what I did:
1. Unmute Output and Microphone
2. Run:
systemctl --user stop wireplumber.service
rm -r ~/.local/state/wireplumber # these deletes your settings
systemctl --user start wireplumber.serviceLast edited by mmarusyk (2024-09-06 21:10:21)
Offline
I was having the same issue after the update, so annoying! the systemctl fix helped me too, but I still had to mute/unmute after every reboot. that script @methadus posted is worth a shot if you're still having trouble—especially if you're dealing with any web api configurations that might be affected
Last edited by ragemanners (2024-09-12 07:18:15)
Offline
It looks like this is an upstream issue; I experience the same problem on Debian Testing.
Offline