On Wed, Aug 5, 2026 at 9:21 AM arrosoir.bleu <[email protected]> wrote:
> ii pavucontrol 6.1-1
> ii pavucontrol-qt 2.4.0-1
You have both gtk and qt versions installed.
> 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.
I cannot reproduce this in my setup. However I got some warming from
X11, maybe that's related in your setup?
> Switching the "External Mixer" setting in the volume plugin's
> configuration dialog to "pavucontrol-qt" fixed the issue completely
> and immediately.
It works in paralle for me. Both connect and talk with pauseauide
daemon when launchs.
> 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
I cannot reproduce it in my clean environment. Can you reproduce it
with documented steps in a clean envirnoment?
Best regards,
--
-Andrew
