Ubuntu
ubuntuone-client package

ubuntu one, problem with connecting at boot

Bug #471746 reported by Pedro Sá (Kunst Uber Alles) on 2009-11-02

This bug report is a duplicate of: Bug #498444: Ubuntu One Cloud Icon Always Shows Exclamation Mark After Boot. 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

when the computer boot, the ubunto one client ask for a password and try to connect, after a few seconds, the icon on the tray show that is disconnected. If i select the icon and clic to connect, the client works ok. I try a few times and at boot never connects.

ProblemType: Bug
.home.pedro..cache.ubuntuone.log.syncdaemon.exceptions.log:

.home.pedro..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = True
connect = 0
show_applet = 0
Architecture: amd64
Date: Mon Nov 2 21:33:08 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
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 x86_64

Tags:

Revision history for this message

Pedro Sá (Kunst Uber Alles) (kunst-uber-alles) wrote on 2009-11-02:

.home.pedro..cache.ubuntuone.log.oauth.login.log.txt Edit (2.6 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 (767 bytes, text/plain; charset="utf-8")

Revision history for this message

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

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