Bug 412003 - xembed tray menu partially blocked with auto hiding panel
Summary: xembed tray menu partially blocked with auto hiding panel
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Tray (show other bugs)
Version: 5.16.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-17 19:53 UTC by Linus Kardell
Modified: 2020-02-14 20:52 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Linus Kardell 2019-09-17 19:53:52 UTC 
SUMMARY
When the panel is set to auto hide or windows can cover, xembed menus are blocked where the panel would be.

STEPS TO REPRODUCE
1. Set the panel to auto hide or windows can cover
2. Run an application with an xembed tray item
3. Right click the tray item, near the bottom

OBSERVED RESULT
The bottom of the menu (where the panel was), does not respond to hover or click.

EXPECTED RESULT
The whole menu is usable

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.61.0
Qt Version: 5.13.1
Comment 1 Konrad Materka 2019-10-14 12:52:35 UTC 
Reproducible with:
* xchat, hexchat, workrave (GTK+ 2)
* liferea (GTK+ 3)
* tuxguitar (Java)
Works correctly with:
* keepass2 (Mono)
* keepassx (Qt 4 without sni)
* any SNI/appindicator app - it prevents panel from hiding, XembedSNIProxy is not used
Comment 2 Patrick Silva 2020-02-07 20:38:37 UTC 
at least liferea and hexchat work as expected on Plasma 5.18 beta with auto-hiding panel.

Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1
Comment 3 Konrad Materka 2020-02-14 20:52:05 UTC 
I tested liferea, hexchat and xchat, issue is still there:
Operating System: KDE neon 5.18
KDE Plasma Version: 5.18.80
KDE Frameworks Version: 5.68.0
Qt Version: 5.13.2

Maybe it was fixed in Qt 5.14?