Ubuntu
ubuntuone-client package

fatal error of ubuntu one applet when disconnecting eth0

Bug #479130 reported by mipmap on 2009-11-09

This bug report is a duplicate of: Bug #478653: BadTransition: SYS_OAUTH_ERROR. Edit Remove

This bug affects 2 people

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

Bug Description

Binary package hint: ubuntuone-client

1) Ubuntu 9.10
2) ubuntu-one 1.0.2-0ubuntu2 (client-gnome)
3) Ubuntu One should halt or terminate session gracefully, ideally reconnect when eth0 is online again
4) applet crashed with "fatal error" report

ProblemType: Bug
.home.chris..cache.ubuntuone.log.oauth.login.log:
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
.home.chris..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = False
connect = 0
show_applet = 0
bookmarked = True
Architecture: i386
CheckboxSubmission: 3420194d506af7b5c9b2fa66a576227b
CheckboxSystem: 34179ae9d787c87b2b99043345f17cea
Date: Mon Nov 9 13:36:54 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic i686

Tags:

Revision history for this message

mipmap (mipmap) wrote on 2009-11-09:

.home.chris..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (581 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 (1.8 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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