Ubuntu
ubuntuone-client package

Ubuntu-One does not work, non simular possibilities

Bug #465248 reported by Erwin Teunissen on 2009-10-30

This bug report is a duplicate of: Bug #462828: Files are marked for deletion on server when syncdaemon is killed during sync: Capabilities mismatch is displayed for outdated clients.. 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

File sharing does not start due to non simular possibilities.

ProblemType: Bug
.home.erwin..cache.ubuntuone.log.oauth.login.log:
Ubuntu One client versie 1.0.2 starten
Ubuntu One client versie 1.0.2 starten
Ubuntu One client versie 1.0.2 starten
.home.erwin..cache.ubuntuone.log.syncdaemon.exceptions.log: 2009-10-30 17:51:50,278 - ubuntuone.SyncDaemon.ActionQueue - ERROR - Capabilities query failed: The server doesn't have the requested capabilities
.home.erwin..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = True
connect = 0
show_applet = 1
Architecture: i386
Date: Fri Oct 30 18:51:05 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: ubuntuone-client 1.0.2-0ubuntu1
PackageArchitecture: all
ProcEnviron:
LANG=nl_NL.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic i686

Tags:

Revision history for this message

Erwin Teunissen (erwin-teunissen) wrote on 2009-10-30:

Dependencies.txt Edit (3.8 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (2.7 MiB, text/plain; charset="utf-8")

Revision history for this message

ooze (zoe-gauthier) wrote on 2009-10-30:

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