Ubuntu
ubuntuone-client package

ubuntu one crashed on wake-up

Bug #546179 reported by Joshua Matthew Gallant on 2010-03-24

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

I woke my computer up after putting it to sleep. Ubuntu One was connected fine at the time.

When I woke my computer from Sleep a couple hours later Ubuntu One displayed a fatal error.

ProblemType: Bug
.home.joshua..config.ubuntuone.syncdaemon.conf:
[bandwidth_throttling]
read_limit = 0
write_limit = 0
on = False
.home.joshua..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = True
connect = 0
show_applet = 1
Architecture: i386
Date: Wed Mar 24 12:56:24 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=en_CA.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-20-generic i686

Tags:

Revision history for this message

Joshua Matthew Gallant (joshua-matthew-gallant) wrote on 2010-03-24:

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

Revision history for this message

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

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.