Pankaj Jangid <
pan...@codeisgreat.org> writes:
> I have upgraded to Bookworm two weeks ago. Everything is working
> perfectly fine, except just one glitch. I have to restart pipewire and
> pipewire-pulse service everytime I reboot. Here is what is happening.
>
> I have just booted my system and the systemctl reports few errors in
> pipewire. Although it is saying pipewire is started. Here is the output,
>
> And GNOME settings also showing "Dummy Output" virtual device in the
> settings.
>
> After restarting once or sometimes twice, internal USB Audio and other
> HDMI Audio devices appear in the GNOME settings. And sound starts
> working fine with those attachments. systemctl also reports no errors
> after restart.
>
> $ systemctl --user status pipewire pipewire-pulse
> ● pipewire.service - PipeWire Multimedia Service
> Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
> Active: active (running) since Mon 2023-04-24 09:10:04 IST; 38s ago
> TriggeredBy: ● pipewire.socket
> Main PID: 6769 (pipewire)
> Tasks: 2 (limit: 76963)
> Memory: 5.1M
> CPU: 16ms
> CGroup: /user.slice/user-1000.slice/us...@1000.service/session.slice/pipewire.service
> └─6769 /usr/bin/pipewire
>
> Apr 24 09:10:04 anant systemd[1009]: Started pipewire.service - PipeWire Multimedia Service.
>
> ● pipewire-pulse.service - PipeWire PulseAudio
> Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: enabled)
> Active: active (running) since Mon 2023-04-24 09:10:04 IST; 38s ago
> TriggeredBy: ● pipewire-pulse.socket
> Main PID: 6776 (pipewire-pulse)
> Tasks: 2 (limit: 76963)
> Memory: 2.8M
> CPU: 11ms
> CGroup: /user.slice/user-1000.slice/us...@1000.service/session.slice/pipewire-pulse.service
> └─6776 /usr/bin/pipewire-pulse
>
> Apr 24 09:10:04 anant systemd[1009]: Started pipewire-pulse.service - PipeWire PulseAudio.
>
> This used to work fine with Debian 11.6 (which had pulseaudio as
> default). How can I fix this issue so that I don't have to restart
> pipewire and pipewire-pulse daemon everytime?
Wanted to add I'm experiencing the same issue. I thought it was because
I was using Chrome remote desktop but looks like it may affect all types
of logins.
--
Manphiz