ubuntuone-syncdaemon crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-C2bvrVydO0: Connection refused
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntuone-client (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: ubuntuone-client
Natty crashes are pretty common, usually on signing in.
Applets (like show desktop) crash, or things like this. I'm not too sure, frankly, what causes it. The laptop is pretty much a clean new natty install, and this sort of thing happens on a clean boot, with or without a network connection.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.5.8-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Wed Mar 30 14:00:57 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
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-
UbuntuOneSyncda
2011-03-30 14:01:38,870 - twisted - ERROR - Unhandled error in Deferred:
2011-03-30 14:01:38,870 - twisted - ERROR - Unhandled Error
Traceback (most recent call last):
Failure: ubuntuone.
UpgradeStatus: Upgraded to natty on 2011-03-24 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Derek (bugs-m8y) 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.