Ubuntu
ubuntuone-client package

ubuntuone client reported a bug after copying a folder into 'Ubuntu One' and deleting it shortly after the transfer started

Bug #484402 reported by sierdzio on 2009-11-17

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

I've copied a folder into 'Ubuntu One', it instantly added '.u1conflict' to the name, like it has done many times before. I deleted the folder shortly afterwards (transfer surely hasn't been completed), and the client reported an error.

ProblemType: Bug
.home.sierdzio..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = False
connect = 0
show_applet = 0
Architecture: amd64
Date: Tue Nov 17 20:20:25 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
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

sierdzio (sierdzio) wrote on 2009-11-17:

.home.sierdzio..cache.ubuntuone.log.oauth.login.log.txt Edit (161.6 KiB, text/plain; charset="utf-8")
.home.sierdzio..cache.ubuntuone.log.syncdaemon.exceptions.log.gz Edit (4.0 KiB, application/x-gzip)
Dependencies.txt Edit (3.8 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (13.7 KiB, text/plain; charset="utf-8")

Revision history for this message

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

hank 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.