Anytime a notification is received and cleared from Chrome Rich Notifications, it leaves a residual icon in the status and notifications system tray widget. Please see the screenshot http://i.imgur.com/4nlbkf2.png. This can be confirmed with both Chrome stable and unstable. Reproducible: Always Steps to Reproduce: 1. Wait/trigger for notification. 2. Clear notification from Chrome bell icon. 3. Check the Status & Notifications in System Tray. Actual Results: Multiple entries of google-chrome-unstable in Status & Notifications in System Tray Expected Results: 1. google-chrome-unstable entry is of no use and should not be up there in Status & Notifications. 2. Google Chrome has its own notification center so its extra entry in Status & Notification is redundant. Linux 3.16.2-200.fc20.x86_64 #1 SMP Mon Sep 8 11:54:45 UTC 2014 x86_64 Fedora 20 Plasam 5.0.1 Frameworks 5.2 installed via copr repository.
With Chrome Stable* I can confirm there is a special icon created after Chrome's notifications, but it's just one icon and I consider that a "feature" of Chrome. As for Chrome unstable...well, it's unstable :) We cannot support unstable versions of things; this should be fixed in Chrome instead anyway as there is apparently a bug in the creation of that icon. > 2. Google Chrome has its own notification center so its extra entry in Status & Notification is redundant. That's also a report for Chrome developers really...we display in there whatever the application tells us to display. If Chrome has its own center and still asks the shell to create an icon...that's a bug on the other side, sorry :) * Chrome 36.0.1985.143
I will go ahead and file a bug with Google Chrome devs. Is there anything that I can point out to them to let them know how they should be implementing system tray support for libappindicator/Kstatusnotifieritems? Providing more precise information would be very helpful. Although we needn't support Chrome unstable but there is cost of not testing unstable on Plasma desktop. After Chrome released AURA graphic stack it came with several regressions related to how it works on Plasma. It takes two months for a bug fix to get to the stable release. google-chrome-unstable isn't really unstable but it changes from week to week basis. Thanks for commenting.
What do you think about this screenshot http://i.imgur.com/h82RJza.png? In this screenshot, you can see there is a Chrome and a Hangouts system tray icon and 3 notifications. Right clicking on notifications opens Hangouts right click menu which you are suppose to click to open Hangouts. But they don't actually do anything. Nothing happens when you click the Hangouts menu opened by clicking on notification google-chrome-stable tabs. I am using Chrome stable Version 37.0.2062.120 (64-bit).
It still is Chrome's bug. The systray icons, known as StatusNotifierItems or AppIndicators (I think that's what Ubuntu calls them) is a specification. Each application that wants to put an icon into the systray must follow that specification, either by implementing it on its own or by using some library helping with that. Each application can add three million icons in the tray if it wishes to. And there's nothing we can do about it because from Plasma's point of view, it behaves correctly. It's the application's responsibility to make sure systray icons are handled properly and not for example triplicated. Sorry.
Thanks Martin. Filed a bug report at Chromium. https://code.google.com/p/chromium/issues/detail?id=419673&thanks=419673&ts=1412240115