With certain Linux Desktops: Systray icon bug #2123
Comments
|
honestly, we do not really have an idea. I think this is a support topic rather than a bug which you should maybe ask on the forum. |
|
I opened a forum post: http://forum.owncloud.org/viewtopic.php?f=14&t=23376&p=68428#p68428 |
You can by the way run |
|
@guruz: There is nothing in the log files, related to this problem. But I made some progress on this. After completly disabling my Notebook screen with suddenly the ownCloud sync icon appeared. But not in the systray. It appeared in the top left corner of the screen. Really weird. Maybe this problem is related to the output device. ownCloud sync client may not check the active / used / actual screen. |
|
I also have the same problem. |
|
Unfortunately you can do nothing. |
|
I'm also running Debian Jessie + XFCE and have this problem... |
guruz
changed the title
|
Debian Testing + XFCE4 4.10.1 |
|
As the settings dialog can't be opened by clicking on the icon in the systray, is there an alternative way to open it? |
|
Debian unstable + Gnome 3.8 (but not for 3.12) |
|
Acording to debian bts 750847 this is maybe related that the file owncloud.png, state-offline.{png|svg}, state-error.{png|svg}, and state-ok.{png|ok} are not shipped with the package. |
|
I built the newest version (1.7.0~beta1+dfsg-2) from http://anonscm.debian.org/cgit/pkg-owncloud/owncloud-client.git/ with BUILD_WITH_QT4=ON and the icon appears and changes correctly. So i guess it is related to QT5. But this workaround does not work perfectly: I noticed that the first icon which is displayed is the same as from the app to the right in the systray (less than half second). |
|
@lupowolfi Yes, tray not showing up with Qt5 not working is a known issue related to Qt. Qt5 currently only supports the xembed-based system tray. |
|
@danimo Thanks for pointing that out. As far as I unterstood this issues should be resolved not later than the upcoming release Qt 5.4. |
|
@lupowolfi With my information, the issue isn't solved with the upcoming Qt 5.4 for XFCE and/or Gnome. If you have any patches to solve it, i would be very interessed in...The base of the problem is properly QTBUG-34364. The base of the problem is that the xembed is thrown out ( and deprecated) by mutlitple DEs and the new system isn't included till now. Gräßlin showed a workaround to setup a xemed systray, but this is only a temporally solution. |
|
@hefee No, unfortunately I don't have a patch. I was just referring to the same source as you, but wasn't aware that his blog entry addresses only KDE. |
|
A work-around (and start of the solution) is using sni-qt. It is a Qt plugin enabling support for the new systray spec, Status Notifiers/indicators. See #2023 (comment) for info - you'll get it working just fine, see screenshot on my Plasma 5 laptop ;-) |
|
Is there an alternative way to open owncloud-client? There seems to be none... |
|
@shellshocker Did you try @jospoortvliet 's solution with qt-sni? |
|
qt-sni seems to be unavailable on Debian |
|
@danimo: There is no such default package on Debian. I could install the Ubuntu package. But this is only a workaround. |
|
@shellshocker not yet. You might want to open an enhancement request. Thx. |
|
After upgrading Debian Jessie packages last night, the icon still does not appear. But there is a hidden placeholder where you can klick on. Some progress. :-) |
|
After upgrading Debian Jessie with the new packages: ... icon is now visible! For me it's fixed. Thank you! |
|
WTH is 1.7.0~beta1+really1.6.3+dfsg-4? @hefee, can you shed some light? |
|
@danimo: Have a look: https://packages.debian.org/jessie/owncloud-client ;-) |
|
Have a look at http://metadata.ftp-master.debian.org/changelogs/main/o/owncloud-client/unstable_changelog The issue wasn't fixed, but they are building the package with qt4 instead of qt5 |
|
well by accident I uploaded the 1.7.0 lupowolfi is right, for debian we switched back to build with qt4 for the upcoming stable release, to have a working version for debian. |
|
I'm going to throw in my experience here. I'm trying to use the ownCloud Client on Bodhi Linux 3.0. It uses e19 with Xembed support removed (it will be gone from e20 entirely). Consequently, it's very hard to use ownCloud in Bodhi 3.0 without installing something like trayer or stalone tray (I have no idea how to give my systray dimensions in x-notation!) My understanding is that Xembed is a dying protocol. Hopefully I'm not offending anyone by saying this, but might ownCloud be coded to use libappindicator instead sometime soon? |
|
@jbiddy Qt 5 supports this and it works. You might have to install qt-sni - depending on your distribution. Bodhi should offer that, if it doesn't - do a feature request to them. So, if you have Qt 5 and ownCloud Client 1.8 and a up to date distribution, this works perfectly fine. I'd close this issue - if it doesn't work it is a distribution problem. |
@jospoortvliet: what you mean with with current qt5 and up to date distro? |
|
@hefee if you use GNOME 3.x, the 'old' systray should work, I'm quite certain the ownCloud Client supports Xembed still as it works on my desktop too. It is possible that GNOME Shell has dropped that - no idea, to be honest. There is also a new systray specification that is supported by Unity and Plasma 4 and 5 and mentioned by @jbiddy which is supported by the ownCloud client. You can check if your Qt version has support for it by looking for libsni-qt.so - for me it is in Unfortunately the GNOME developers invented a third wheel. Ask them to support Status Notification Items... http://www.freedesktop.org/wiki/Specifications/StatusNotifierItem/ If it is already supported in GNOME Shell, then either Qt SNI is broken, not installed (look for a sni-qt package) or the SNI implementation in GNOME is broken. |
|
Qt 5.5 should now have support for the dbus protocol |
|
@ogoffart but that's not really helping, is it? It will be a solid two years before Qt 5.5 has arrived on a majority of Linux Desktops. |
|
@ogoffart Would it be an option to ship Qt with the oC client on Linux like it is done on Windows and OS X? ;-) |
|
@guruz why are you asking me that? |
|
@ogoffart he's screwing with you. |
|
I'm using Linux Mint (Ubuntu based) with Cinnamon window manager (Gnome based). The ownclowd-client icon does not appear on startup, while the synchronization is running and I can see the process. Restarting owncloud is a workaround for me. Type into Terminal: owncloud-client 1.5.0+dfsg-4ubuntu1 |
|
Owncloud version 2.0.1 |
|
I am having this issue as well: After logging in, there is no icon for the ownCloud client, just a window popping up informing me about the sync state. I just killed the owncloud process and started it again, which made the icon appear. This is with Qt 5.5 on Debian testing, using Cinnamon as my desktop. |
|
@RalfJung sounds like a timing issue: cinnamon is too slow letting the systemtray be started, ownCloud is then already up and running. File a bug with Cinnamon to delay starting apps until they are sure the systemtray is available... |
|
GNOME also has a rather broken systemtray so that might be the problem, rather than anything in ownCloud @pecuna |
|
We are using the QSystemTrayIcon and it gets better with newer Qt version. This particular bug report contains information about many desktop and many qt version and is old and no longer usefull. |
|
This is still a problem. Using latest available Owncloud Desktop sync client v2.2.0 build 1605 on Ubuntu Desktop 14.04 x64 LTS. Edit: FYI, installed the Mate DE yesterday, seeing the same problem. Waiting to see if the regression-fix will help! Edit2: FWIW, I just noticed the same thing on the latest CentOS 7 x64. I use the Mate DE there too. |
|
@adrianvg This is a regression in the v2.2.0 builds (as they have been build against Qt5 accidentially). We will fix this in the coming days. |
Hi folks,
I'm using Debian package owncloud-client (1.6.2+dfsg-1) on an Debian Jessie System with XFCE.
Unfortunately I cannot see the systray icon.
Notification Area panel is installed (http://docs.xfce.org/xfce/xfce4-panel/systray). I can hide/unhide the icon there but nothing is visible in the systray.
When is start owncloud from the terminal there is no output. It's running fine.
Any ideas?
The text was updated successfully, but these errors were encountered: