Ubuntu
ubuntuone-client package

ubuntu one client crashes after a restart due to power loss

Bug #512330 reported by oican on 2010-01-25

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)	New	Undecided	Unassigned

Bug Description

Binary package hint: ubuntuone-client

After a power loss system rebooted and Ubuntu One raised this error.

ProblemType: Bug
.home.thorin..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = True
connect = 0
show_applet = 0
Architecture: i386
Date: Mon Jan 25 16:02:13 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-17-generic i686
XsessionErrors:
(polkit-gnome-authentication-agent-1:2023): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(firefox:2256): GLib-WARNING **: g_set_prgname() called multiple times

Tags:

Revision history for this message

oican (ozgurican) wrote on 2010-01-25:

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

Revision history for this message

Victor Vargas (kamus) wrote on 2010-01-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. Feel free to continue to report any other bugs you may find.