ubuntuone-login crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-jx4jJJZBQe: В соединении отказано

[Pavel-II]

Binary package hint: ubuntuone-client

ubuntuone-login crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-jx4jJJZBQe: В соединении отказано

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: Sun Apr 10 00:08:54 2011
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-login
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-login
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=ru_RU:ru:en_GB:en
 LANG=ru_RU.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-jx4jJJZBQe: В соединении отказано
UbuntuOneClientConfig:
 [ubuntuone]
 show_applet = 1
 connected = False
 connect = 0
 bookmarked = True
UbuntuOneSyncdaemonExceptionsLog:

UbuntuOneUserSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 2097152
 on = False
UpgradeStatus: Upgraded to natty on 2011-03-25 (16 days ago)
UserGroups: adm admin audio cdrom dialout dip disk fax lpadmin netdev plugdev root sambashare src ssh sudo tape video

[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.