Ubuntu
ubuntuone-client package

Ubuntu One crashes after disconnect

Bug #510918 reported by Scott Blayney on 2010-01-21

This bug report is a duplicate of: Bug #478653: BadTransition: SYS_OAUTH_ERROR. 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

I had uploaded some files from my Windows PC to my One account. I was trying to have them snyc to my Linux PC, but they weren't showing up. I hit disconnect and then tried to reconnect when it crashed.

ProblemType: Bug
.home.scott..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = False
connect = 0
show_applet = 0
Architecture: i386
Date: Thu Jan 21 17:23:54 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-16.53-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-16-generic i686

Tags:

Revision history for this message

Scott Blayney (scottblayney) wrote on 2010-01-21:

.home.scott..cache.ubuntuone.log.oauth.login.log.txt Edit (1.3 KiB, text/plain; charset="utf-8")
.home.scott..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (591 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 (666 bytes, text/plain; charset="utf-8")

Revision history for this message

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

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 478653, 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.