Ubuntu
ubuntuone-client package

ubuntuone-client reports fatal error resuming from sleep.

Bug #484927 reported by sterios prosiniklis on 2009-11-18

This bug report is a duplicate of: Bug #457147: BadTransition: SYS_CONNECTION_MADE - Ubuntu One crashes coming out of sleep/hibernate. Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: ubuntuone-client

Application reports fatal error resuming from sleep.

ProblemType: Bug
.home.sterios..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = True
connect = 2
show_applet = 0
bookmarked = True
Architecture: amd64
CheckboxSubmission: fb090458126de898a5b62e20bdc25bf3
CheckboxSystem: f134069bba098730d27f59b402920826
Date: Wed Nov 18 19:49:51 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=el_GR.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-15-generic x86_64

Tags:

Revision history for this message

sterios prosiniklis (steriosprosiniklis) wrote on 2009-11-18:

.home.sterios..cache.ubuntuone.log.oauth.login.log.txt Edit (26.7 KiB, text/plain; charset="utf-8")
.home.sterios..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (497 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.2 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (234 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.6 KiB, text/plain; charset="utf-8")

summary:

- Problem appeared while resuming from sleep
+ ubuntuone-client reports fatal error resuming from sleep.

Revision history for this message

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

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 457147, 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.