syncdaemon restarts every second when File Sync is disabled

Bug #766344 reported by Gediminas Paulauskas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubuntuone-client

I have disabled File Sync in Ubuntu One Control Panel, as there are no files in ~/Ubuntu One.

Then I noticed my system runs very slowly, load avg is > 1, and laptop fans are constantly spinning.

Turns out, there is a syncdaemon process eating up to 100% of CPU, and it cannot be killed because it dies and is restarted every second.

~/.cache/ubuntuone/log/syncdaemon.log

2011-04-18 17:42:02,992 - ubuntuone.SyncDaemon - WARNING - Files synchronization is disabled.
2011-04-18 17:42:03,901 - ubuntuone.SyncDaemon - WARNING - Files synchronization is disabled.
2011-04-18 17:42:04,780 - ubuntuone.SyncDaemon - WARNING - Files synchronization is disabled.
2011-04-18 17:42:05,629 - ubuntuone.SyncDaemon - WARNING - Files synchronization is disabled.
2011-04-18 17:42:06,496 - ubuntuone.SyncDaemon - WARNING - Files synchronization is disabled.
2011-04-18 17:42:07,359 - ubuntuone.SyncDaemon - WARNING - Files synchronization is disabled.
2011-04-18 17:42:08,359 - ubuntuone.SyncDaemon - WARNING - Files synchronization is disabled.
2011-04-18 17:42:09,184 - ubuntuone.SyncDaemon - WARNING - Files synchronization is disabled.
... and so on.

~/.xsession-errors

** (nautilus:2189): WARNING **: Error calling current_status: Message did not receive a reply (timeo
ut by message bus)

** (nautilus:2189): CRITICAL **: syncdaemon_status_info_get_online: assertion `SYNCDAEMON_IS_STATUS_INFO (sinfo)' failed

** (nautilus:2189): WARNING **: Error calling get_folders: Message did not receive a reply (timeout by message bus)

** (nautilus:2189): WARNING **: Error calling current_status: Message did not receive a reply (timeout by message bus)

and this is repeated lots of times.

Enabling File Sync fixed the problem.

Revision history for this message
Natalia Bidart (nataliabidart) wrote :

Hello,

we're aware of this issue, we're tracking the progress of the fix in bug #759714.

Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.