Your message dated Fri, 3 Jan 2025 11:23:11 +0100 with message-id <ca+6xhwsr7exevrwl3sxmxcemuzt0q+ljnajgksj9k_zqf8f...@mail.gmail.com> and subject line Re: wireplumber doesn't start from daemon when using libglib2.0-0t64 2.82.4-1 has caused the Debian Bug report #1089865, regarding wireplumber doesn't start from daemon when using libglib2.0-0t64 2.82.4-1 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.) -- 1089865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: wireplumber Version: 0.5.7-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After the following upgrades were applied and logged out and in again, wireplumber did not start from daemon. [UPGRADE] gir1.2-glib-2.0:amd64 2.82.3-2 -> 2.82.4-1 [UPGRADE] gir1.2-glib-2.0-dev:amd64 2.82.3-2 -> 2.82.4-1 [UPGRADE] girepository-tools:amd64 2.82.3-2 -> 2.82.4-1 [UPGRADE] libgio-2.0-dev:amd64 2.82.3-2 -> 2.82.4-1 [UPGRADE] libgio-2.0-dev-bin:amd64 2.82.3-2 -> 2.82.4-1 [UPGRADE] libgirepository-2.0-0:amd64 2.82.3-2 -> 2.82.4-1 [UPGRADE] libglib2.0-0t64:amd64 2.82.3-2 -> 2.82.4-1 [UPGRADE] libglib2.0-bin:amd64 2.82.3-2 -> 2.82.4-1 [UPGRADE] libglib2.0-data:amd64 2.82.3-2 -> 2.82.4-1 [UPGRADE] libglib2.0-dev:amd64 2.82.3-2 -> 2.82.4-1 [UPGRADE] libglib2.0-dev-bin:amd64 2.82.3-2 -> 2.82.4-1 /usr/bin/daemon --bind --respawn --pidfiles=$XDG_RUNTIME_DIR --name=pipewire-wir eplumber /usr/bin/wireplumber (loaded from .xsessionrc) did not start. I could run wireplumber from the command line and it would start. * What exactly did you do (or not do) that was effective (or ineffective)? I downgraded those pages, and could again get wireplumber starting from the daemon connect in .xsessionrc * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: trixie/sid APT prefers experimental APT policy: (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.13.0-rc2+ (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages wireplumber depends on: ii dbus-x11 [default-dbus-session-bus] 1.15.90-1devuan2 ii init-system-helpers 1.67devuan1 ii libc6 2.40-4 ii libglib2.0-0t64 2.82.3-2 ii libpipewire-0.3-0t64 1.2.7-1 ii libwireplumber-0.5-0 0.5.7-1 ii pipewire 1.2.7-1 Versions of packages wireplumber recommends: ii pipewire-pulse 1.2.7-1 Versions of packages wireplumber suggests: ii libspa-0.2-bluetooth 1.2.7-1 ii libspa-0.2-libcamera 1.2.7-1 pn wireplumber-doc <none> -- no debconf information
--- End Message ---
--- Begin Message ---On Sun, 15 Dec 2024 19:06:58 +1030 Arthur Marsh <arthur.ma...@internode.on.net> wrote: > Package: wireplumber > Followup-For: Bug #1089865 > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > Please close the bug report, unable to reproduce the issue now. > So closing! 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
