Ubuntu
ubuntuone-client package

Bug occured during UbuntuOne connexion

Bug #465296 reported by luismi123 on 2009-10-30

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

When I start Ubuntu One there is a message telling me:
There is a fatal error in Ubuntu One. Click on the icone to send the error report

And I'm then unable to use Ubuntu One as everytime I clicl on the icone I trigger the send error report action

Regards

Luis

ProblemType: Bug
.home.luis..cache.ubuntuone.log.oauth.login.log: Démarrage du client Ubuntu One version 1.0.2
.home.luis..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
show_applet = 1
connected = False
connect = 0
bookmarked = True
Architecture: amd64
Date: Fri Oct 30 19:28:23 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.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

luismi123 (luismi123) wrote on 2009-10-30:

.home.luis..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (7.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.9 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (3.0 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 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.