UbuntuOne applet crashes after clicking connect, disconnect, then again connect

Bug #507580 reported by freddy3on
This bug report is a duplicate of:  Bug #420354: BadTransition in ubuntuone-syncdaemon. Edit Remove
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu One Client
New
Undecided
Ubuntu One Client Engineering team
ubuntuone-client (Ubuntu)
New
Low
Ubuntu One Client Engineering team

Bug Description

After booting I clicked on UbuntuOne applet - connect, then disconnect, then connect within a few seconds (don't ask why). The applet crashed. It's reproducible. I can't start UbuntuOne unless reboot the system. Edit: I can quit it and then restart UbuntuOne.

2010-04-21 18:51:25,234 - ubuntuone.SyncDaemon.State - ERROR - READY_WITH_NETWORK_WITH_METAQ --[SYS_SET_CAPABILITIES_ERROR]--> 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_SET_CAPABILITIES_ERROR event

freddy3on (selokigro)
description: updated
Revision history for this message
Vincenzo Di Somma (vds) wrote :

Hi, thanks for filing the bug, do you still have this problem after the last update? Do you mind to add the logs of Ubuntu One to the bug?

Changed in ubuntuone-client:
status: New → Incomplete
Revision history for this message
Duane Hinnen (duanedesign) wrote :

We haven't heard back from you in a while so we are closing this bug. If this is still an issue for you could you test the current Ubuntu development version, this would help us a lot. There have been many changes in Ubuntu One since the time you reported the bug and your problem may have been fixed with some of the updates. We would appreciate if you could upload updated information by running: apport-collect -p ubuntuone-client bug # , and attach the logs to this report. Just zip your $HOME/.cache/ubuntuone/log/ folder and attach the zip here. You can make an archive of the $HOME/.cache/ubuntuone/log/ folder by right-clicking on it and selecting 'Compress'. You might need to do Ctrl + H (view hidden files) in you Home directory to see the .cache folder. You can attach the logs to this report using the 'Add Attachment or Patch' button at the bottom of the page. After you attach the logs you can change the 'Status' of your bug back to 'New'. The status of a bug report can be modified by clicking on the current status in the yellow line, which will reveal a sub menu. You can then set a new status in the drop down box.

thank you,
duanedesign

Changed in ubuntuone-client:
status: Incomplete → Invalid
Revision history for this message
freddy3on (selokigro) wrote :

I tried ist again now after not using ubuntuone for a while. It seems that the bug is still there, even if I had to try more often to reproduce it. So there's no problem during using it the normal way. Only by clicking "connect" and "disconnect" a few times, it crashes. Then a bug-report window appears. I can close it and then restart ubuntuone without a problem. So the problem only appears during "wrong use".

I try to attach the right file.

kind regards

Changed in ubuntuone-client:
status: Invalid → New
description: updated
Changed in ubuntuone-client (Ubuntu):
assignee: nobody → Ubuntu One Desktop+ team (ubuntuone-desktop+)
Changed in ubuntuone-client:
assignee: nobody → Ubuntu One Desktop+ team (ubuntuone-desktop+)
Changed in ubuntuone-client (Ubuntu):
importance: Undecided → Low
tags: added: desktop+
tags: added: bad-transition
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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