After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685296 - Systray icon disappears on desktop environment restart
Systray icon disappears on desktop environment restart
Status: RESOLVED DUPLICATE of bug 529023
Product: banshee
Classification: Other
Component: User Interface
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Reported: 2012-10-02 14:08 UTC by Lars Mueller
Modified: 2012-11-02 10:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Lars Mueller 2012-10-02 14:08:54 UTC
After a desktop environment restart (e.g. after a DE crash or by invoking "gnome-shell --replace" in a terminal), the Notification Area Extension fails to detect the newly created system tray. It also happens, if the system tray is started with Banshee already up and running.

This happens in Gnome Shell (and Cinnamon) as well as in KDE.
 It does not happen, if the Notification Area Extension is changed so that it uses the Gtk implementation to communicate with the system tray (usually only used on non-UNIX-systems), instead of its own X11 event handling.

Reproducible: always
How to reproduce:
1) start banshee
2) enable Notification Area Extension (if not enabled)
3) restart desktop environment (e.g. via terminal with "gnome-shell --replace")

Expected result: Banshee recognizes the new system tray and displays its icon there
Actual result: Banshee does not detect the new system, the icon is not displayed

Further information:
The X11 communication in X11NotificationArea.cs gets a wrong selection_atom code from the XClientMessageEvent, although the desktop environment uses the exact same code, that X11NotificationArea.cs uses for comparison. I discovered this when looking into an issue filed to Cinnamon ( and
Comment 1 Bertrand Lorentz 2012-11-02 10:20:48 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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