Ubuntu
ubuntuone-client package

ubuntuone-client signale une erreur

Bug #498430 reported by SC4ideal on 2009-12-19

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

Peut-être lié à des problèmes de connexions au réseau.

Ubuntu - Linux pour les êtres humains !

Vous utilisez actuellement Ubuntu 9.10 - le Koala Karmique sortie en Octobre 2009 et supportée jusqu'en Avril 2011.

https://one.ubuntu.com/files/#path=/My%20Files

ProblemType: Bug
.home.i..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = True
connect = 0
show_applet = 1
Architecture: amd64
Date: Sat Dec 19 07:22:18 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: fglrx
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.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

SC4ideal (sc4ideal) wrote on 2009-12-19:

.home.i..cache.ubuntuone.log.oauth.login.log.txt Edit (2.1 KiB, text/plain; charset="utf-8")
.home.i..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (511 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 (3.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Joshua Hoover (joshuahoover) wrote on 2009-12-21:

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.