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 702087 - tray icon flicker with awesome WM
tray icon flicker with awesome WM
Status: RESOLVED DUPLICATE of bug 698901
Product: NetworkManager
Classification: Platform
Component: nm-applet
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-06-12 12:02 UTC by Kyrylo Shpytsya
Modified: 2013-06-12 12:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kyrylo Shpytsya 2013-06-12 12:02:19 UTC 
NetworkManager (v0.9.6.4) applet icon in systray is flickering.

If nm-applet is executed with NMA_SIZE_DEBUG=1 env var, one can see endless cycle of

** Message: status_icon_size_changed_cb(): status icon size now 19
** Message: status_icon_size_changed_cb(): status icon size now 22
** Message: status_icon_size_changed_cb(): status icon size now 26
** Message: status_icon_size_changed_cb(): status icon size now 28

debug output, which is printed in handler of "size-changed" signal of gtk3 gtk_status_icon_* object. So it apparently is some kind of race condition. Since I am not expert in X windows internals, I cannot say for sure if it is a fault of awesome, or rather of nm-applet, however this behavior does not occur if awesome's own systray is disabled and instead "tint2" is used for systray.

Please refer to:

https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1143
(there is apparently an issue with TLS certificate)
Comment 1 Dan Winship 2013-06-12 12:59:19 UTC 
this is fixed in git master and in 0.9.8.2. 0.9.6 isn't really being maintained any more, though the patch would probably apply if you wanted to patch it locally (https://git.gnome.org/browse/network-manager-applet/patch/?id=d6f5bd36)

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