Ubuntu
ubuntuone-client package

Ubuntu One Crashes On File Upload Attempt

Bug #513386 reported by Sam Williams on 2010-01-27

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'm running with a fully up to date system of Ubuntu 9.10 as of January 27th. Running version: 1.0.2-0ubuntu2 of ubuntuone-client. The client doesn't die on all uploads, but it does seem to get confused as to whether or not it is logged in or not. It would be nice if there was an easy way to restart all the processes involved in this process.

ProblemType: Bug
.home.samiam..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = False
connect = 0
show_applet = 0
bookmarked = True
Architecture: i386
Date: Wed Jan 27 11:58:43 2010
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: ubuntuone-client
Tags: ubuntu-unr
Uname: Linux 2.6.31-17-generic i686

Tags:

Revision history for this message

Sam Williams (sam-williams) wrote on 2010-01-27:

.home.samiam..cache.ubuntuone.log.oauth.login.log.txt Edit (65.8 KiB, text/plain; charset="utf-8")
.home.samiam..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (521 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (9.2 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Joshua Hoover (joshuahoover) wrote on 2010-01-27:

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.