💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › kisslinux-2024-03-08.txt captured on 2024-05-26 at 15:55:00.
⬅️ Previous capture (2024-03-21)
-=-=-=-=-=-=-
[2024-03-08T00:53:03Z] <riteo> no there's something fishier going on... I'm absolutely baffled on why it stopped working all of a sudden, I've been debugging this shit for the whole day [2024-03-08T06:34:13Z] <sewn> ehawkvu: what is the c in echawk in your github name mean? [2024-03-08T07:09:06Z] <riteo> aight folks, I cracked the secret: the latest pipewire package at version 1.0.3+0.4.82 is broken. 1.0.0+0.4.16-1 works fine [2024-03-08T07:09:46Z] <riteo> I had a lot of trouble debugging the thing because, very embarassingly, the daemon would persist between sessions (I assumed it wouldn't) hehe [2024-03-08T07:52:37Z] <riteo> testuser[m]: you're the maintainer of the pipewire package, right? Does pipewire work for you? I can consistently use older 1.0.0+0.4.16-1 version but not the new 1.0.3+0.4.82 one, which is weird, as all the alsa-udev stuff got unchanged between those versions, so I'm not sure what changed to break device probing (I only have "Dummy Output") [2024-03-08T08:25:33Z] <riteo> it broke again wtf [2024-03-08T08:31:56Z] <sewn> i love pipewire [2024-03-08T08:38:26Z] <riteo> newsflash: I ran it at root and it worked [2024-03-08T08:38:38Z] <riteo> my existence is becoming more and more miserable at every attempt [2024-03-08T08:39:09Z] <riteo> sewn: the funny thing is that it just worked the first time I setup it and was like "uh, that's it?" and worked with anything I threw at it [2024-03-08T08:39:16Z] <riteo> then one day I reboot and here we are [2024-03-08T08:41:54Z] <riteo> ok while testing I had set up a broken user config, 0.3.85+0.4.15-1 definitely works [2024-03-08T08:44:17Z] <riteo> 1.0.3 does _not_ work when ran from the user, but it does work when run from root [2024-03-08T08:46:34Z] <riteo> 1.0.0 works fine [2024-03-08T08:50:47Z] <riteo> the issue might be wireplumber, as mixing 1.0.3 and a new wireplumber version works [2024-03-08T09:13:26Z] <riteo> yup, got it finally. You can use _any_ pipewire version (1.0.3 works fine), but the only wireplumber setup I could find was 0.4.16 WITH no-dbus.patch applied [2024-03-08T09:14:20Z] <riteo> if you take that out it just stops working, migth be related to the device reservation module, not sure. One thing though is that 0.4.82 completely revamped the scripts so it might "just" be a matter of again disabling the right things. [2024-03-08T09:14:57Z] <riteo> I've been debugging this stuff for more than one day, thus, my adventure ends here for now, happy to have pipewire 1.0.3+0.4.16 (with no-dbus.patch). [2024-03-08T09:15:18Z] <riteo> Sorry for the wall of text [2024-03-08T09:16:05Z] <riteo> testuser[m]: hope this ends up useful to troubleshoot any problem that new wireplumber versions might give