-
Notifications
You must be signed in to change notification settings - Fork 6
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
No tray icon #18
Comments
Do you mean I get the following on my systems (Debian Bullseye and Pop!_OS 19.10):
|
Sadly, I am using GNOME exclusively, so interactions with the tray icon aren't something I can test and fix myself. |
It does start and it keeps running, but it does not show an application window or a tray icon. I ran |
So you're not seeing the window shown on the screenshot above? Even after ensuring no leftover process is running in the background? |
I see the same behaviour on:
|
No, I do not see the video from the screenshot after starting Zulip. This can be explained by I later changed
|
Then, you won't mind if I retitle this issue to remove said confusion.
Looking at other Electron-based chat clients (RocketChat, Riot, Discord), it seems that support for tray icons is a headache. Could you try running the flatpak with |
At the time I wrote the title, I did not yet know whether Zulip's behaviour might have changed to no longer support minimisation to tray.
Same behaviour: Window only appears when |
Thanks for digging this up! See-Also: https://bugs.chromium.org/p/chromium/issues/detail?id=419673 |
Upstream claims this is fixed with version 5.3.0: zulip/zulip-desktop#936 (comment) |
Seems to work here. Can anyone confirm? |
I am at 5.4.2 and the issue is fixed on both my Gentoo and my Fedora system. |
Since updating to Zulip 5.0.0 (#13, #14), after startup no window appears and no tray icon is shown. #10 and #17 did not fix this. It does not matter whether I start Zulip from KRunner / KDE Plasma or from the command line. With Zulip 4.0.3 this still worked: After startup a tray icon was shown.
The text was updated successfully, but these errors were encountered: