

I second that :D
Beruflich Web-Entwickler, privat ein Ober Nerd und Links-Grün versifft…
Musik Liebhaber, von #kpop bis #metal alles dabei
Ansonsten bin ich auch gerne mit der Kamera unterwegs.
Entwickler und Maintainer für #mbin
ich bin auch auf mastodon: @BentiGorlich
Ich betreibe thebrainbin.org, gehirneimer.de und wehavecookies.social
I second that :D
So these are the log messages right after the device failed:
Jan 21 11:20:41 fedora pipewire[2460]: spa.alsa: set_hw_params: Protokollfehler Jan 21 11:20:41 fedora pipewire[2460]: pw.link: 0x55db4830afa0: one of the nodes is in error out:error in:suspended Jan 21 11:20:41 fedora pipewire[2460]: pw.link: 0x55db485f9360: one of the nodes is in error out:error in:suspended Jan 21 11:20:44 fedora pipewire[2460]: spa.alsa: set_hw_params: Protokollfehler Jan 21 11:20:44 fedora pipewire[2460]: spa.alsa: set_hw_params: Protokollfehler Jan 21 11:20:44 fedora pipewire[2460]: spa.alsa: set_hw_params: Protokollfehler Jan 21 11:20:44 fedora pipewire[2460]: pw.link: 0x55db48355240: one of the nodes is in error out:suspended in:error Jan 21 11:20:44 fedora pipewire[2460]: pw.node: (alsa_output.usb-MOTU_M2_M2MT15188F-00.Direct__Direct__sink-56) suspended -> error ((null)) Jan 21 11:20:44 fedora pipewire[2460]: pw.link: 0x55db482bdca0: one of the nodes is in error out:idle in:error Jan 21 11:20:44 fedora pipewire[2460]: pw.link: 0x55db47b39140: one of the nodes is in error out:idle in:error
I have no idea how to unsuspend the device after it errored, nor do I know why it errored. Like I said in the OP I’ve tried turning it off and on again, but the only solution I have found is to reboot which sucks… I changed the sampling rate from 41k to 48k but that didn’t change anything. I have no idea how to change the bit depth of the device though. I applied the fixes from the repo you linked, but I am not able to install the version of alsa they referenced in there. Fedore 41 only comes with the 2 most recent versions it seems…
I will look into that, thanks for your help, time and effort ❤️
A small capture of the log (these errors were repeating multiple times):
Wed 2025-01-15 15:09:47 CET fedora user@1000.service/pipewire.service[2482]: spa.alsa: set_hw_params: Protocol error Wed 2025-01-15 15:09:49 CET fedora user@1000.service/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 user@1000.service/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 user@1000.service/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 user@1000.service/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 user@1000.service/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 user@1000.service/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 user@1000.service/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 user@1000.service/pipewire.service[2482]: spa.alsa: set_hw_params: Protocol error Wed 2025-01-15 15:09:50 CET fedora user@1000.service/pipewire.service[2482]: spa.alsa: set_hw_params: Protocol error Wed 2025-01-15 15:09:50 CET fedora user@1000.service/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 user@1000.service/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 user@1000.service/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 user@1000.service/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 user@1000.service/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 user@1000.service/pipewire.service[2482]: pw.node: (alsa_output.usb-MOTU_M2_M2MT15188F-00.HiFi__Line1__sink-55) suspended -> error ((null))
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.
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/
Nope Interstellar is still solo
We also have a magazine dedicated to release information with a more detailed changelog: !mbinReleases@gehirneimer.de For the latest release: https://gehirneimer.de/m/mbinReleases/t/451780
you can use https://browser.pub/ I like it very much for that use case :)
Yeah that meant only that we have two different “tabs” or “areas” for the thread side (lemmy) and the microblog side (mastodon)
Hi there mbin dev here. The interaction with mastodon is possible: you can follow people, you can see posts from people from mastodon (just in the “microblog” tab, not the “threads” tab), but it has not been the main focus since mbin was created and has therefore not made huge progress. We have plans to improve the microblog side of things (or at least I have), but there were just so many behind the scene problems with the code that needed fixing (and still need improvements) so we focused more on that.
I will not promise anything, but I want to have threads and microblogs in the same list and I am thinking of adding a “timeline” tab that works more like the microblog style that people know. However development has not started on that, yet and we therefore do not have a release with which this is expected or even an ETA.
I am literally not interested in any of them 😂
Its higher voltage,but yes It does. However the higher standards take care of that, so you don’t have too weak power cables available
I strongly disagree… We just have higher standards regarding power wires. Since we have more voltage running through the wires we need tougher ones, but that is what regulation is for
I mean it is hard to find out if they are the exact same, since power strips often don’t specify it, but from handling both I’d say they are pretty much the same…
do you know of an actual instance of it? gush.social isn’t one as far as I can tell :D
I think it is partly a US specific problem as the quality of the extension cords really suck. Meanwhile in Eurpoe (or at least in Germany) the extension cords actually use the same wire grade as your in wall wires, so there is a basically no difference in using daisy chained extension cords versus different wall outlets (as long as the outlets are in the same curcuit)
Yeah it seems very chinese focused. Some views like when you try to mark a movie as watched have a lot of chinese in it.
very nice
More than once 🙈