-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
[Bug Report] No tray icon visible on elementaryOS 5.1.2 #17
Comments
Just to confirm, did it occur every time or just one time bug? because it happened to me on Ubuntu 18.04 but when I closed and reopened it, it was all fine. |
It's always so. |
It is issue in Implementation of Elementary OS tray Icon support and its Electron Implementation. See details here (electron/electron#22550 or electron/electron#10427) So I will wait for electron to solve this issue and then if it is still not resolved in WALC after electron or Elementary solves it then I will check at my end.
AppImage removed the support for Desktop Integration(See release notes). I might be able to fix it in next version with some alternate implementation but meanwhile you can create a Desktop Integration file that will allow you fix it. (Follow this link and skip to step 5 ) |
I use many Electron apps and all of them are working fine on elementaryOS in regard to the tray icon so it's hard for me to believe that this is an Electron issue.
|
They might be using a different version of Electron and Electron-builder. I am using latest versions of both and don't want to revert back to older versions. |
Thank you for your time and effort. |
AppImage Desktop Integration has been integrated manually again in latest release (v0.1.6) You may download the updated AppImage and you are good to go. |
As far as Tray Icon for elementary OS is concerned that I will try to fix in upcoming release. |
Confirming working desktop integration. Thank you @cstayyab |
No tray icon visible while all other apps, native and electron, have visible tray icon.
Cheers.
The text was updated successfully, but these errors were encountered: