Comment 10 for bug 1712866

Revision history for this message
JaSauders (jasauders) wrote :

Thank you, developers, for your time regarding this issue. I'd like to chime in with my experiences following the proposed patch. Full disclosure: I did not enable proposed. I just downloaded the .deb generated for the appindicator-17.10.2.deb package and installed it. Afterwards, I rebooted and began to tinker.

The appindicator seems to "mostly work", at least with the apps I tested. These apps were Telegram, Quassel-Client, Nextcloud-Client, Dropbox, and VLC.

Quassel, Nextcloud, and VLC work fine. They come back each time (so far in my testing) when unlocking the screen. This success is true for both typical locks/unlocks along with suspend/resume. The only thing worth noting about this behavior is that the order of the icons seems to change every time. It's almost as if they are ordered by their response speed upon the session unlocking again. It varies, it's not a big deal, but I think it's worth noting, however they *do* come back -- that's an improvement for sure.

The story changes with Telegram and Dropbox. With ease I can trigger the disappearance of the Telegram tray icon. One suspicious thing worth noting here is the Telegram tray icon is very undersized. This is entirely speculation, but is it possible Telegram is excluded from this patch working because of this undersized icon issue? I recall seeing a bug report regarding very small icons in the appindicator tray...

Dropbox failed to come back approximately 3/4 of the time. On some tests, Dropbox did come back, but an easy majority of the time Dropbox was no where to be found upon resuming. I can confirm via system monitor that Dropbox is still indeed running, though.

If there are other patches in proposed that might help with this, then I apologize ahead of time regarding the fact that I simply downloaded the appindicator.17.10.2.deb package from launchpad. Otherwise, while there's some definite improvements, perhaps this behavior is the sign of a lingering issue.

Again, thank you devs, for your time and hard work. :)