Ubuntu
ubuntuone-client package

Ubuntu One crashed on wake up

Bug #474515 reported by Jim Nygård on 2009-11-04

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

This bug affects 3 people

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

Bug Description

Binary package hint: ubuntuone-client

Ubuntu One client crashed when the computer wake up from suspend on UNR 9.10.

ProblemType: Bug
.home.jim..cache.ubuntuone.log.oauth.login.log:
Starter Ubuntu One klient versjon 1.0.2
Starter Ubuntu One klient versjon 1.0.2
Starter Ubuntu One klient versjon 1.0.2
Starter Ubuntu One klient versjon 1.0.2
Starter Ubuntu One klient versjon 1.0.2
.home.jim..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = True
connect = 0
show_applet = 0
bookmarked = True
Architecture: i386
Date: Wed Nov 4 19:02:59 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANGUAGE=nb_NO.UTF-8
LANG=nb_NO.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Tags: ubuntu-unr
Uname: Linux 2.6.31-14-generic i686

Tags:

Revision history for this message

Jim Nygård (jim-nygard) wrote on 2009-11-04:

.home.jim..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (511 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 (15.7 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.