Ubuntu
ubuntuone-client package

ubuntu one gave critical error

Bug #515055 reported by Geoff Hunt on 2010-01-31

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)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: ubuntuone-client

Was trying to connect, then gave critical error, and closed.

ProblemType: Bug
.home.geoff..config.ubuntuone.syncdaemon.conf:
[bandwidth_throttling]
read_limit = 262144
write_limit = 262144
on = True
.home.geoff..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = False
connect = 0
show_applet = 1
Architecture: i386
Date: Sun Jan 31 11:51:22 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: wl
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=en_ZA.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-17-generic i686

Tags:

Revision history for this message

Geoff Hunt (grhunt) wrote on 2010-01-31:

.home.geoff..cache.ubuntuone.log.oauth.login.log.txt Edit (1.0 KiB, text/plain; charset="utf-8")
.home.geoff..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (2.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.9 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (718 bytes, text/plain; charset="utf-8")

Revision history for this message

Mitch Towner (kermiac) wrote on 2010-01-31:

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. Please continue to report any other bugs you may find.