Bug#1070729: wireplumber: 0.5 breaks unmodified configurations because of incompatible state format
Hi, I moved old configuration in (thankfully still in trash on my notebook, forgot to keep it on the main PC), upgraded and restarted the service - seems to be working correctly now! Grzesiek11 W dniu 3.06.2024 o 10:22, Dylan Aïssi pisze: Hi, Le mer. 8 mai 2024 à 05:21, Grzesiek11 a écrit : As mentioned by the NEWS entry, 0.5 replaces the old configuration system with a new one utilizing JSON. It also states this should be transparent for systems using only Debian configuration, however the state format (for files stored in $XDG_STATE_HOME/wireplumber) is also incompatible, causing unmodified configurations to break. The workaround I used is removing the state directory and restarting the service, causing it to regenerate. I just uploaded wireplumber 0.5.3 in sid. This version seems to fix a potential duplicated bug. Could you check if this version fix your issue once the package lands in apt repository? Thanks, Dylan
Bug#1070729: wireplumber: 0.5 breaks unmodified configurations because of incompatible state format
Hi, Le mer. 8 mai 2024 à 05:21, Grzesiek11 a écrit : > > As mentioned by the NEWS entry, 0.5 replaces the old configuration > system with a new one utilizing JSON. It also states this should be > transparent for systems using only Debian configuration, however the > state format (for files stored in $XDG_STATE_HOME/wireplumber) is also > incompatible, causing unmodified configurations to break. > > The workaround I used is removing the state directory and restarting the > service, causing it to regenerate. I just uploaded wireplumber 0.5.3 in sid. This version seems to fix a potential duplicated bug. Could you check if this version fix your issue once the package lands in apt repository? Thanks, Dylan
Bug#1070729: wireplumber: 0.5 breaks unmodified configurations because of incompatible state format
Package: wireplumber Version: 0.5.2-2 Severity: important Dear Maintainer, As mentioned by the NEWS entry, 0.5 replaces the old configuration system with a new one utilizing JSON. It also states this should be transparent for systems using only Debian configuration, however the state format (for files stored in $XDG_STATE_HOME/wireplumber) is also incompatible, causing unmodified configurations to break. The workaround I used is removing the state directory and restarting the service, causing it to regenerate. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wireplumber depends on: ii dbus-user-session [default-dbus-session-bus] 1.14.10-4+b1 ii dbus-x11 [dbus-session-bus] 1.14.10-4+b1 ii init-system-helpers 1.66 ii libc6 2.38-8 ii libglib2.0-0t64 2.80.0-10 ii libpipewire-0.3-0t64 1.0.5-1+b3 ii libwireplumber-0.5-0 0.5.2-2 ii pipewire 1.0.5-1+b3 Versions of packages wireplumber recommends: ii pipewire-pulse 1.0.5-1+b3 Versions of packages wireplumber suggests: ii libspa-0.2-bluetooth 1.0.5-1+b3 pn libspa-0.2-libcamera pn wireplumber-doc -- no debconf information
