Ubuntu One Client

problem logging on to Ubuntu One

Bug #526119 reported by cyberb764 on 2010-02-22

This bug report is a duplicate of: Bug #479271: BadTransition: SYS_SET_CAPABILITIES_ERROR. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu One Client	Confirmed	Undecided	Unassigned

Bug Description

not sure, when rebooting this error message about Ubuntu One popped up, but now it seems to have no problem

ProblemType: Bug
.home.cyberb764..config.ubuntuone.syncdaemon.conf:
[bandwidth_throttling]
read_limit = 0
write_limit = 0
on = False
.home.cyberb764..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = False
connect = 0
show_applet = 1
bookmarked = True
Architecture: i386
CrashDB: ubuntuone
Date: Mon Feb 22 15:33:39 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: ubuntuone-client 1.1.1+r321-0ubuntu1~ppa1~jaunty
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic-pae
SourcePackage: ubuntuone-client
ThirdParty: True
Uname: Linux 2.6.31-20-generic-pae i686
XsessionErrors:
(polkit-gnome-authentication-agent-1:2535): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(<unknown>:2558): GLib-WARNING **: g_set_prgname() called multiple times

Tags:

Revision history for this message

cyberb764 (rmills764) wrote on 2010-02-22:

.home.cyberb764..cache.ubuntuone.log.oauth.login.log.txt Edit (5.1 KiB, text/plain; charset="utf-8")
.home.cyberb764..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (654 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (3.9 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (290 bytes, text/plain; charset="utf-8")

Revision history for this message

Duane Hinnen (duanedesign) wrote on 2010-02-23:

cyberb764,
Thank you for taking the time to report this bug and helping to make Ubuntu One better. This particular bug has already been reported and is a duplicate of bug 479271, 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.

thank you,
duanedesign