Comment 5 for bug 498444

I am making this bug report as a master report for all bugs related with the applet being unable to signal syncdaemon to connect to ubuntuone service. The signal receives dbus timeout if metadata rescan does not happen in a timely fashion.

This bug can be detected via the following line in oauth-login.log on applet startup:
2009-11-19 12:14:20,291:291.863918304 UbuntuOne.Client.Applet DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Useful info from bug #461614 (which original description is related to completely different issue):

Roman Yepishev wrote on 2009-11-13:
The bottom line is that ubuntuone-client-applet calls to syncdaemon do not complete in time under high system load.
In my case gnome starts trackerd applet, Empathy, Tomboy, indicator applets and everything competes for the CPU and disk.

Joshua Hoover wrote on 2009-11-18:
See http://irclogs.ubuntu.com/2009/11/13/%23ubuntuone.html#t17:53 for more info. It sounds like this happens when syncdaemon is working on a lot of metadata. There is supposed to be a bug for optimizing fixing the scanning of metadata but I was unable to find it so I'm leaving this comment on this bug as a reminder. :-)

Roman Yepishev wrote on 2009-12-02:
@Facundo Batista Re: "most probably syncdaemon is not started yet"
Observed on my real (i.e. not vm) PC: gnome-session starts, Empathy, Trackerd are loading and then the hard drive is completely possessed by ubuntuone-syncdaemon, with applet not displaying the Icon (in order to avoid the flickering, as the sources say). Then the applet pops up and says we are disconnected. So syncdaemon is started but not ready to service DBus requests.

P.S. Metadata profiling is discussed in bug #436612