Bug 487166

Summary: Sometimes clicking a tray icon will invoke the menu of a completely different tray icon
Product: [Plasma] plasmashell Reporter: Ellie <el>
Component: System TrayAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: materka
Priority: NOR    
Version: 6.0.4   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Video showing the wrong tray menu opening up depending on the exact spot clicked

Description Ellie 2024-05-17 22:49:28 UTC
Created attachment 169584 [details]
Video showing the wrong tray menu opening up depending on the exact spot clicked

SUMMARY

Sometimes clicking a tray icon while invoke the menu of a completely different tray icon. See the attached video for demonstration, where a right-click on the volume tray icon sometimes brings up the keepass tray icon menu.

STEPS TO REPRODUCE

1. (Somehow enter the broken state, it's not 100% reproducible and just having keepass running isn't enough)
2. Right-click an affected icon, where also the exact pixel that was right-clicked could be relevant
3. Observe what menu opens

OBSERVED RESULT

Wrong menu opens sometimes. It seems to depend on the exact pixel position and somehow the order of icons. Simply keepass being running alone isn't sufficient. It also happens both with the keepass icon hidden in the tray overflow area and also with the keepass icon showing, that doesn't seem to make a difference.

EXPECTED RESULT

Right menu opens no matter which tray icon I click and no matter which spot.

SOFTWARE/OS VERSIONS

Windows: 
macOS: 
Linux/KDE Plasma: openSUSE Slowroll
(available in About System)
KDE Plasma Version: plasmashell 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0 

ADDITIONAL INFORMATION
Comment 1 Konrad Materka 2024-05-18 12:41:39 UTC
Are you using Wayland? Is Bug 433079 related?
Comment 2 Ellie 2024-05-18 13:09:31 UTC
I'm using Wayland, yes! keepass I'm pretty sure is some legacy X11/XWayland app, so maybe it could be related. I don't know about the tech well enough to say if the bug you linked is definitely the same, but it sounds like a similar area.
Comment 3 Konrad Materka 2024-05-18 13:40:08 UTC
Yes, it's the same issue. Thank you for your report!

*** This bug has been marked as a duplicate of bug 433079 ***