Ubuntu
ubuntuone-client package

UbuntuOne crash

Bug #507213 reported by Jeremy Yoder on 2010-01-13

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 1 person

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

Bug Description

Binary package hint: ubuntuone-client

Sorry, I don't actually know what happened. I didn't witness the crash, it was caught for me. I'm hoping the attached files will have enough info to be useful.

ProblemType: Bug
.home.jyoder..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = True
connect = 0
show_applet = 1
Architecture: i386
Date: Wed Jan 13 16:24:47 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-17-generic i686

Tags:

Revision history for this message

Jeremy Yoder (jyoder) wrote on 2010-01-13:

.home.jyoder..cache.ubuntuone.log.oauth.login.log.txt Edit (573 bytes, text/plain; charset="utf-8")
.home.jyoder..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (497 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 (806 bytes, text/plain; charset="utf-8")

Revision history for this message

Joshua Hoover (joshuahoover) wrote on 2010-01-15:

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.