Code review comment for lp:~rodrigo-moya/ubuntuone-client/fix-613219

Unfortunately I need to set Needs Fixing again. Here's what happens now:

Clean reboot, ubuntuone-login enabled in system-wide xdg configuration, pretty much default user setup with 1K files under Ubuntu One.

1. Log in to GDM, get to desktop pretty fast.
2. Start using nautilus to navigate your folders
3. After 30 seconds ubuntuone-login starts ubuntuone-syncdaemon and nautilus freezes until syncdaemon finishes loading and starts d-bus server.

** (nautilus:2098): WARNING **: Error calling current_status: 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.

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

** (nautilus:2098): WARNING **: Could not get syncdaemon's root dir: 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.

** (nautilus:2098): WARNING **: Error calling get_folders: 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.

Looks like ready is called too early, i.e. not when Syncdaemon is launched and has DBus service, but too early when it is launched. Maybe we can emit ready when a) syncdaemon is present on the bus and it emitted some DBus signal?