Ubuntu
ubuntuone-client package

ubuntu one crashed on login with network problems

Bug #479712 reported by Philipe Farias on 2009-11-10

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

Logged in with problems in my network (internet problem) and while changing the settings on the network-manager the ubuntu-one client suddenly crashed.

ProblemType: Bug
.home.nativo..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = True
connect = 0
show_applet = 1
bookmarked = True
Architecture: amd64
Date: Mon Nov 9 22:49:17 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANGUAGE=pt_BR.UTF-8
LANG=pt_BR.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic x86_64

Tags:

Revision history for this message

Philipe Farias (philipefarias) wrote on 2009-11-10:

.home.nativo..cache.ubuntuone.log.oauth.login.log.txt Edit (319 bytes, text/plain; charset="utf-8")
.home.nativo..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (497 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 (871 bytes, 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 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.