ubuntuone-login crashed with DBusException in __new__(): org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-gu5yAJK9NW: Connection refused
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntuone-client (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubuntuone-client
I removed a directory from an Ubuntu One sync directory this afternoon and it doesn't seem to have syncd properly. A few hours after I deleted it, I noticed that my CPU was high and 'top' suggested that the Ubuntu One sync daemon was dying off and respawning itself. I restarted the machine and Ubuntu One crashed on login. I reconnected it and Ubuntu One client suggests "File sync in progress". Checking the website reveals that the directory has gone, i.e. sync is complete, but the client still shows "File sync in progress" and keeps disconnecting whenever I reconnect it.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.5.6-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-6-generic x86_64
Architecture: amd64
Date: Mon Mar 14 17:22:20 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/lib/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
PythonArgs: ['/usr/
SourcePackage: ubuntuone-client
Title: ubuntuone-login crashed with DBusException in __new__(): org.freedesktop
UbuntuOnePrefer
2011-01-09 20:32:07,134 - ubuntuone-
2011-01-09 20:32:19,228 - ubuntuone-
UbuntuOneSyncda
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #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.