Ubuntu
ubuntuone-client package

Crash on "disconnect"

Bug #472769 reported by Iain Lane on 2009-11-03

This bug report is a duplicate of: Bug #458393: BadTransition: SYS_SERVER_RESCAN_DONE. Edit Remove

This bug affects 2 people

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

Bug Description

Binary package hint: ubuntuone-client

My U1 hasn't been syncing. I clicked "disconnect" to try and toggle the connection status to see if that would fix it. The client crashed and asked me to send this report.

ProblemType: Bug
.home.laney..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = False
connect = 0
show_applet = 0
Architecture: i386
Date: Tue Nov 3 14:39:08 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
NonfreeKernelModules: nvidia wl
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/usr/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic i686

Tags:

Revision history for this message

Iain Lane (laney) wrote on 2009-11-03:

.home.laney..cache.ubuntuone.log.oauth.login.log.txt Edit (2.9 KiB, text/plain; charset="utf-8")
.home.laney..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (521 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 (2.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Joshua Hoover (joshuahoover) wrote on 2009-11-16:

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