Ubuntu One Client

ubuntu one crashed on disconnect

Bug #440009 reported by marios on 2009-10-01

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

This bug affects 8 people

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu One Client	Confirmed	Medium	Lucio Torre

Bug Description

it happened a lot of times in the past while my router restarts or when I get disconnected from the Internet!!

ProblemType: Bug
Architecture: amd64
CrashDB: ubuntuone
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: ubuntuone-client 0.96.0+r225-0ubuntu1~ppa1~jaunty
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntuone-client
ThirdParty: True
Uname: Linux 2.6.28-15-generic x86_64
UnreportableReason: This is not a genuine Ubuntu package

Tags:

Revision history for this message

marios (marioszou) wrote on 2009-10-01:

.home.msrowley..cache.ubuntuone.log.oauth.login.log.txt Edit (98.0 KiB, text/plain; charset="utf-8")
.home.msrowley..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (510 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (3.8 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (294 bytes, text/plain; charset="utf-8")

Revision history for this message

Facundo Batista (facundo) wrote on 2009-10-02:

BadTransition: State READY_WAITING_WITH_METAQ can't handle the SYS_SERVER_RESCAN_DONE event

Changed in ubuntuone-client:
assignee:	nobody → Lucio Torre (lucio.torre)
status:	New → Triaged
tags:	added: foundations+

Nicola Larosa (teknico) on 2010-01-12

Changed in ubuntuone-client:
importance:	Undecided → Medium

Revision history for this message

Roman Yepishev (rye) wrote on 2010-04-01:

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. Please continue to report any other bugs you may find.