Hi,
Carlos Soriano Sanchez suggested I re-sent my call for help on the
GNOME Shell list, so here we go. Please keep me Cc'ed, I'm not
subscribed to gnome-shell-list@???.
I am a contributor to the Tails project (
https://tails.boum.org/),
a live system aimed at preserving its users' safety, privacy and
anonymity, focusing on ease of use for non-technical users. To give
you an idea of the impact of the problems I'm asking for help here,
we're talking about a system that is started more than 17,000 times
a day.
We are about to release Tails 2.0 in a few days. It will be our first
release based on Debian 8 (Jessie), and more to the point here, our
first release that includes GNOME Shell as the default (and only)
desktop environment. Woo!
There's a glitch though: during the beta and RC phases, many testers
reported to us serious bugs with how icons in the top-right tray are
displayed. Probably relevant is the fact that we include the topIcons
extension (because not all the important status icons have been
migrated to more modern GNOME technologies yet). But not only icons
moved by topIcons to the top-right tray are affected.
TBH, I personally came to the conclusion that the bug most likely
lives in the topIcons extension. I can very well understand if you see
it as none of your business for this reason, and I have reported it to
this extension's author already.
Still, we're in a hard place on our way to ship GNOME Shell right now,
because sadly, nobody on our team has the skills to debug this
problem, so we help from any skilled people would be much appreciated.
The symptoms we see are:
* Widgets in the top-right tray are somewhat narrowed (to their
arrow, with a dot instead of the expected text); I've seen this
happen at least for the date/time and the ibus menu icon:
https://labs.riseup.net/code/attachments/download/1186/new-session.png
https://labs.riseup.net/code/attachments/download/1180/1.png
https://labs.riseup.net/code/attachments/download/1181/2.png
https://labs.riseup.net/code/attachments/download/1182/3.png
https://labs.riseup.net/code/attachments/download/1183/4.png
* The clickable area and the icon of a widget moved by topIcons are
not at the same place. For example, nothing happens when I click on
the Florence icon, but Florence appears when I click elsewhere (on
the left of the OpenPGP Applet). This screenshot shows what is the
clickable area for Florence at this point:
https://labs.riseup.net/code/attachments/download/1173/clickable%20area.png
Enabled extensions:
* Classic mode extensions:
apps-menu@??? and
window-list@???
* topIcons v28
* a custom Tails extension called shutdown-helper@???:
https://git-tails.immerda.ch/tails/tree/config/chroot_local-includes/usr/share/gnome-shell/extensions/shutdown-helper@tails.boum.org?h=testing
Other possibly relevant information:
* We run GNOME Shell 3.14.4-1~deb8u1 in Classic mode.
* The ISO image for Tails 2.0~rc1 can be downloaded from
https://tails.boum.org/news/test_2.0-rc1/ — it's a live system, so
you can try it out in a virtual machine, after dd'ing it to a USB
stick, or burning it to a DVD.
* I don't seem to be able to reproduce these bugs with an ISO that
has the topIcons extension disabled. It seems that a loaded (or
just slow) system exposes the problem more often than a powerful
and idling system.
* I've seen similar bug reports online elsewhere:
https://extensions.gnome.org/extension/495/topicons/
https://www.reddit.com/r/archlinux/comments/2g06t7/icons_disappearing_from_notification_tray_using/
* In an environment (Spice/QXL/QEMU VM) where I can dynamically
change the display size & resolution, making the display way bigger
fixes the bug, and reverting to the initial display size reverts
back to the problematic initial state.
* There is one error in the logs that I only see when the bug
happens:
gnome-session[2343]: (gnome-shell:2871): GLib-GObject-WARNING **: /build/glib2.0-EvFudu/glib2.0-2.42.1/./gobject/gsignal.c:2579: instance '0x94b20f0' has no handler with id '32170'
It refers to
https://sources.debian.net/src/glib2.0/2.42.1-1/gobject/gsignal.c/?hl=2501#L2579
When this happens, I also see:
gnome-session[2003]: (gnome-shell:3042): Gjs-WARNING **: JS ERROR: TypeError: parent is null
gnome-session[2003]: onTrayIconRemoved@/usr/share/gnome-shell/extensions/topIcons@???@gmail.com/extension.js:115
* Another piece of logs that we (sometimes) see when the problem happens:
gnome-session[30034]: (gnome-shell:30263): Gjs-WARNING **: JS ERROR: TypeError: parent is null
gnome-session[30034]: moveToTop@/usr/share/gnome-shell/extensions/topIcons@???@gmail.com/extension.js:135
gnome-session[29844]: (gnome-shell:30074): Clutter-WARNING **: Attempting to add actor of type 'ShellTrayIcon' to a container of type 'ShellGenericContainer', but the actor has already a parent of type 'ShellGenericContainer'.
* The
https://github.com/wincinderith/topicons fork has changes in
areas that might be relevant to the problems we see. We've not
tested it so far.
Is there any information you need from us to debug this problem?
I'm sure those of us who see this problem would be glad to test
patches aimed at fixing it.
Please don't hesitate forwarding this message to anyone you think
might want to give us a hand.
Cheers!
--
intrigeri
,%0A>%20a%20live%20system%20aimed%20at%20preserving%20its%20users'%20safety,%20privacy%20and%0A>%20anonymity,%20focusing%20on%20ease%20of%20use%20for%20non-technical%20users.%20To%20give%0A>%20you%20an%20idea%20of%20the%20impact%20of%20the%20problems%20I'm%20asking%20for%20help%20here,%0A>%20we're%20talking%20about%20a%20system%20that%20is%20started%20more%20than%2017,000%20times%0A>%20a%20day.%0A>%20%0A>%20We%20are%20about%20to%20release%20Tails%202.0%20in%20a%20few%20days.%20It%20will%20be%20our%20first%0A>%20release%20based%20on%20Debian%208%20(Jessie),%20and%20more%20to%20the%20point%20here,%20our%0A>%20first%20release%20that%20includes%20GNOME%20Shell%20as%20the%20default%20(and%20only)%0A>%20desktop%20environment.%20Woo!%0A>%20%0A>%20There's%20a%20glitch%20though:%20during%20the%20beta%20and%20RC%20phases,%20many%20testers%0A>%20reported%20to%20us%20serious%20bugs%20with%20how%20icons%20in%20the%20top-right%20tray%20are%0A>%20displayed.%20Probably%20relevant%20is%20the%20fact%20that%20we%20include%20the%20topIcons%0A>%20extension%20(because%20not%20all%20the%20important%20status%20icons%20have%20been%0A>%20migrated%20to%20more%20modern%20GNOME%20technologies%20yet).%20But%20not%20only%20icons%0A>%20moved%20by%20topIcons%20to%20the%20top-right%20tray%20are%20affected.%0A>%20%0A>%20TBH,%20I%20personally%20came%20to%20the%20conclusion%20that%20the%20bug%20most%20likely%0A>%20lives%20in%20the%20topIcons%20extension.%20I%20can%20very%20well%20understand%20if%20you%20see%0A>%20it%20as%20none%20of%20your%20business%20for%20this%20reason,%20and%20I%20have%20reported%20it%20to%0A>%20this%20extension's%20author%20already.%0A>%20%0A>%20Still,%20we're%20in%20a%20hard%20place%20on%20our%20way%20to%20ship%20GNOME%20Shell%20right%20now,%0A>%20because%20sadly,%20nobody%20on%20our%20team%20has%20the%20skills%20to%20debug%20this%0A>%20problem,%20so%20we%20help%20from%20any%20skilled%20people%20would%20be%20much%20appreciated.%0A>%20%0A>%20The%20symptoms%20we%20see%20are:%0A>%20%0A>%20%20*%20Widgets%20in%20the%20top-right%20tray%20are%20somewhat%20narrowed%20(to%20their%0A>%20%20%20%20arrow,%20with%20a%20dot%20instead%20of%20the%20expected%20text);%20I've%20seen%20this%0A>%20%20%20%20happen%20at%20least%20for%20the%20date/time%20and%20the%20ibus%20menu%20icon:%0A>%20%0A>%20%20%20%20https://labs.riseup.net/code/attachments/download/1186/new-session.png%0A>%20%20%20%20https://labs.riseup.net/code/attachments/download/1180/1.png%0A>%20%20%20%20https://labs.riseup.net/code/attachments/download/1181/2.png%0A>%20%20%20%20https://labs.riseup.net/code/attachments/download/1182/3.png%0A>%20%20%20%20https://labs.riseup.net/code/attachments/download/1183/4.png%0A>%20%0A>%20%20*%20The%20clickable%20area%20and%20the%20icon%20of%20a%20widget%20moved%20by%20topIcons%20are%0A>%20%20%20%20not%20at%20the%20same%20place.%20For%20example,%20nothing%20happens%20when%20I%20click%20on%0A>%20%20%20%20the%20Florence%20icon,%20but%20Florence%20appears%20when%20I%20click%20elsewhere%20(on%0A>%20%20%20%20the%20left%20of%20the%20OpenPGP%20Applet).%20This%20screenshot%20shows%20what%20is%20the%0A>%20%20%20%20clickable%20area%20for%20Florence%20at%20this%20point:%0A>%20%0A>%20%20%20%20https://labs.riseup.net/code/attachments/download/1173/clickable%20area.png%0A>%20%0A>%20Enabled%20extensions:%0A>%20%0A>%20%20*%20Classic%20mode%20extensions:%0A>%20%20%20%20apps-menu@???%20and%0A>%20%20%20%20window-list@???%0A>%20%0A>%20%20*%20topIcons%20v28%0A>%20%0A>%20%20*%20a%20custom%20Tails%20extension%20called%20shutdown-helper@???:%0A>%20%0A>%20%20%20%20https://git-tails.immerda.ch/tails/tree/config/chroot_local-includes/usr/share/gnome-shell/extensions/shutdown-helper@tails.boum.org?h=testing%0A>%20%0A>%20Other%20possibly%20relevant%20information:%0A>%20%0A>%20%20*%20We%20run%20GNOME%20Shell%203.14.4-1~deb8u1%20in%20Classic%20mode.%0A>%20%0A>%20%20*%20The%20ISO%20image%20for%20Tails%202.0~rc1%20can%20be%20downloaded%20from%0A>%20%20%20%20https://tails.boum.org/news/test_2.0-rc1/%20%E2%80%94%20it's%20a%20live%20system,%20so%0A>%20%20%20%20you%20can%20try%20it%20out%20in%20a%20virtual%20machine,%20after%20dd'ing%20it%20to%20a%20USB%0A>%20%20%20%20stick,%20or%20burning%20it%20to%20a%20DVD.%0A>%20%0A>%20%20*%20I%20don't%20seem%20to%20be%20able%20to%20reproduce%20these%20bugs%20with%20an%20ISO%20that%0A>%20%20%20%20has%20the%20topIcons%20extension%20disabled.%20It%20seems%20that%20a%20loaded%20(or%0A>%20%20%20%20just%20slow)%20system%20exposes%20the%20problem%20more%20often%20than%20a%20powerful%0A>%20%20%20%20and%20idling%20system.%0A>%20%0A>%20%20*%20I've%20seen%20similar%20bug%20reports%20online%20elsewhere:%0A>%20%0A>%20%20%20%20https://extensions.gnome.org/extension/495/topicons/%0A>%20%20%20%20https://www.reddit.com/r/archlinux/comments/2g06t7/icons_disappearing_from_notification_tray_using/%0A>%20%0A>%20%20*%20In%20an%20environment%20(Spice/QXL/QEMU%20VM)%20where%20I%20can%20dynamically%0A>%20%20%20%20change%20the%20display%20size%20&%20resolution,%20making%20the%20display%20way%20bigger%0A>%20%20%20%20fixes%20the%20bug,%20and%20reverting%20to%20the%20initial%20display%20size%20reverts%0A>%20%20%20%20back%20to%20the%20problematic%20initial%20state.%0A>%20%0A>%20%20*%20There%20is%20one%20error%20in%20the%20logs%20that%20I%20only%20see%20when%20the%20bug%0A>%20%20%20%20happens:%0A>%20%0A>%20%20%20%20gnome-session%5B2343%5D:%20(gnome-shell:2871):%20GLib-GObject-WARNING%20**:%20/build/glib2.0-EvFudu/glib2.0-2.42.1/./gobject/gsignal.c:2579:%20instance%20'0x94b20f0'%20has%20no%20handler%20with%20id%20'32170'%0A>%20%0A>%20%20%20%20It%20refers%20to%0A>%20%20%20%20https://sources.debian.net/src/glib2.0/2.42.1-1/gobject/gsignal.c/?hl=2501#L2579%0A>%20%0A>%20%20%20%20When%20this%20happens,%20I%20also%20see:%0A>%20%0A>%20%20%20%20gnome-session%5B2003%5D:%20(gnome-shell:3042):%20Gjs-WARNING%20**:%20JS%20ERROR:%20TypeError:%20parent%20is%20null%0A>%20%20%20%20gnome-session%5B2003%5D:%20onTrayIconRemoved@/usr/share/gnome-shell/extensions/topIcons@???@gmail.com/extension.js:115%0A>%20%0A>%20%20*%20Another%20piece%20of%20logs%20that%20we%20(sometimes)%20see%20when%20the%20problem%20happens:%0A>%20%0A>%20%20%20%20gnome-session%5B30034%5D:%20(gnome-shell:30263):%20Gjs-WARNING%20**:%20JS%20ERROR:%20TypeError:%20parent%20is%20null%0A>%20%20%20%20gnome-session%5B30034%5D:%20moveToTop@/usr/share/gnome-shell/extensions/topIcons@???@gmail.com/extension.js:135%0A>%20%0A>%20%20%20%20gnome-session%5B29844%5D:%20(gnome-shell:30074):%20Clutter-WARNING%20**:%20Attempting%20to%20add%20actor%20of%20type%20'ShellTrayIcon'%20to%20a%20container%20of%20type%20'ShellGenericContainer',%20but%20the%20actor%20has%20already%20a%20parent%20of%20type%20'ShellGenericContainer'.%0A>%20%0A>%20%20*%20The%20https://github.com/wincinderith/topicons%20fork%20has%20changes%20in%0A>%20%20%20%20areas%20that%20might%20be%20relevant%20to%20the%20problems%20we%20see.%20We've%20not%0A>%20%20%20%20tested%20it%20so%20far.%0A>%20%0A>%20Is%20there%20any%20information%20you%20need%20from%20us%20to%20debug%20this%20problem?%0A>%20I'm%20sure%20those%20of%20us%20who%20see%20this%20problem%20would%20be%20glad%20to%20test%0A>%20patches%20aimed%20at%20fixing%20it.%0A>%20%0A>%20Please%20don't%20hesitate%20forwarding%20this%20message%20to%20anyone%20you%20think%0A>%20might%20want%20to%20give%20us%20a%20hand.%0A>%20%0A>%20Cheers!%0A>%20--%20%0A>%20intrigeri%0A>%20%0A>%20 "Reply to this message"){kind=icon}
