ubuntuone-login crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-AfHEaCCe6J: Connection refused

[Che Dean]

Binary package hint: ubuntuone-client

I had just logged into Ubuntu 11.04 beta 1 and started to check for updates. Then I got a message from Ubuntu One saying it was downloading my latest files and a few seconds later I got a crash report from Ubuntu One. However even after reporting that it had crashed Ubuntu One kept running and synced my files and continued to run as normal.

1) Ubuntu 11.04

2) 0.9.4-0ubuntu1 (ubuntuone-control-panel-gtk)

3) File Sync as normal

4) I received an error message

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.5.8-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Wed Apr 6 17:50:03 2011
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-login
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-login
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_IE:en
 LANG=en_IE.UTF-8
PythonArgs: ['/usr/lib/ubuntuone-client/ubuntuone-login']
SourcePackage: ubuntuone-client
Title: ubuntuone-login crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-AfHEaCCe6J: Connection refused
UbuntuOneSyncdaemonExceptionsLog:

UpgradeStatus: Upgraded to natty on 2011-03-26 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #711324, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.