Ubuntu
ubuntuone-client package

ubuntu one client crashes without apparent reason

Bug #548411 reported by jofarmer on 2010-03-25

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

This bug affects 2 people

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

Bug Description

Binary package hint: ubuntuone-client

Just out of nowhere ubuntu-one client crashed and I was asked to report this as a bug. Unfortunately I cannot provide any more usefule info...

ProblemType: Bug
.home.klaus..config.ubuntuone.syncdaemon.conf:
[bandwidth_throttling]
read_limit = 0
write_limit = 0
on = False
.home.klaus..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = False
connect = 0
show_applet = 1
Architecture: i386
Date: Thu Mar 25 23:47:29 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: ubuntuone-client 1.0.3-0ubuntu1
PackageArchitecture: all
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58~phc0-generic-phc
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-20-generic-phc i686

Tags:

Revision history for this message

jofarmer (m-launchpad-kwf-otherinbox-com) wrote on 2010-03-25:

.home.klaus..cache.ubuntuone.log.oauth.login.log.txt Edit (20.8 KiB, text/plain; charset="utf-8")
.home.klaus..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (511 bytes, 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 (1.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Mitch Towner (kermiac) wrote on 2010-03-26:

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.