Your message dated Thu, 19 Sep 2024 09:49:12 +0200
with message-id
<CA+6XHwSh14eZ=0gm3-kvnyobwfm3knexivxwh631g57romm...@mail.gmail.com>
and subject line Re: Bug#1075896: wireplumber: Please backport v0.5 to stable.
v0.4 broken with pipewire 1.2
has caused the Debian Bug report #1075896,
regarding wireplumber: Please backport v0.5 to stable. v0.4 broken with
pipewire 1.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1075896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wireplumber
Version: 0.4.17-1~bpo12+1
Severity: wishlist
X-Debbugs-Cc: noisyc...@tutanota.com
Dear Maintainer,
After upgrading pipewire to 1.2, which was backported to stable back in April,
neither the GNOME settings panel nor `wpctl status` are able to detect the
correct sink, and I can no longer regulate volume (although sound still plays).
Rolling back to 1.0 fixes this. On the same machine, a testing/unstable
installation with wireplumber 0.5 + pipewire 1.2 + the same kernel has no
issues. Apparently then, it is the pairing of wireplumber 0.4 + pipewire 1.2
that is not working properly. Since bookworm-backports is already providing
pipewire 1.2, I would like to ask you to backport wireplumber 0.5 to stable in
the hope that this will fix the issue.
Thank you,
NoisyCoil
-- System Information:
Debian Release: 12.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Kernel: Linux 6.9.7+bpo-asahi (SMP w/8 CPU threads)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
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-1~deb12u1
ii init-system-helpers 1.65.2
ii libc6 2.36-9+deb12u7
ii libglib2.0-0 2.74.6-2+deb12u3
ii libpipewire-0.3-0 1.2.0-1~bpo12+1
ii libwireplumber-0.4-0 0.4.17-1~bpo12+1
ii pipewire 1.2.0-1~bpo12+1
Versions of packages wireplumber recommends:
ii pipewire-pulse 1.2.0-1~bpo12+1
Versions of packages wireplumber suggests:
ii libspa-0.2-bluetooth 1.2.0-1~bpo12+1
pn libspa-0.2-libcamera <none>
pn wireplumber-doc <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.5.6-1~bpo12+1
Hi,
Le dim. 7 juil. 2024 à 14:57, NoisyCoil <noisyc...@tutanota.com> a écrit :
>
> After upgrading pipewire to 1.2, which was backported to stable back in
> April, neither the GNOME settings panel nor `wpctl status` are able to detect
> the correct sink, and I can no longer regulate volume (although sound still
> plays). Rolling back to 1.0 fixes this. On the same machine, a
> testing/unstable installation with wireplumber 0.5 + pipewire 1.2 + the same
> kernel has no issues. Apparently then, it is the pairing of wireplumber 0.4 +
> pipewire 1.2 that is not working properly. Since bookworm-backports is
> already providing pipewire 1.2, I would like to ask you to backport
> wireplumber 0.5 to stable in the hope that this will fix the issue.
>
Wireplumber 0.5.6-1 is now available in bookworm-backports.
Best regards,
Dylan
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers