ubuntuone-syncdaemon 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
!
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.6.1-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sat Apr 23 22:36:54 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/lib/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANGUAGE=en_US:en
LANG=en_US.UTF-8
PythonArgs: ['/usr/
SourcePackage: ubuntuone-client
Title: ubuntuone-
UbuntuOnePrefer
2011-04-14 23:20:05,427 - ubuntuone-
2011-04-14 23:20:05,666 - ubuntuone-
UbuntuOneSyncda
2011-04-24 00:00:51,139 - twisted - ERROR - Unhandled error in Deferred:
2011-04-24 00:00:51,140 - twisted - ERROR - Unhandled Error
Traceback (most recent call last):
Failure: ubuntuone.
UbuntuOneUserSy
[bandwidth_
on = False
read_limit = 2097152
write_limit = 2097152
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout games lpadmin plugdev sambashare
| Michael Evdokimov (michael-evdokimov) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| visibility: | private → public |
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 #420705, 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.