Ubuntu
ubuntuone-client package

unable to reconnect to UbuntuOne after manual deconnection

Bug #497730 reported by Jean Rebillat on 2009-12-17

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

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ubuntuone-client (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: ubuntuone-client

Ununtu 9.10
package ubuntuone-client 1.0.2-ubuntu2
Once connected in ubuntuone with local folder open, I selected "disconnect" in applet, then try to select "connect". Then the applet said there was a fatal error - may be a bug.
I was then unable to reconnect.

ProblemType: Bug
.home.jean..cache.ubuntuone.log.oauth.login.log: Démarrage du client Ubuntu One version 1.0.2
.home.jean..config.ubuntuone.syncdaemon.conf:
[bandwidth_throttling]
on = True
read_limit = -1
write_limit = -1
.home.jean..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
show_applet = 0
connected = False
connect = 0
bookmarked = True
Architecture: amd64
Date: Thu Dec 17 12:54:24 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=fr_FR.UTF-8
SHELL=/usr/bin/tcsh
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-16-generic x86_64

Tags:

Revision history for this message

Jean Rebillat (jean-rebillat) wrote on 2009-12-17:

.home.jean..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (521 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (3.8 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (11.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Joshua Hoover (joshuahoover) wrote on 2009-12-17:

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.