ubuntuone-syncdaemon crashed with DBusException in call_blocking()

Bug #683234 reported by Sense Egbert Hofstede
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ubuntuone-client

This crash message was shown by Apport after PolicyKit crashed (bug #683233), which in its turn had crashed after Update Manager had crashed after finishing installing updates.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.5.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-7.18-generic 2.6.37-rc3
Uname: Linux 2.6.37-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Nov 30 17:41:12 2010
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=nl_NL:nl:en_GB:en
 LANG=nl_NL.utf8
PythonArgs: ['/usr/lib/ubuntuone-client/ubuntuone-syncdaemon']
SourcePackage: ubuntuone-client
Title: ubuntuone-syncdaemon crashed with DBusException in call_blocking()
UbuntuOneUserSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 2097152
 on = False
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev postgres pulse-access sambashare src staff users video www-data

Revision history for this message
Sense Egbert Hofstede (sense) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #404541. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: removed: need-duplicate-check
tags: added: regression-retracer
Changed in ubuntuone-client (Ubuntu):
status: New → Confirmed
Revision history for this message
Sense Egbert Hofstede (sense) wrote :

Closing my bug as Invalid, because I can no longer reproduce it. it is quite old already and considering the massive work that has gone into Ubuntu One since then, not relevant anymore.

visibility: private → public
Changed in ubuntuone-client (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.