Ubuntu
ubuntuone-client package

crashes updates conflict files

Bug #491564 reported by Manuel E on 2009-12-02

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

no update files and info conflict files no rewriting same files

ProblemType: Bug
.home.manuel..config.ubuntuone.syncdaemon.conf:
[bandwidth_throttling]
read_limit = 2097152
write_limit = 4194304
on = True
.home.manuel..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = False
connect = 0
show_applet = 0
Architecture: i386
CheckboxSubmission: 9407ea279a21de3497fc24c1738a1f2b
CheckboxSystem: ee0ba8cd0157c52da73452acf78b7b2a
Date: Wed Dec 2 15:38:50 2009
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=es_VE.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-15-generic i686

Tags:

Revision history for this message

Manuel E (cotoprixve) wrote on 2009-12-02:

.home.manuel..cache.ubuntuone.log.oauth.login.log.txt Edit (7.4 KiB, text/plain; charset="utf-8")
.home.manuel..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (5.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.8 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (5.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Joshua Hoover (joshuahoover) wrote on 2009-12-02:

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