Ubuntu
ubuntuone-client package

startup after suspend, auto popup of bug reporter

Bug #543296 reported by Ken Wagner on 2010-03-21

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

Ubuntu crashed after suspend followed by awakening.

ProblemType: Bug
.home.beaucoder..config.ubuntuone.syncdaemon.conf:
[bandwidth_throttling]
read_limit = 0
write_limit = 0
on = False
.home.beaucoder..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = True
connect = 0
show_applet = 0
bookmarked = True
Architecture: amd64
Date: Sun Mar 21 05:10:34 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: ubuntuone-client 1.0.3-0ubuntu1
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-20-generic x86_64

Tags:

Revision history for this message

Ken Wagner (kenneth-wagner) wrote on 2010-03-21:

.home.beaucoder..cache.ubuntuone.log.oauth.login.log.txt Edit (3.8 KiB, text/plain; charset="utf-8")
.home.beaucoder..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (511 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.0 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (2.7 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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.