Bug 362556

Summary: Right click on legacy GTK tray icons does not work.
Product: [Plasma] plasmashell Reporter: Luca Mastromatteo <lukycrociato>
Component: XembedSNIProxyAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: beaux_monde, kde, kde, l12436.tw, sknauss
Priority: NOR    
Version: master   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Luca Mastromatteo 2016-05-01 18:39:59 UTC
Right clicking on the legacy GTK icons, in the icon tray, nothing happens. 

Reproducible: Always

Steps to Reproduce:
1. Have a GTK program which uses GTK legacy icon trays. (Like Pamac, or redshift)
2.
3.

Actual Results:  
Nothing happens.

Expected Results:  
After right clicking on them, there should be a dropdown menu.
Comment 1 Sandro Knauß 2016-07-21 09:15:26 UTC
Can confirm on debian unstable ( plasma 5.6.5.1) with the application ring and pracimonie-applet.
Comment 2 David Edmundson 2016-07-21 12:41:18 UTC
Whilst I will try to fix this, please also file a bug with each of those respective projects that they need to use the updated SNI specification.

https://www.freedesktop.org/wiki/Specifications/StatusNotifierItem/StatusNotifierItem/
Comment 3 Sandro Knauß 2016-07-21 23:23:17 UTC
I updated a bug for parcimonie - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799942
So far I understand from the code parcimonie is written in perl using the Gtk3/Glib3 for their applet. 

Also ring is gtk3 software.
Comment 4 Sandro Knauß 2016-07-21 23:57:47 UTC
ring bugreport: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832067
Comment 5 pdf 2016-08-27 02:29:02 UTC
pamac issue: https://github.com/manjaro/pamac/issues/159
Comment 6 pdf 2016-08-28 10:20:22 UTC
pamac has merged changes to enable use of SNI under KDE.
Comment 7 Serge Roussak 2017-02-08 05:14:11 UTC
I use the Arch too, but this issue has appeared since the 5.9.0. Prior this version right click was working. Downgrading the plasma-workspace to the 5.8.x solves this issue.
Comment 8 David Edmundson 2017-02-08 09:17:47 UTC
*** Bug 375930 has been marked as a duplicate of this bug. ***