Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 768666

Summary: lxqt-base/lxqt-meta: tray widget is broken
Product: Gentoo Linux Reporter: Vitaly Zdanevich <zdanevich.vitaly>
Component: Current packagesAssignee: LxQt maintainers <lxqt>
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Package list:
Runtime testing required: ---
Attachments: On nm-applet hover the panel is hidden
Default list of available widgets

Description Vitaly Zdanevich 2021-02-04 17:48:38 UTC
Created attachment 685749 [details]
On nm-applet hover the panel is hidden

Out of the box there is an issue with nm-applet and autohide. And in available widgets I see `statusnotifier` but this is Unknown and do nothing. Member of LXQt organization on Github said "Something should be wrong with the package your distro provides. Ask you distro about that!" 

This issue is related to
Comment 1 Vitaly Zdanevich 2021-02-04 17:49:19 UTC
Created attachment 685752 [details]
Default list of available widgets
Comment 2 Vitaly Zdanevich 2021-02-04 17:57:18 UTC
Reply from

Status Notifier Plugin is a part of the Panel itself, not a separate app.

As I said, you may want to ask your distro as to why Status Notifier Plugin isn't included. Your distro should have a forum for asking questions.
Comment 3 Chiitoo gentoo-dev 2021-02-04 18:41:06 UTC
Did you build with USE="statusnotifier"?
Comment 4 Vitaly Zdanevich 2021-02-04 20:09:26 UTC
Rebuild with USE="statusnotifier", now in Widgets I see Status Notifier Plugin (statusnotifier), but how can I get not obsolete tray that is not autohide the panel when I hover the Wi-Fi ico from nm-applet?
Comment 5 Chiitoo gentoo-dev 2021-02-04 20:26:10 UTC
Try disabling the 'tray' widget, and see if you still get the nm-applet to show up.

It may choose to show up in the 'tray' one if you have both enabled.

If you don't see it, it might not support 'statusnotifier'.
Comment 6 Vitaly Zdanevich 2021-02-04 23:13:19 UTC
Disabled the `tray` widget - looks like `statusnotifier` is 0px :(

Developers of nm-applet should fix something?
Comment 7 Chiitoo gentoo-dev 2021-02-05 12:22:20 UTC
Just to be sure, it's 'gnome-extra/nm-applet'?

I just tried it myself, and to me, too, it seems to be able to use 'tray' only.

Yes, it would look like changes are needed in 'nm-applet' itself.
Comment 8 Vitaly Zdanevich 2021-02-05 13:30:00 UTC
Filled issue at
Comment 9 Vitaly Zdanevich 2021-02-09 16:57:27 UTC
I found that on Gentoo I need to build nm-applet with USE flag appindicator. Description of this flag: "Build in support for notifications using the libindicate or libappindicator plugin". Also USE statusnotifier for lxqt-base/lxqt-panel and alter autostart from nm-applet to nm-applet --indicator.

Maybe you can automate this a little bit: when gnome-extra/nm-applet is built with USE appindicator and LXQt is installed and lxqt-base/lxqt-panel is built with USE statusnotifier: alter startup from `nm-applet` to `nm-applet --indicator`. Also maybe show in the console message after different variants on installations. I spent hours because of this defect, lets make it better for other people.
Comment 10 Manfred Knick 2021-11-08 12:37:06 UTC
Comment 11 Chiitoo gentoo-dev 2022-04-10 17:35:10 UTC
Apologies for the delay on looking into this again!

Since 'gnome-extra/nm-applet' is a package that I'm not tracking in any way (no USE-flag to pull it in for example), I don't think I will want to add special handling for it.

It seems that someone (probably you; thank you for that!) has added a note about this behaviour into the LXQt and NetworkManager articles on the Gentoo Wiki, which I believe is good enough for the time being.

With the next version bump, I'll see if it makes sense to add an 'optfeature' post-install message or something similar about this.

I'll close this now, since I don't see this as a defect in the LXQt ebuilds, but rather an nm-applet configuration peculiarity.  That, and we no longer enable the 'tray' plug-in by default, though perhaps it should be removed completely soon (I'd like to keep it for a while more for the applications that don't play well with the statusnotifier one, though perhaps it should receive a warning of sorts in the ebuild).

Thank you for the report, and for finding the way to make it work!