-
Notifications
You must be signed in to change notification settings - Fork 22
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
Nextcloud Tray Icon missing on Gnome Wayland sessions #21
Comments
After further testing this behavior appears to not be reliable. Maybe it wasn't the new socket access that made a difference. Even in the same session the nextcloud-client tray icon may appear the first time nc-client runs but not on any subsequent runs (after you exit the app on your own on the first time). Moreover they tray icon exhibited different patterns of appearing and not appearing between the two users on my installation ... |
Disabling |
I've check the icon problem, and this is not related to Wayland, however it still is a icon problem. Other related issues: |
any updates here? |
Still having this issue |
I'm on X11 and I have this issue too. |
I think this is not an official repository since no developer replied to it. Does anyone realized how to fix it? |
No, I started using the one that is bundled in Fedora, which fixed most of the issues for me and has better integration with Nautilus. |
i have that also. it's a useless icon. you aren't notified if you're syncing or not. if you install the real app there is a green checkbox if it's all synced or a red x if there is a probem. this three dots doesn't tell us anything. can we get a better icon? |
@kollienne Could you provide more details to use this workaround ? |
Looking at lines 4900f. https://buildbot.flathub.org/#/builders/5/builds/13664/steps/7/logs/stdio it seems to me that the tray icons are not exported. |
I found another interesting difference: the flatpak build sends a concrete icon name (e.g. "state-offline") as property of the dbus object |
This didn't work for me on openSUSE Aeon (Gnome). Currently I am unable to get the icon working properly with the Flatpak version of Nextcloud Desktop. I was able to install the RPM package version of Nextcloud Desktop, but I would like to use the Flatpak version once the icon issue is fixed. |
Here is some context with the issue for anyone wanting some: Nextcloud is using QSystemTrayIcon, its documentation stands:
So it is likely using the D-Bus status notifier system which means that the rendering is happening outside of the sandbox. As such, it can't know where the icons are located as only the application icon is exported. There is no real way out that I can think of. I would really recommend using the interface exposed in libcloudproviers in your system instead, it should already be included in GNOME Files (Nautilus). |
This is an ugly workaround for flathub#21. It prevents passing an icon name over DBus to the host environment where the theme is not known. Instead it enforces the use of the PixMap.
This is an ugly workaround for flathub#21. It prevents passing an icon name over DBus to the host environment where the theme is not known. Instead it enforces the use of the PixMap.
I was testing the nextcloud-client flatpak in Fedora SilverBlue 32.
I noticed that on the Wayland session I was not seeing the nextcloud tray icon. My system has installed the
gnome-shell-extension-appindicator
as a layered package to help facilitate this. I also tested the element flatpak that had a working tray icon. Comparing the settings from element and that I was getting a system tray icon in a Gnome on Xorg session I was able to resolve this by adding thesocket=fallback-x11
permission.More over I noticed from element's settings that only
org.kde.StatusNotifierItem-2-1=own
was needed instead iforg.kde.*=own
for the indicator to show up.Here are some information from my set up for reproducibility of the results.
P.S.1: Flatseal was an awesome software to help me look into this.
P.S.2: Happy to make a PR for this if maintainer(s) are willing to implement those changes.
The text was updated successfully, but these errors were encountered: