Ubuntu
ubuntuone-client package

No visible error for me as a user

Bug #542463 reported by Peter on 2010-03-20

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
	ubuntuone-client (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: ubuntuone-client

N/A

ProblemType: Bug
.home.peter..config.ubuntuone.syncdaemon.conf:
[bandwidth_throttling]
read_limit = 0
write_limit = 0
on = False
.home.peter..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = True
connect = 0
show_applet = 1
bookmarked = True
Architecture: i386
CheckboxSubmission: 4a9b0eb3f653cbc103397f8a76054817
CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
Date: Sat Mar 20 08:12:33 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: ubuntuone-client 1.0.3-0ubuntu1
PackageArchitecture: all
ProcEnviron:
LANG=nl_NL.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-20-generic i686

Tags:

Revision history for this message

Peter (peter-van-es) wrote on 2010-03-20:

.home.peter..cache.ubuntuone.log.oauth.login.log.txt Edit (10.0 KiB, text/plain; charset="utf-8")
.home.peter..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (646 bytes, 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 (658 bytes, text/plain; charset="utf-8")

Revision history for this message

Mitch Towner (kermiac) wrote on 2010-03-20:

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 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. Please continue to report any other bugs you may find.