I've never used the --user flag to reset/restart a service.
Have you tried systemctl reset-failed ?
And then systemctl daemon-reload or daemon-reexec
this post was submitted on 15 Jan 2025
12 points (100.0% liked)
Linux
8732 readers
180 users here now
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
founded 2 years ago
MODERATORS
No I have not tried that, though pw-top still worked, in general pipewire still worked, I just didn't get any sound anymore....
The --user flag commands come from this reddit thread: https://www.reddit.com/r/pop_os/comments/v3g2w9/is_there_a_cli_command_to_restart_pipewire/
Maybe try without the flag.
You can see what errors may have caused the issue by checking systemctl status NAMEOFSERVICE.service
or
journalctl -xem -o with-unit -p1 -p2 -p3 | grep -i pipewire
That may additionally help you diagnose the cause.
Since they are started with the user session these services do only exist there. If you try to restart them without the flag they just don't exist.
The journal would be a nice way to look for sure, but the command you posted throws an error for me:
Using --boot or --list-boots with --merge is not supported.
weird. Just change -xem to -xeb
You can also do -xe --since yesterday
The reset-failed should also work to reset any/all failed units/services so you don't have to go through one by one.
Fedora may be a bit different in the need for the --user flag, so try with/without.
But I've had an entire user scope crash and dump and recovered using it.
A small capture of the log (these errors were repeating multiple times):
Wed 2025-01-15 15:09:47 CET fedora [email protected]/pipewire.service[2482]: spa.alsa: set_hw_params: Protocol error Wed 2025-01-15 15:09:49 CET fedora [email protected]/pipewire.service[2482]: spa.alsa: 'front:3': capture open failed: The device or resource is busy/occupied Wed 2025-01-15 15:09:49 CET fedora [email protected]/pipewire.service[2482]: spa.alsa: 'front:3': capture open failed: The device or resource is busy/occupied Wed 2025-01-15 15:09:49 CET fedora [email protected]/pipewire.service[2482]: spa.audioadapter: params Spa:Enum:ParamId:EnumFormat: 1:0 (follower format) The device or resource is busy/occupied Wed 2025-01-15 15:09:49 CET fedora [email protected]/pipewire.service[2482]: pw.node: (alsa_output.usb-MOTU_M2_M2MT15188F-00.HiFi__Line1__sink-55) suspended -> error ((null)) Wed 2025-01-15 15:09:49 CET fedora [email protected]/pipewire.service[2482]: spa.alsa: 'front:3': capture open failed: The device or resource is busy/occupied Wed 2025-01-15 15:09:49 CET fedora [email protected]/pipewire.service[2482]: spa.alsa: 'front:3': capture open failed: The device or resource is busy/occupied Wed 2025-01-15 15:09:49 CET fedora [email protected]/pipewire.service[2482]: spa.audioadapter: params Spa:Enum:ParamId:EnumFormat: 1:0 (follower format) The device or resource is busy/occupied Wed 2025-01-15 15:09:49 CET fedora [email protected]/pipewire.service[2482]: spa.alsa: set_hw_params: Protocol error Wed 2025-01-15 15:09:50 CET fedora [email protected]/pipewire.service[2482]: spa.alsa: set_hw_params: Protocol error Wed 2025-01-15 15:09:50 CET fedora [email protected]/pipewire.service[2482]: pw.node: (alsa_input.usb-046d_Logitech_Webcam_C925e_AE792FAF-02.analog-stereo-60) suspended -> error ((null)) Wed 2025-01-15 15:09:50 CET fedora [email protected]/pipewire.service[2482]: spa.alsa: 'front:3': capture open failed: The device or resource is busy/occupied Wed 2025-01-15 15:09:50 CET fedora [email protected]/pipewire.service[2482]: spa.alsa: 'front:3': capture open failed: The device or resource is busy/occupied Wed 2025-01-15 15:09:50 CET fedora [email protected]/pipewire.service[2482]: spa.audioadapter: params Spa:Enum:ParamId:EnumFormat: 1:0 (follower format) The device or resource is busy/occupied Wed 2025-01-15 15:09:50 CET fedora [email protected]/pipewire.service[2482]: spa.alsa: set_hw_params: Protocol error
I translated the error messages, because they were in German.
I think the most important line might be this one as this is the audio device I am actually using:
Wed 2025-01-15 15:09:49 CET fedora [email protected]/pipewire.service[2482]: pw.node: (alsa_output.usb-MOTU_M2_M2MT15188F-00.HiFi__Line1__sink-55) suspended -> error ((null))
I don't know if I can resolve this, but I've done some reading and the m2/m4 have some known issues with Linux.
Some patches and configs and instructions are here:
https://github.com/kiosion/alsa-motu-m2
Aside from that, there could be another application that is locking the card which is why you're getting the resource busy error.
As mentioned here:
And some more issues/troubleshooting specifically with the m4:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3312
I will look into that, thanks for your help, time and effort ❤️