this post was submitted on 08 Apr 2025
36 points (95.0% liked)
Linux
53126 readers
904 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah I wrote that stop command wrong, it's supposed to be
systemctl --user stop pulseaudio. The relevant errors from journalctl were the "busy" errors. Are they still there? Maybe they're old messages? You can type G to go to the end of the log.Also, and this is probably my last suggestion, try restarting the socket with
systemctl --user restart pipewire-pulse.socket. And maybe restart all the other crap as well for good measure. My theory here is that pulseaudio overwrote that socket with it's own socket, and anything trying to play sound would be trying to connect to the nonexistent pulseaudio, and maybe restarting pipewire doesn't actually recreate the socket, because systemd does that, but I'm not sure that's actually how that works.Theoretically logging out and in again should also restart all the things pipewire I think, but it's possible that whatever is slowing down your boot is actually slowing down the login, so do at your own risk.
Ok, so a lot of them are old messages, none of the messages from this session are labeled as busy. I did just try logging out and back in and that was pretty much instantaneous, so whatever it was that caused my computer to boot slowly just effect the boot itself. But yeah, I tried restarting pipewire and everything related to it and it's still just showing the dummy output device and audio isn't working. Thanks for trying though.
If we assume, for a moment, that your issue was in fact related to fluidsynth, which I kinda still think it might be, because of what fuser and the logs showed, it would be a good idea to undo your module blacklist thingy and reboot.
If your slow boot issue persists, and you try to fix that tomorrow, then try looking at the bootup messages as described here:
https://askubuntu.com/questions/25022/how-to-enable-boot-messages-to-be-printed-on-screen-during-boot-up
If you reinstall pulseaudio to get back to where you were before, uninstall pipewire, those two shouldn't be running simultaneously.
Good luck and keep me updated if you manage to fix it somehow.
Ok, even though I said I'd wait until tomorrow, I decided to try it again. It seemed to boot more or less normally but I did try someone else's suggestion and it got audio working again. I did undo the edit I made to the modprobe blacklist and I did keep fluidsynth and pulseaudio uninstalled but I tried using the wireplumber ppa, like someone else suggested and my audio is working again. Granded, I have no idea what actually fixed the issue, so I don't know who to fully credit but thanks for helping.
Glad you got it working.