Ubuntu
ubuntuone-client package

Ubuntu One Crashes openning

Bug #494821 reported by Felipe Cortes on 2009-12-10

This bug report is a duplicate of: Bug #478653: BadTransition: SYS_OAUTH_ERROR. 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

No Information

ProblemType: Bug
.home.felipec..cache.ubuntuone.log.oauth.login.log:
Iniciando el cliente de Ubuntu One versión 1.0.2
Iniciando el cliente de Ubuntu One versión 1.0.2
Iniciando el cliente de Ubuntu One versión 1.0.2
Iniciando el cliente de Ubuntu One versión 1.0.2
Iniciando el cliente de Ubuntu One versión 1.0.2
.home.felipec..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = True
connect = 0
show_applet = 0
bookmarked = True
Architecture: amd64
Date: Wed Dec 9 20:47:28 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=es_CO.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-16-generic x86_64

Tags:

Revision history for this message

Felipe Cortes (hfrincon2006) wrote on 2009-12-10:

.home.felipec..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (559 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 (665 bytes, text/plain; charset="utf-8")

Kees Cook (kees) on 2009-12-15

security vulnerability:	yes → no
visibility:	private → public
tags:	added: karmic

Revision history for this message

Joshua Hoover (joshuahoover) wrote on 2009-12-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 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.