ubuntuone-syncdaemon crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntuone-client (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubuntuone-client
I don't know what happen - report was automatically generated. Maybe may integrated graphic card i865, witch don't work properly with new natty ubuntu. Now I plug in second card Nvidia MX4, but I started Ubuntu with i865. Everyday problem, crashes and corrupted windows and another graphics elements.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.5.8-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Thu Apr 7 22:40:34 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=pl_PL:en
LANG=pl_PL.UTF-8
PythonArgs: ['/usr/
SourcePackage: ubuntuone-client
Title: ubuntuone-
UbuntuOnePrefer
2010-12-02 20:14:10,772 - ubuntuone-
2010-12-02 20:14:14,907 - ubuntuone-
UbuntuOneSyncda
2011-04-07 22:45:50,337 - twisted - ERROR - Unhandled error in Deferred:
2011-04-07 22:45:50,354 - twisted - ERROR - Unhandled Error
Traceback (most recent call last):
Failure: ubuntuone.
UbuntuOneUserSy
[bandwidth_
read_limit = 2097152
write_limit = 2097152
on = False
UpgradeStatus: Upgraded to natty on 2011-03-06 (32 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv 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 #711221, 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.