Ubuntu
ubuntuone-client package

Disconnect caused crash

Bug #494871 reported by Scott S. McCoy on 2009-12-10

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

Down-stream synchronization was not occurring (or there were no notices). Attempted to disconnect and reconnect to induce synchronization, but disconnect caused crash.

ProblemType: Bug
.home.scott..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = False
connect = 0
show_applet = 0
Architecture: amd64
CheckboxSubmission: 26f350e25a617be02e0826a6f15e2324
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Wed Dec 9 21:59:03 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: fglrx
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-16-generic x86_64

Tags:

Revision history for this message

Scott S. McCoy (tag) wrote on 2009-12-10:

.home.scott..cache.ubuntuone.log.oauth.login.log.txt Edit (25.0 KiB, text/plain; charset="utf-8")
.home.scott..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (521 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (3.9 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Joshua Hoover (joshuahoover) wrote on 2009-12-10:

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.