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

[frizzle21]

Binary package hint: ubuntuone-client

whenever i log into my desktop session, i get a bunch of little modal windows telling me some system app crashed... but not which one. This crash/bug report was generated automatically, so i wouldn't know what else to fill in here..

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.5.5-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic-pae 2.6.38-rc2
Uname: Linux 2.6.38-1-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sat Mar 5 18:36:29 2011
ExecutablePath: /usr/bin/ubuntuone-launch
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/ubuntuone-launch
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/ubuntuone-launch']
SourcePackage: ubuntuone-client
Title: ubuntuone-launch crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-7nGXmzGmDg: Connection refused
UbuntuOnePreferencesLog:
 2010-12-25 17:05:11,597 - ubuntuone-preferences - INFO - Starting Ubuntu One Preferences
 2010-12-25 17:05:35,244 - ubuntuone-preferences - ERROR - Database enablement is unavailable.
UbuntuOneSyncdaemonExceptionsLog:

UbuntuOneUserSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 2097152
 on = False
UpgradeStatus: Upgraded to natty on 2011-02-17 (16 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 #618189, 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.