Disconnected from a network, BadTransition kills SyncDaemon

[Martin Albisetti]

Binary package hint: ubuntuone-client

Apport foo attached.

ProblemType: Bug
.home.beuno..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = True
 connect = 0
 show_applet = 1
 bookmarked = True
Architecture: i386
Date: Fri Nov 13 08:53:05 2009
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic i686

[Nigel Babu (nigelbabu)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

[Rick McBride (rmcbride)]

Another BadTransition issue. Log below.

2009-11-13 07:47:44,354 - ubuntuone.SyncDaemon.State - ERROR - READY_WAITING_WITH_BOTHQ --[SYS_SERVER_RESCAN_DONE]--> ERROR!!!
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/state.py", line 61, in handle_default
    next_state = self.state.next(event)
  File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/states.py", line 100, in next
    % (self.name, event))
BadTransition: State READY_WAITING_WITH_BOTHQ can't handle the SYS_SERVER_RESCAN_DONE event

[Joshua Hoover (joshuahoover)]

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.