Ubuntu
ubuntuone-client package

ubuntuone-syncdaemon crashed with OSError in main()

Bug #442238 reported by Matt Wheeler on 2009-10-04

This bug report is a duplicate of: Bug #437471: Ubuntu one client crashed. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ubuntuone-client (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: ubuntuone-client

the daemon does not appear to start up at all.

ProblemType: Crash
Architecture: i386
Date: Sun Oct 4 14:34:51 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
InterpreterPath: /usr/bin/python2.6
Package: ubuntuone-client 0.96.0-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
ProcEnviron:
SHELL=/usr/bin/zsh
LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
PythonArgs: ['/usr/lib/ubuntuone-client/ubuntuone-syncdaemon']
SourcePackage: ubuntuone-client
Title: ubuntuone-syncdaemon crashed with OSError in main()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev pulse-access scanner vboxusers video

Tags:

Revision history for this message

Matt Wheeler (funkyhat) wrote on 2009-10-04:

.home.matt..cache.ubuntuone.log.oauth.login.log.txt Edit (24.6 KiB, text/plain; charset="utf-8")
.home.matt..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (320 bytes, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (227 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (641 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-10-04: This bug is a duplicate

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 #441482, 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.