-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Impossible to interact with the tray icon and thus to quit the app (desktop version based on electron) (and weird icon issue) #3133
Comments
OK, I’ve partly fixed it, the issue was the missing |
Yep, this does sounds like problems caused by the new tray icon. I suspect it's not allowing interaction with the tray icon which means you don't get the menu / app focusing behaviour when you click the tray icon. What desktop environment are you using? Can you interact with other tray icons in your desktop environment, and if so in what way? |
Another user reported the same issue, on Plasma 5 too. |
I had the same issues on Plasma 5. Installing the I am now able to interact with the tray icon using the right mouse button. Unfortunately this also introduced an issue rendering the icon: When In case this is a packaging issue: I built the Riot Desktop package using the build script from AUR, which currently uses version 0.9.7 of riot-web. |
Hum indeed, using libappindicator-gtk3 allows to interact with the icon, but then its rendering is wrong. |
I fixed this for myself on KDE Neon (Ubuntu + Plasma) by using equivs-control to make a dummy libappindicator1 and installing it |
@t3chguy can you describe more detaily how to fix this problem on Ubuntu with KDE5? |
@MurzNN install https://riot.ovh/_matrix/media/v1/download/riot.ovh/RrwsYrxMcIyHWjfhpxxWtvEN over libappindicator1, this is a dummy package I made using |
@t3chguy thanks, it helps! At now tray icon looks and works well on Ubuntu 14.04 with KDE 4.14! Also solves the problem on Ubuntu 16.04+ with KDE5 too. |
Can confirm that removing libappindicator3-gtk makes the icon look not-zoomed in but the resolution of the tray icon is very bad and looks pretty ugly it's current form. |
I confirm too that removing libappindicator3-gtk now results in a working tray icon but very blurred. At least we can interact with it and the notification badge works. |
Got same issue - icon is a purple box (and left click does nothing, not sure if that is correct behaviour). @lazToum's workaround seems to work (at least when launching from a console), I'll modify the autostart file and hopefully it will fix the issue for good. |
@lazToum workaround solve the problem only with icon size, but left click on tray icon is still broken (shows |
would having ayatana-appindicator help in anyway instead of libappindicator ? https://github.com/AyatanaIndicators/libayatana-appindicator. See https://wiki.debian.org/Ayatana/IndicatorsTransition |
It's not something we get control of, it's something electron-builder specifies |
@lazToum where to set this? |
@akontsevich run that command: XDG_CURRENT_DESKTOP=Unity riot-desktop |
@ChrisP4 it solves only icon look but does not fix tray behavior on mouse click. Also DE session manager does not store exact app command to rerun and icon still ugly on next DE start on session restore. |
Enlightenment 22.4 |
This is working properly for me now in KDE Plasma 5.15 with Riot 1.0.1. Can anyone confirm? |
@Pointedstick, what works for You? For me in KDE Plasma 5.15 with Riot 1.0.1 works only with right mouse click - opens context menu, left mouse to show main window does not work. |
Both works for me with Plasma 5.15.1 and Riot 1.0.1 on Arch Linux |
With or without appindicator? |
Probably they does not use libappindicator. Does not work for me with libappindicator1 - forced to use for acestreamengine. Many distributions use patched libappindicator, hope openSUSE will patch or replace it as well. |
I do not have appindicator installed (only the gtk2 version) |
@akontsevich Then your issue is https://bugs.archlinux.org/task/59652. |
The correct way to have system tray icon properly working is to use Electron 5.0 or later and have libappindicator installed (but making sure that it doesn't use any patches that actually break it, like it's the case with Arch right now). Also, the app itself shouldn't have any special behavior when it detects KDE, like scaling down the icon to 22x22 - this was "helping" with old buggy Electron (or very old KDE), but now it just makes the icon blurry. There were multiple bugs in various places that were hindering the usability of systray icons in Electron apps, so you have to make sure all of these pieces are covered. |
|
@532910 Your issue seems to be separate and I'd suspect a bug in Enlightenment there. Do other, non-electron apps that use libappindicator work with E? |
xfce4-panel: no icon |
Neither trayer nor xfce4-panel seem to support indicators, so as soon as there's any registrar running it's expected that there won't be any icon displayed there, as it won't fallback to XEmbed (and even if it fallbacks, it will be shown only in one panel at a time). [edit] With xfce4-panel seems like you can use xfce4-indicator-plugin |
Are people still experiencing this? |
It works for me both with and without libappindicator installed (though with libappindicator, both right and left click open the menu, while without it right click is the menu and left shows/hides element). |
Thank you for opening an issue. Unfortunately I wasn’t able to reproduce it. If you keep experiencing this defect, please update your description with steps/screenshots/video/more details and add a comment with @weeman1337 to let me know that it’s ready to be reopened. |
When I start riot, I’ve got a strange behaviour. I either start it from within a terminal or using the desktop entry added by this .desktop file.
When starting a first time, it doesn’t work. A window is added to task manager if using the desktop entry, but then disappears without anything else happening; while using the terminal results in this:
And then nothing happens, I have to
Ctrl+C
to get out of it.Then, on a second attempt, seems become very weird. If the previous attempt was from the terminal, then it doesn’t work as above. However, if the previous failed attempt was from the desktop entry, then it does work whether trying from the terminal or the desktop entry.
After this, it goes back to square one. So, I have a work-around for now (just launch it twice from the desktop entry), but this is far from ideal and could confuse people if I’m not the only one affected.
The text was updated successfully, but these errors were encountered: