U1 cannot communicate with dbus

[PrivateUser132781]

After a reboot, u1syncdaemon apparently cannot communicate with dbus:

eduard@maantop:~$ tail -f .cache/ubuntuone/log/oauth-login.log
2009-12-09 02:52:00,000:0.174999237061 UbuntuOne.Client.Applet Starting Ubuntu One client version 1.1
2009-12-09 12:00:54,204:204.952001572 UbuntuOne.Client.Applet DBus Error: Message did not receive a reply (timeout by message bus)
2009-12-09 14:26:06,509:509.160995483 UbuntuOne.Client.Applet Starting Ubuntu One client version 1.1
2009-12-09 14:26:56,985:985.347986221 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.
2009-12-09 14:26:56,986:986.443996429 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.
2009-12-09 14:27:17,573:573.407888412 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.

This also happens when manually requesting status:
eduard@maantop:~$ dbus-send --session --print-reply --dest=com.ubuntuone.SyncDaemon --type=method_call /status com.ubuntuone.SyncDaemon.Status.current_statusError org.freedesktop.DBus.Error.NoReply: 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.

ProblemType: Bug
.home.eduard..cache.ubuntuone.log.syncdaemon.exceptions.log:

.home.eduard..config.ubuntuone.syncdaemon.conf:
 [bandwidth_throttling]
 on = False
 read_limit = 0
 write_limit = 0
.home.eduard..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 show_applet = 0
 connected = True
 connect = 0
 bookmarked = True
Architecture: amd64
CrashDB: ubuntuone
Date: Wed Dec 9 14:32:48 2009
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.1+r283-0ubuntu1~ppa1~karmic
PackageArchitecture: all
ProcEnviron:
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SourcePackage: ubuntuone-client
ThirdParty: True
Uname: Linux 2.6.31-16-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:2282): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2282): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2408): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2391): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

[PrivateUser132781 (privateuser132781-deactivatedaccount)]

I should add that after a while the applet appeared (in the circular arrows mode) but when clicked says "Your files are up to date" (they are not). Response is now as follows:

eduard@maantop:~$ dbus-send --session --print-reply --dest=com.ubuntuone.SyncDaemon --type=method_call /status com.ubuntuone.SyncDaemon.Status.current_statusmethod return sender=:1.70 -> dest=:1.120 reply_serial=2
   array [
      dict entry(
         string "is_error"
         string ""
      )
      dict entry(
         string "is_connected"
         string ""
      )
      dict entry(
         string "name"
         string "READING_WITH_NETWORK_WITH_BOTHQ"
      )
      dict entry(
         string "is_online"
         string ""
      )
      dict entry(
         string "description"
         string "doing local rescan; network is available, BOTHQ waiting"
      )
   ]

[Roman Yepishev (rye)]

I believe this can be marked as a duplicate of bug 498444.
When syncdaemon is loading metadata it might not be able to respond in timely fashion to DBus requests, thus causing the error message mentioned above to appear.