Ubuntu
ubuntuone-client package

UbuntuOne crashed for some reason

Bug #501124 reported by Daniel Hackney on 2009-12-28

This bug report is a duplicate of: Bug #457147: BadTransition: SYS_CONNECTION_MADE - Ubuntu One crashes coming out of sleep/hibernate. Edit Remove

This bug affects 2 people

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

Bug Description

Binary package hint: ubuntuone-client

I wasn't doing anything with UbuntuOne (other than letting it do whatever scheduled backups it does automatically), but after resuming from suspend, Apport told me that UbuntuOne had crashed.

ProblemType: Bug
.home.dhackney..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = True
connect = 0
show_applet = 1
bookmarked = True
Architecture: i386
Date: Mon Dec 28 16:01:11 2009
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-16-generic i686

Tags:

Revision history for this message

Daniel Hackney (haxney) wrote on 2009-12-28:

.home.dhackney..cache.ubuntuone.log.oauth.login.log.txt Edit (491 bytes, text/plain; charset="utf-8")
.home.dhackney..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (511 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (3.8 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (692 bytes, text/plain; charset="utf-8")

Revision history for this message

Dave Walker (dogatemycomputer) wrote on 2010-01-11:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 457147, so it 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. Feel free to continue to report any other bugs you may find.