Ubuntu
ubuntuone-client package

fatal error

Bug #468645 reported by Youssef on 2009-11-01

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

This bug affects 6 people

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

Bug Description

Binary package hint: ubuntuone-client

i was simply starting up my system, when i got "fatal error" and ubuntu-one could not connect

ProblemType: Bug
.home.youssef..config.ubuntuone.syncdaemon.conf:
[bandwidth_throttling]
read_limit = 2097152
write_limit = 2048000
on = True
.home.youssef..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = False
connect = 0
show_applet = 0
bookmarked = True
Architecture: amd64
Date: Sun Nov 1 15:16:27 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic x86_64

Tags:

Revision history for this message

Youssef (that-y-guy) wrote on 2009-11-01:

.home.youssef..cache.ubuntuone.log.oauth.login.log.txt Edit (245 bytes, text/plain; charset="utf-8")
.home.youssef..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 (1.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Joshua Hoover (joshuahoover) wrote on 2009-11-16:

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.