Package: lxqt-panel
Version: 2.3.2-4
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Distributor ID: Devuan
Description: Devuan GNU/Linux 7 (freia/ceres)
Release: 7
Codename: freia ceres
Architecture: x86_64
Kernel: Linux 7.1.3+deb14-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled
Versions of packages lxqt-panel depends on:
ii libasound2t64 1.2.16.1-1
ii libc6 2.42-17
ii libdbusmenu-lxqt0 0.4.0-1
ii libkf6solid6 6.26.0-1
ii libkf6windowsystem6 6.26.0-1
ii liblayershellqtinterface6 6.7.2-1
ii liblxqt-globalkeys-ui2 2.4.0-1
ii liblxqt-globalkeys2 2.4.0-1
ii liblxqt2 2.4.0-1
ii libpulse0 17.0+dfsg1-2.1+b2
ii libqt6core6t64 [qt6-base-private-abi] 6.10.2+dfsg-15
ii libqt6dbus6 6.10.2+dfsg-15
ii libqt6gui6 6.10.2+dfsg-15
ii libqt6svg6 6.10.2-9
ii libqt6waylandclient6 6.10.2+dfsg-15
ii libqt6widgets6 6.10.2+dfsg-15
ii libqt6xdg4 4.4.0-1
ii libqt6xml6 6.10.2+dfsg-15
ii libsensors5 1:3.6.2-2+b2
ii libstatgrab10t64 0.92.1-1.2
ii libstdc++6 16.1.0-3
ii libsysstat-qt6-1 1.1.0-1+b2
ii libwayland-client0 1.26.0-1
ii libx11-6 2:1.8.13-1
ii libxcb-composite0 1.17.0-2+b2
ii libxcb-damage0 1.17.0-2+b2
ii libxcb-image0 0.4.0-2+b3
ii libxcb-shape0 1.17.0-2+b2
ii libxcb-util1 0.4.1-1+b2
ii libxcb-xkb1 1.17.0-2+b2
ii libxcb1 1.17.0-2+b2
ii libxkbcommon-x11-0 1.13.1-1
ii libxkbcommon0 1.13.1-1
ii libxtst6 2:1.2.5-1+b2
ii lxqt-menu-data 2.4.0-1
ii lxqt-policykit 2.4.0-1
ii lxqt-theme-debian 0.14.0.8
Versions of packages lxqt-panel recommends:
ii lxqt-about 2.4.0-1
ii lxqt-config 2.4.0-1
ii lxqt-notificationd 2.4.0-1
ii lxqt-panel-l10n 2.3.2-4
ii lxqt-qtplugin 2.4.0-1
ii lxqt-runner 2.4.0-1
ii lxqt-session 2.4.0-1+b1
ii pavucontrol 6.1-1
ii pavucontrol-qt 2.4.0-1
ii qlipper 1:6.1.0-1
Versions of packages lxqt-panel suggests:
ii lxqt 33.2+b1
ii lxqt-core 33.2
ii qtxdg-tools 4.4.0-1
-- no debconf information
When lxqt-panel's volume plugin is configured to use "pavucontrol"
(GTK) as external mixer, clicking the "Mixer" link, or more
importantly, the volume popup itself, misbehaves: on my system the
popup opened on hover but closed almost instantly, making the
volume slider effectively unusable via mouse.
Switching the "External Mixer" setting in the volume plugin's
configuration dialog to "pavucontrol-qt" fixed the issue completely
and immediately.
Root cause analysis: lxqt-panel Recommends "pavucontrol-qt |
pavucontrol", treating both as interchangeable alternatives. In
practice they are not equivalent from the plugin's point of view:
apt satisfies this Recommends line as soon as either package is
present, so if pavucontrol (GTK) happens to already be installed
for any reason, pavucontrol-qt is never pulled in, and the user
ends up with a broken/unreliable volume popup with no indication
of why.
Suggestion: either drop the alternative and Recommend pavucontrol-qt
specifically, or have the plugin/documentation clarify that the GTK
build is not fully supported for this use case.
--- System context (for transparency) ---
This system is a Devuan LXQt install obtained by cloning an
existing Devuan XFCE install to a separate partition (via rsync),
then purging xfce4 and installing task-lxqt-desktop in a chroot.
pavucontrol (GTK) was already present on the system, inherited from
the original XFCE install, which is almost certainly why apt never
pulled pavucontrol-qt in via the Recommends line above. This is an
unusual ("on the edge") installation method, not a fresh live
install, and I cannot rule out that some other pre-existing leftover
package/config contributed to the issue. That said, the Recommends
alternative itself seems like a genuine packaging inconsistency
regardless of install method, since a fresh system where pavucontrol
(GTK) got pulled in first by some other dependency chain would
hit the same problem.
Simple Workaround: to start pavucontrol "by hand" through terminal
