I will look into that, thanks for your help, time and effort ❤️
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 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/
The site is not yet in operation. That has nothing to do with outsourcing… Its maybe bad supervision, but honestly most manufacturers fall in that category
I think the destinction between the chinese firm constructing the site and BYD itself is quite important here. I am absolutely not a fan of chinese car manufacturers but its just not the same as if BYD was operating the site right now and this news came to light
very nice. I will give it a try as well (after the holidays though)
I don’t really understand the readme. Is the creation done in a cli or in the jellyfin UI?
I was missing this feature in jellyfin and this would be really great (I switched from plex which has it and I used it a lot 😅)
I had the exact same problem and the solution was to ask my ISP who then either just gave me a public IP (Vodafone) or asked for money so my network could be reached from the outside (Primerocom). So check whether there is an option with you ISP to get a “public” IP.
I did my part 😇
@echo_pbreyer@digitalcourage.social MEP for @piratenpartei@piratenpartei.social and the European Pirate Party: https://digitalcourage.social/@echo_pbreyer/112636245969803768
You should be using bcrypt or something similiarly designed to hash passwords, since they are much safer than sha256/512. Sha is not designed for hashing passwords and therefore a fast algorithm which you shouldn’t use for passwords
I decided to upgrade, and so far everything is working fine. I had some hiccups after the installation, but a reboot fixed all of them. Thanks for your input :)
Nice though. Sounds like I can do the upgrade 😁
very nice
nvidia RTX 2070 super. But that was from 38 to 39. I am not on 40 yet
That doesn’t sound promising, though I am using Gnome, so at least my DE is not getting the biggest upgrade :)
Are you using KDE or Gnome?
I definitely don’t want to deal with that. Last time that happened I had to do a clean install which is just pain imo XD
So these are the log messages right after the device failed:
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…