ubuntuone-login crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-Gqs9tuJpSr: Kapcsolat elutasítva

[Zsolt Tarsoly]

Binary package hint: ubuntuone-client

Crash after boot.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.5.8-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Sun Apr 3 18:21:20 2011
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-login
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-login
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=hu_HU:en
 LANG=hu_HU.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-Gqs9tuJpSr: Kapcsolat elutasítva
UbuntuOnePreferencesLog:
 2011-03-13 18:44:28,958 - ubuntuone-preferences - INFO - Starting Ubuntu One Preferences
 2011-03-13 18:44:30,444 - ubuntuone-preferences - INFO - Got credentials for Ubuntu One
 2011-04-02 15:23:10,615 - ubuntuone-preferences - INFO - Starting Ubuntu One Preferences
 2011-04-02 15:23:12,481 - ubuntuone-preferences - INFO - Got credentials for Ubuntu One
UbuntuOneSyncdaemonExceptionsLog:

UbuntuOneUserSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 2097152
 on = False
UpgradeStatus: Upgraded to natty on 2011-04-03 (0 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.