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

Bug #745262 reported by Mauricio Pretto
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubuntuone-client

after login

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 x86_64
Architecture: amd64
Date: Tue Mar 29 16:59:45 2011
ExecutablePath: /usr/bin/ubuntuone-launch
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110202)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/ubuntuone-launch
ProcEnviron:
 LANGUAGE=en
 LANG=pt_BR.UTF-8
 LC_MESSAGES=en_GB.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-ziMuu2jxy6: Connection refused
UbuntuOneSyncdaemonExceptionsLog:

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

Revision history for this message
Mauricio Pretto (pretto) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.