ubuntuone-launch crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntuone-client (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubuntuone-client
I had just rebooted and didn't touch Ubuntu One. Before the reboot the computer was running only for a few minutes (then I tried powertop and its suspend non-input USB devices, which killed my mouse movements, so I had to reboot); not sure if that's related.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.6.0-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Tue Apr 12 07:36:48 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110408)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
LANGUAGE=de:en
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: ubuntuone-client
Title: ubuntuone-launch crashed with DBusException in __new__(): org.freedesktop
UbuntuOneSyncda
2011-04-12 07:38:28,345 - twisted - ERROR - Unhandled error in Deferred:
2011-04-12 07:38:28,345 - twisted - ERROR - Unhandled Error
Traceback (most recent call last):
Failure: ubuntuone.
UpgradeStatus: Upgraded to natty on 2011-04-09 (3 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
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.