ownCloud Client system tray icon integration broken

Status changed to 'Confirmed' because the bug affects multiple users.

Copying Olivier's comment from upstream bug:

I was able to locate the problem. The problem is in ubuntu's "appmenu-qt5" and is a bug that cause our call to QSystemTrayIcon::isSystemTrayAvailable() to remove the icon.

That's because appmenu-qt5 seems to assume there is only one QPlatformSystemTrayIcon while there can be one per QSystemTrayIcon. in particular, QSystemTrayIcon::isSystemTrayAvailable creates a temporary one, and when it gets distroyed, it unregister the dbus object for the existing systray.

Adding the appmenu-qt5 task accordingly.

I reported the bug to appmenu-qt5: https://bugs.launchpad.net/appmenu-qt5/+bug/1574699

Workaround in owncloud https://github.com/owncloud/client/commit/0da2adcbe02eb9499e90622ca60a726ba75d0188

Status changed to 'Confirmed' because the bug affects multiple users.

This bug was fixed in the package owncloud-client - 2.1.1+dfsg-1ubuntu2

---------------
owncloud-client (2.1.1+dfsg-1ubuntu2) yakkety; urgency=medium

  * workaround-systemtray-bug.diff: Don't call isSystemTrayAvailable, it
    hides the systemtray. (LP: #1573639)

 -- Timo Aaltonen <email address hidden> Thu, 28 Apr 2016 20:30:38 +0300

when it is released?

Any chance of an SRU into 16.04?

it's already in the queue since thursday

Hello danimo, or anyone else affected,

Accepted owncloud-client into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/owncloud-client/2.1.1+dfsg-1ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Verificación realizada desde propossed.

el paquete ahora funciona como se esperaba.

Gracias!

Proposed verification conducted from.
the package now works as expected.
Thank you!

The proposed package fixed the bug. Thanks!

I can also confirm the proposed package works nicely.

The new package works for me, thanks !

The update from the proposed repository fixes the problem for me.

After apt-get update and apt-get dist-upgrade my Ubuntu 16.04 still has the problem.

@ Marco Righi : you have to activate to proposed repo before upgrading.

It's working ok with proposed package .
If anyone wants to update only the owncloud-client package (and dependencies) you must first enable proposed repo (Unity Settings > Software & Updates > Last tab) and reload package info.
Then force the upgrade only of owncloud-client and needed libraries by: sudo apt-get install owncloud-client
You can now safely disable proposed repo waiting for a new update on main Universe updates repo.

Hope it helps.

+1 Working again with proposed package. And great tip, Diego / #19. Thanks!

Tested 2.1.1+dfsg-1ubuntu1.1 from proposed repo.
Works OK.

It's almost all ok, indeed. After resume from suspend or hibernation the client results disconnected from the net, while wireless is on and firefox, thunderbird and dropbox keep on working, so I need to close owncloud and re-open. (the client from owncloud repos/ubuntu15.04 didn't have this issue).

Luca, this is not related to this bug, which is only about the indicator icon. Please create a new bug regarding your issue--it can be troubleshooted and discussed there.

Thanks @nhaines : there was this bug https://bugs.launchpad.net/bugs/1572321 filed yet.

The update from the proposed repository fixes the problem for me.

The update from the proposed repository fixes the problem for me too.

don't close bugs manually, the package hasn't transitioned to -updates yet

This bug was fixed in the package owncloud-client - 2.1.1+dfsg-1ubuntu1.1

---------------
owncloud-client (2.1.1+dfsg-1ubuntu1.1) xenial; urgency=medium

  * workaround-systemtray-bug.diff: Don't call isSystemTrayAvailable, it
    hides the systemtray. (LP: #1573639)

 -- Timo Aaltonen <email address hidden> Thu, 28 Apr 2016 20:30:38 +0300

The verification of the Stable Release Update for owncloud-client has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package appmenu-qt5 - 0.3.0+16.10.20160628.1-0ubuntu1

---------------
appmenu-qt5 (0.3.0+16.10.20160628.1-0ubuntu1) yakkety; urgency=medium

  * Fix for creating two or more system tray icons. (LP: #1573639,
    #1574699)

 -- Dmitry Shachnev <email address hidden> Tue, 28 Jun 2016 10:48:58 +0000

Memory 3,8 Gb. Ubuntu 16.10 up to date as of today. Desktop is Flashback with Nemo. Appmenu-qt5 is not installed. Indicator-applet-complete 12.10.2+15.20141127.2-0ubuntu1, indicator-application 12.10.1+15.20150128.2-0ubuntu1.
Indicator-applet gets mad after some time. At the beginning of the session, the indicator appears, with ownCloud client (2.2.2+dfsg-1). It is possible to work while ownCloud is synchronizing. After two or three hours work, everything slows down to nearly freezing. Is seems impossible to get the ownCloud menu from the indicator to quit ownCloud. It takes a long time to even get a terminal and start top to see indicator-applet at 100 % CPU. Killing the owncloud process takes a very long time after the kill command. Then the indicator gradually calms down and it is possible to go on working.

Dominique: you are experiencing bug 1635577, it is already fixed in Ubuntu 16.10 updates. Please upgrade owncloud-client to version 2.2.2+dfsg-1ubuntu0.2.