Ubuntu One applet switches Idle/Working continually
Bug #379449 reported by
Mart van Ineveld
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu One Client |
Fix Released
|
Medium
|
Natalia Bidart |
Bug Description
The applet icon in the panel is continually switching between the states Idle and Working. The effect is that the other icons shift left- and rightwards in the same panel.
Maybe the following has to do something with this strange behaviour: there are several (big) files in my Ubuntu One folder that are not yet synchronised. After logging on to my workstation Ubuntu One does not connect to the server. I have to connect manually, and then the described behaviour is shown. As far as I can see no network traffic is taking place.
Related branches
lp:~facundo/ubuntuone-client/states-refactor
- Natalia Bidart (community): Approve
- Eric Casteleijn (community): Approve
- Rick McBride (community): Approve
-
Diff: 16453 lines (+11590/-2428)19 files modifiedbin/ubuntuone-syncdaemon (+0/-1)
contrib/testing/testcase.py (+15/-13)
data/syncdaemon.conf (+0/-5)
docs/states_connection.svg (+1884/-0)
docs/states_manager.svg (+7360/-622)
docs/states_queues.svg (+2064/-0)
tests/syncdaemon/test_action_queue.py (+108/-14)
tests/syncdaemon/test_dbus.py (+28/-37)
tests/syncdaemon/test_main.py (+33/-81)
tests/syncdaemon/test_states.py (+0/-571)
tests/syncdaemon/test_tools.py (+18/-12)
tests/syncdaemon/test_u1sdtool.py (+11/-4)
ubuntuone/syncdaemon/action_queue.py (+29/-37)
ubuntuone/syncdaemon/dbus_interface.py (+21/-15)
ubuntuone/syncdaemon/event_queue.py (+6/-8)
ubuntuone/syncdaemon/main.py (+12/-14)
ubuntuone/syncdaemon/state.py (+0/-117)
ubuntuone/syncdaemon/states.py (+0/-876)
ubuntuone/syncdaemon/tools.py (+1/-1)
Changed in ubuntuone-client: | |
assignee: | John Lenton (chipaca) → Naty Bidart (nataliabidart) |
To post a comment you must log in.
It seems that there's some failure in the upload, so it keeps trying, and trying, and trying...
We will work on this bug, at least to log better which the failure is.
Thanks for the report!