NIGHTLIES: Setting download limit to a low value like 1 does bad things

Bug #479517 reported by Rick McBride
This bug report is a duplicate of:  Bug #458393: BadTransition: SYS_SERVER_RESCAN_DONE. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu One Client
Confirmed
Undecided
Unassigned

Bug Description

set download limit to 1 K via manual input in the spinner box in the config UI. Clicked "Disconnect" in the applet.

got the following immediately.

2009-11-09 16:01:17,757 - ubuntuone.SyncDaemon.State - ERROR - READY_WITH_NETWORK_WITH_METAQ --[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_WITH_NETWORK_WITH_METAQ can't handle the SYS_SERVER_RESCAN_DONE event

ProblemType: Bug
.home.rmcbride..config.ubuntuone.syncdaemon.conf:
 [bandwidth_throttling]
 read_limit = 0
 write_limit = 65536
 on = True
.home.rmcbride..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = False
 connect = 0
 show_applet = 0
 bookmarked = True
Architecture: amd64
CrashDB: ubuntuone
Date: Mon Nov 9 16:02:27 2009
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.1+r276-0ubuntu1~ppa1~karmic
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48+ureadahead2-generic
SourcePackage: ubuntuone-client
ThirdParty: True
Uname: Linux 2.6.31-14-generic x86_64

Revision history for this message
Rick McBride (rmcbride) wrote :
Changed in ubuntuone-client:
status: New → Confirmed
tags: added: desktop+
Revision history for this message
Joshua Hoover (joshuahoover) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.