No sound from pipewire until I restart pipewire

[martijntje]

I'm running Debian Bookworm, which I've setup to use pipewire as per the instructions on the wiki. It was running great for quite a while. Now, however, all of a sudden it's entirely silent after every boot, until I restart pipewire.

I can find no indication anywhere of any kind of error. If I open gnome settings and go to sound, I can see the little indicators under the device light up if I play a sound (which I won't hear).

Pipewire appears to be running:

Code: Select all

● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
     Active: active (running) since Fri 2024-07-12 20:18:20 CEST; 5min ago
TriggeredBy: ● pipewire.socket
   Main PID: 1939 (pipewire)
      Tasks: 3 (limit: 18414)
     Memory: 9.4M
        CPU: 2.006s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─1939 /usr/bin/pipewire

jul 12 20:18:20 vivobook systemd[1908]: Started pipewire.service - PipeWire Multimedia Service.

When I execute a single

Code: Select all

systemctl --user restart pipewire.service

, my audio works again until the next boot. I'm a bit flummoxed as to how I can debug it, or what it can be. In case it's relevant: I'm running this on an asus vivobook 14 flip, with the following audio controller:

Code: Select all

Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller

Any idea what I can do about this?

[Augie77]

Added anything new to Application Autostart that may interfere with sound? Something like a VoIP or Discord, etc.

[martijntje]

Not to my knowledge, no. The last thing I installed was firefox-nightly, and that was some months back. Then it was still working. I've not added any services or anything that auto starts AFAIK.

[martijntje]

Hmm, I just discovered that if I mute and then unmute my sound, it also starts working. So maybe somehow the hardware is in some muted state, while pipewire thinks it's not. Then muting it and unmuting it fixes it.

Just changing the volume without going to zero has no effect.

[shubhisroking]

Hmm, I just discovered that if I mute and then unmute my sound, it also starts working. So maybe somehow the hardware is in some muted state, while pipewire thinks it's not. Then muting it and unmuting it fixes it.

Just changing the volume without going to zero has no effect.

you found any fix?

[martijntje]

you found any fix?

Unfortunately, no. I'm currently on vacation. When I get back I'll see if it works when I boot from a live cd.

[martijntje]

For some reason it suddenly started working again. I believe it has something to do with the initial volume upon boot. When the machine starts, but before I log in, it's now muted, then when I login it's restored to the volume I had set before turning the machine off.

I think this causes it to be muted upon boot, which somehow makes it work. I'm not sure if it was like that before or not and I have no way of testing this.