Comment 2 for bug 904071

I would love to be able to see what is in queue, but unfortunately, this happens:

bladernr@GarbageScow:~$ u1sdtool --waiting

Oops, an error ocurred:
Traceback (most recent call last):
Failure: dbus.exceptions.DBusException: 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.

So maybe I'll at least look and see what folders U1 is scanning:

bladernr@GarbageScow:~$ u1sdtool --list-folders

Oops, an error ocurred:
Traceback (most recent call last):
Failure: dbus.exceptions.DBusException: 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.

I may as well just shut it down now so I can actually get some work done:

bladernr@GarbageScow:~$ u1sdtool -q
ubuntuone-syncdaemon stopped.

Surprisingly, this actually worked this time. about 50% of the time, syncdaemon is consuming so much resources that the quit command actually fails. Instead of the above message, I get a message like this:

ubuntuone-syncdaemon still running.

Look, I'm still, after 2 years, willing to help make this work, and I'm even willing to conceded that I could possibly be part of the cause (pebkac) however, I find it hard to believe that I am the direct cause of exactly the same symptoms on 3 different machines.