Tray icon goes away after locking/unlocking the screen

[fabiomargarido]

• I have searched open and closed issues for duplicates

---

Bug Description

When using the `--start-in-tray' option, everything works as expected but the systray icon disappears after locking the screen and unlocking again.

Steps to Reproduce

1. Start signal-desktop with the --start-in-tray option;
2. Wait for the app to start and verify that the systray icon works as expected;
3. Lock the screen (Super+L on Ubuntu);
4. Unlock the screen.

Actual Result:

The systray icon is gone but it is possible to see that the signal-desktop process is still running in the background.

Expected Result:

The systray icon is still shown and continues to work as expected.

Platform Info

Signal Version:

1.32.1

Operating System:

Ubuntu 18.04.0 LTS

Linked Device Version:

4.57.2

[majkeldzordan]

[N0GX]

I am seeing this as well after updating to v1.32.2 this morning.

[scottnonnenberg-signal]

@majkeldzordan @N0GX This is the bug tracking that issue: #4085

[mandree]

On Fedora 31 Linux with GNOME 3 (3.34) desktop and TopIcons Plus as packaged by Fedora, I do not currently get the tray icon (neither in the panel nor in the dock), but I do get it with the Plasma (KDE) desktop. Some other icons (keepassxc) are also going missing on GNOME, so it may be an issue of GNOME... GNOME is notorious for breaking extensions and application icons every half year with each and every new release.

@fabiomargarido what desktop are you running on your Ubuntu?

[fabiomargarido]

@mandree I'm running Gnome 3.28.4, the default for Ubuntu 18.04.

[mandree]

See #3974 for more details, and for GNOME, specifically this comment: #3974 (comment)

[bungabunga]

@scottnonnenberg-signal there seems to be a solution for this: zulip/zulip-desktop#910

[mandree]

@bungabunga that seems to be more a workaround than a real solution, but it's not clear if GNOME or chromium/electron need to fix this. Electron are pointing fingers at GNOME and Chromium, see ubuntu/gnome-shell-extension-appindicator#220

[bungabunga]

@mandree can this workaround be implemented Signal-desktop-wise so that we don't have to wait for Electron, Gnome and Chromium to make up their minds?

[mandree]

It makes more sense to put massive pressure on GNOME for constantly breaking things and ask Chromium if they can help adjusting to the ever-changing GNOME environment, than fix hundreds of downstream users.

[tribut]

But this is a regression in Electron/Chromium, no? This worked on the same version of GNOME before the update of Electron? How is it GNOMEs fault? Haven't they been disabling extensions when the screen is locked since forever?

[scottnonnenberg-signal]

Seems to be a chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1042098

[mandree]

To me that's not so clear... https://bugs.chromium.org/p/chromium/issues/detail?id=1042098#c11 and GNOME 3 is the desktop that has been reinventing everything every other year.

[loxK]

Please implement the workaround in the meantime it is fixed upstream.

[bungabunga]

it seems there's gonna be a fix in electron.

[mandree]

it seems there's gonna be a fix in electron.

https://github.com/electron/electron/releases/tag/v9.0.3 was released with the fix, but as of today, this release has not yet hit the servers in a manner that yarn would accept it.

[mandree]

I've rebuilt Signal with Electron 9.0.3, which resolves this issue.
@scottnonnenberg-signal - please rebase Signal onto Electron 9.0.3 or newer.

[loxK]

It is solved with the new version release.