Comment 23 for bug 420705

Revision history for this message
Roman Yepishev (rye) wrote :

Ok, I was able to reproduce this under the following conditions:

1. ubuntuone-syncdaemon had file synchronization disabled.
2. A call was made to Ubuntu One SyncDaemon DBus API that triggered the syncdaemon to be started.
3. libsyncdaemon in nautilus plugin was listening to NameOwnerChange event from DBus
4. syncdaemon starts up, aquires DBus name, finds that file sync is disabled and shuts down
5. nautilus found that syncdaemon is starting and queued some calls to /status
6. SyncDaemon is being restarted
7. I log out from the session, session manager tells me that File Manager (nautilus) is very busy
8. I log in back to the session and /var/crash/_usr_lib_ubuntuone-client_ubuntuone-syncdaemon.1000.crash has appeared with the date/time corresponding to my logout.

Exception:
 DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-NjgqXdjDbh: Connection refused

But this dbus session is not valid:
$ echo $DBUS_SESSION_BUS_ADDRESS
unix:abstract=/tmp/dbus-hNCmBsQZMX,guid=14abeb90782bd46a03e00a4d00000084

Does anybody who experience this issue have File Synchronization disabled?