LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Wireplumber doesn't autostart since switching from HDD to SSD (https://www.linuxquestions.org/questions/slackware-14/wireplumber-doesnt-autostart-since-switching-from-hdd-to-ssd-4175735934/)

murdo 04-12-2024 03:55 AM
Wireplumber doesn't autostart since switching from HDD to SSD
 
I've been having a very odd issue recently, since I switched from an ageing HDD to an SSD -- wireplumber won't autostart any more.

I can still start it manually and it runs just as it used to, and both pipewire and pipewire-pulse autostart as usual, but for some reason it won't run on startup, even though it's still enabled in Session & Startup.

Anyone have any ideas? I'm pretty well stumped. As far as I'm aware, there were no updates to pipewire or wireplumber when it started failing. The only change I can think of to my system is the HDD to SSD switch.

ferrari 04-12-2024 10:39 PM
Have you tried starting it manually? Any errors?

This may be of insight...
https://rbn.im/pipewire-on-slackware...e-current.html

murdo 04-13-2024 04:16 AM
Yes, I can run it manually and it works fine. It does print some errors in the console output, but they don't seem to affect any functionality that I can tell.

Code:
W 10:03:53.374938        pw.context ../src/pipewire/context.c:354:pw_context_new: 0x1a91ec0: no modules loaded from context.modules
E 10:03:53.444338          spa.alsa ../spa/plugins/alsa/acp/alsa-mixer.c:1660:element_probe_volume: The decibel volume range for element 'PCM' (-7300 dB - -100 dB) has negative maximum. Disabling the decibel range.
E 10:03:53.444374          spa.alsa ../spa/plugins/alsa/acp/alsa-mixer.c:1660:element_probe_volume: The decibel volume range for element 'PCM' (-7300 dB - -100 dB) has negative maximum. Disabling the decibel range.
E 10:03:53.444395          spa.alsa ../spa/plugins/alsa/acp/alsa-mixer.c:1660:element_probe_volume: The decibel volume range for element 'PCM' (-7300 dB - -100 dB) has negative maximum. Disabling the decibel range.
E 10:03:53.444413          spa.alsa ../spa/plugins/alsa/acp/alsa-mixer.c:1660:element_probe_volume: The decibel volume range for element 'PCM' (-7300 dB - -100 dB) has negative maximum. Disabling the decibel range.
E 10:03:53.444428          spa.alsa ../spa/plugins/alsa/acp/alsa-mixer.c:1660:element_probe_volume: The decibel volume range for element 'PCM' (-7300 dB - -100 dB) has negative maximum. Disabling the decibel range.
E 10:03:53.610690          spa.alsa ../spa/plugins/alsa/acp/alsa-mixer.c:1660:element_probe_volume: The decibel volume range for element 'PCM' (-4000 dB - -500 dB) has negative maximum. Disabling the decibel range.
E 10:03:53.610723          spa.alsa ../spa/plugins/alsa/acp/alsa-mixer.c:1660:element_probe_volume: The decibel volume range for element 'PCM' (-4000 dB - -500 dB) has negative maximum. Disabling the decibel range.
E 10:03:53.610740          spa.alsa ../spa/plugins/alsa/acp/alsa-mixer.c:1660:element_probe_volume: The decibel volume range for element 'PCM' (-4000 dB - -500 dB) has negative maximum. Disabling the decibel range.
E 10:03:53.610756          spa.alsa ../spa/plugins/alsa/acp/alsa-mixer.c:1660:element_probe_volume: The decibel volume range for element 'PCM' (-4000 dB - -500 dB) has negative maximum. Disabling the decibel range.
E 10:03:53.610770          spa.alsa ../spa/plugins/alsa/acp/alsa-mixer.c:1660:element_probe_volume: The decibel volume range for element 'PCM' (-4000 dB - -500 dB) has negative maximum. Disabling the decibel range.
E 10:03:54.371377        spa.bluez5 ../spa/plugins/bluez5/bluez5-dbus.c:5332:get_managed_objects_reply: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner
N 10:03:54.377607          wp-device ../lib/wp/device.c:619:wp_spa_device_new_from_spa_factory: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
N 10:03:54.377621 s-monitors-libcame enumerate-device.lua:30:chunk: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.

ferrari 04-13-2024 04:57 AM
Speculating here - maybe wireplumber is started before pipewire is active, and a small delay is required. ( The move to the SSD might have inadvertently caused this “timing“ issue to arise.)

ferrari 04-13-2024 05:02 AM
FWIW, here’s a similar Gentoo thread regarding pipewire and wireplumber startup timing….
https://bugs.gentoo.org/822498

murdo 04-14-2024 03:54 AM
So, oddly there were two pipewire.desktop's in my local autostart -- one with an uppercase P and one with a lowercase. I'm not sure whether it was removing the former or changing the wireplumber.desktop command from just "/usr/bin/wireplumber" to "/usr/bin/daemon -rB --pidfiles=~/.run --name=wireplumber /usr/bin/wireplumber" that fixed things, but it seems to be working now. We'll see, maybe it's a fluke and I'll boot up the next day and it'll be back to not working. Either way, thanks for the help!


All times are GMT -5. The time now is 11:08 PM.