2026-09-01 09:08:45 Getting cosmic to work is pretty straightforward. 2026-09-01 10:39:08 When trying to install https://github.com/OpenNebula/addon-context-linux/releases/download/v6.6.1/one-context-6.6.1-r1.apk to alpine 3.24, apk says "v2 package format error" - what's the right way to "reformat" the apk? 2026-09-01 10:55:23 I just noticed there is monero package in edge repo. Do you think it would be possible to run monero node over I2P network using I2Pd package on Raspberry Pi 4 or 5? 2026-09-01 11:43:39 "When trying to install https://..." <- with an apk from 2023 you wont have much luck on an edge install 2026-09-01 11:43:56 probably rebuilding from source might fix it 2026-09-01 11:44:55 or try this? https://github.com/OpenNebula/one-apps/releases/tag/v7.4.0 2026-09-01 12:05:22 Anyone else have issues with bluetooth speakers/headsets that started over last day or 2? 2026-09-01 12:05:50 Not getting much in errors beyond a br-connection-unknown error from bluez. Can try rolling back more firmware, but trying to validate what step to take next 2026-09-01 12:06:22 Mice and keyboards are fine. 2026-09-01 12:52:19 "or try this? https://github.com..." <- I actually overlooked that one - thanks for the pointer! It indeed works! 2026-09-01 15:09:47 andar1an: I have the same problem, it's a regression in a wireplumber upgrade 2026-09-01 15:14:26 Thank you lnl! I rolled back pipewire, but not wireplumber yet. 2026-09-01 16:56:21 this? https://gitlab.freedesktop.org/pipewire/wireplumber/-/work_items/999 2026-09-01 16:57:16 It didn't have to do with profiles for me 2026-09-01 16:57:31 Profiles would have been a different error 2026-09-01 16:58:04 Just purely unable to connect. Was able to grab a snippet of "local host dropped connection" with a specific flow 2026-09-01 16:59:21 Could pair, could trust. Couldn't connect. 2026-09-01 17:00:18 All bluetooth audio devices i tried were the same (tried 3). 2026-09-01 17:00:52 These same devices never had issues even earlier this week 2026-09-01 17:01:38 I can try to dig for more info later when back at system 2026-09-01 17:05:11 Maybe something changed with wireplumber config that needs update, maybe bluetooth firmware? Going to start with wireplumber rollback and go from there. Already tried rolling back pipewire and a few firmwares (maybe wrong ones) 2026-09-01 21:33:57 Thank you lnl, was wireplumber for me too 2026-09-01 21:36:03 omni: doesn't look like it 2026-09-01 21:36:49 I've bisected it down to https://gitlab.freedesktop.org/pipewire/wireplumber/-/commit/cb92ef9846e2b2f827e1831515bc3a31e7d2ed1a but this doesn't tell me much 2026-09-01 21:54:35 Do you think there is some loop with the addition of remove dropping the connection. Maybe some logic is flawed, because I was immediately getting dropped by local host 2026-09-01 21:55:08 That's awesome you dug down to that haha. How long did that take? 2026-09-01 22:02:24 A bit, I had to reboot multiple times to confirm if it works or not 2026-09-01 22:04:45 Line 58, create-device.lua 2026-09-01 22:04:47 Does that seem right? 2026-09-01 22:06:25 I want to dig in with you haha. I just know nothing about the codebase yet 2026-09-01 22:10:01 Just seems weird from a naiive perspective to see a connection event removing a node. But it could be for a reason i don't know yet. 2026-09-01 22:12:13 If that is supposed to be there, maybe something is triggering object removed signal when it shouldn't? 2026-09-01 22:18:56 There also used to be a createDevice function, and a CreateMonitor function. Now just createMonitor 2026-09-01 22:20:57 Just renamed. My bad 2026-09-01 22:29:46 Could it be as simple as the changes in module standard event sources? Should remkve have the same event priority? 2026-09-01 22:35:02 Gotta go make dinner, sorry if that was useless haha