[SOLVED] Wireplumber doesn't autostart since switching from HDD to SSD
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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.)
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!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
