-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tray icon no longer working on Cinnamon 4.6.x (Linux) 1.34.0-beta.3 #3974
Comments
Apparently Electron v8 now uses |
Similarly on Ubuntu 19.10. Since 1.32 beta2 (but not beta 1): tray icon appears when I start the app, but after I turn off the screen and later turn it on again it's gone. |
@bungabunga Is the icon perhaps very small? This appears to be related: electron/electron#21445 |
no, the icon is ok when visible and after turning off the screen completely gone. i can only bring it back if i turn off Signal, and turn it on again when the screen is on. |
btw, there is no tray icon on Windows10 with 1.31.0 anymore too. |
@luciash When was the last version it worked for you? How are you enabling the tray icon, exactly? |
This bug seems applicable: electron/electron#22443 |
Last version was the version before 1.31.0 - it got auto-updated and since then nomore systray icon when closing the Signal desktop app. I had it setup for several versions on closing window it was minimized to the systray - IIRC it was a setting in the app preferences. I did not do any tricks... But now it seems it is gone from there. |
EDIT: Correction. This is NOT a problem in Kubuntu. The default launcher simply doesn't expose the --use-tray-icon options. Manually launching with the options corrects the issue. |
See this issue linuxmint/cinnamon#9176
|
Same problem here on lubuntu 18.04. |
This also exists with Linux Mint MATE edition, which does not use Cinnamon. It can be worked around by opening |
On xfce (ubuntu 18.104) at least, switching to |
Same here on Gnome 3.22, Debian Buster. |
Same here, with cinnamon 3.8.9 |
Is there a work around for Gnome? Issue exists on Manjaro as well. |
Note that v1.32.x updated Electron from 6.x to 8.x. It does make sense that notifications are now using a more modern system. Please let us know what you find. |
As @ondondil said, enabling support for indicators solves the problem on linux mint / Cinnamon, Make sure to restart the DE |
I'm on lubuntu (lxde) 18.04. |
The indicator method does not fix the issue on my end. |
This issue also affects me. Ubuntu 19.10. Is there any workaround? |
I've bisected this on Fedora 31, and as expected and reported by Scott, got
and the first release after that was For GNOME users, see if your distribution provides |
Enabling indicator support in Cinnamon 4.4.x more or less fixed the issue but this has been removed in 4.6.x. (There appear to be a number of issues remaining with Cinnamon's implementation and not necessarily related to Signal or electron per se.) |
See my solution: |
problem persists on other desktop environments than cinnamon, for example lxde. |
I can confirm this solves the problem for me on Mint 19.03. |
Here also with Linux Mint 19 and doesn't solve the problem. |
Same in Mint with Mate as DE |
Cinnamon 4.6's new XApp framework appears to support libindicator-style tray icons (by adding the XApp Status Applet to a panel). Bugs seem to be upstream and not related to signal-desktop/electron per se. |
I just got the icon working on my lxde using https://git.sr.ht/~steef/snixembed |
This Work for me with cinnamon 4.6.6 |
Bug Description
Steps to Reproduce
Actual Result:
There is no tray icon in the system tray.
Expected Result:
Tray icon appears in system tray indicating unread messages.
Platform Info
Signal Version:
1.34.0-beta.3 (problem was also seen in 1.32.0-r2 but not 1.32.0-r1)
Operating System:
Linux version 5.5.5 DISTRIB_ID="Gentoo"
Linked Device Version:
4.60.4
Link to Debug Log
https://debuglogs.org/25d8b7248134cc0550c14431512bf6be5564199c1cafebbc5989b4b9c2f7c9ac
Cinnamon references:
linuxmint/cinnamon#9328
linuxmint/cinnamon#9176
linuxmint/xapp@0a27c6a
The text was updated successfully, but these errors were encountered: