System tray not visible on some Linux distributions #350
Comments
|
Steam has had the same issue since at least January 2013 and their approach was to substitute the close action with minimize and utilize an environment variable to enable closing to the sys tray for users who know it will work on their system. |
|
Thanks for the hint! |
|
@ManfredKarrer System tray still not supported? Should I open a new issue? Ubuntu 16.04 |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
ripcurlx
changed the title
|
This problem is still current. The system tray is not visible since years for me, would be nice to have this fixed because it's bad UX. Additionally, the tray icon appear as an opened page on Debian, forcing me to right click the main icon, choose the actual bisq interface, and finally click to visualize it. I also get a "the system tray is not supported on this system" warning every time my laptop turns of the screen to save energy. It's very annoying.
The problem shows in both Debian Sid and Buster (Gnome) and was present in Stretch. |
Update the gradle dependency to JavaFX 14. This brings to Bisq the latest JavaFX fixes and improvements, especially in the areas of UI performance, memory management and security. JavaFX can be upgraded independently of the JDK used to build the application, so this change is modular and does not affect other parts of the build process. Related / likely related to: bisq-network#350 bisq-network#2135 bisq-network#2509 bisq-network#3128 bisq-network#3307 bisq-network#3308 bisq-network#3343 bisq-network#3430 bisq-network#3657 bisq-network#3677 bisq-network#3683 bisq-network#3686 bisq-network#3786 bisq-network#3787 bisq-network#3892 bisq-network#3917 bisq-network#3918 bisq-network#3936
Update the gradle dependency to JavaFX 14. This brings to Bisq the latest JavaFX fixes and improvements, especially in the areas of UI performance, memory management and security. JavaFX can be upgraded independently of the JDK used to build the application, so this change is modular and does not affect other parts of the build process. Related / likely related to: bisq-network#350 bisq-network#2135 bisq-network#2509 bisq-network#3128 bisq-network#3307 bisq-network#3308 bisq-network#3343 bisq-network#3430 bisq-network#3657 bisq-network#3677 bisq-network#3683 bisq-network#3686 bisq-network#3786 bisq-network#3787 bisq-network#3892 bisq-network#3917 bisq-network#3918 bisq-network#3936
|
the error popup removed in #4874 |
|
Closing as complete. |
|
my comment refererd only to removing the error message "The system tray is not supported on the current platform" |
|
It seems to me that the icon is misplaced on Xorg but it's at the right place on Wayland Wayland (correct): Xorg (icon in top left corner but clickable at the correct position in the top bar at the right side) |
|
This might improve when switching to the latest Java runtime and packager in #4242. |
|
Should be fixed in the most recent release (v1.6.4). |
"First start was ok (testnet synced, Tor connection established) but 2rd and follow attempts failed with error messages stating that running few Bitsquare at the same time is impossible. I guess when I click on Close button of running Bitsquare, it doesn't close, but minimize to systray instead. But the problem is that seems like Java using xembed systray icons, and Plasma 5.4 (DE of Kubuntu 15.10) is phasing out dependency on X11 technologies/protocols, including xembed (because DE developers implementing support for new protocol Wayland for communication between applications and display server, they keep only functional that works with this new protocol, and xembed happen to work only with old one - X11; also there is number of issues with xembed). So xembed systray icons doesn't work for me and when I click close on Bitsquare window I thought it's really closed while in fact it continue running (still not sure if it's really the case because I doesn't know how to check this).
If I was right, then issue in Java, that using xembed directly, instead of relying on toolkit (in case of Java on Linux it's GTK3, for example save dialog in Bitsquare is GTK3-style) for interaction with DE systray. There is more details.
Also libappindicator support could be implemented in Java directly, but not sure if this necessary, if they could use implemented GTK3 libappindicator support.
Also as far I know other DE is also phase out xembed support, for example Gnome Shell."
-> We deactivate that "keep running in background" behaviour for the moment until those issues are solved. Need a information alert also to tell the user about that behviour.
The text was updated successfully, but these errors were encountered: