Ubuntu
ubuntuone-client package

ubuntu_one crashed when network changed

Bug #503793 reported by tx on 2010-01-06

This bug report is a duplicate of: Bug #458393: BadTransition: SYS_SERVER_RESCAN_DONE. Edit Remove

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	ubuntuone-client (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: ubuntuone-client

There an more than one AP around, when I changed from one to another, ubuntu_one detects a fatal error

ProblemType: Bug
.home.tx..config.ubuntuone.syncdaemon.conf:
[bandwidth_throttling]
read_limit = 0
write_limit = 0
on = False
.home.tx..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = True
connect = 0
show_applet = 1
bookmarked = True
Architecture: amd64
Date: Wed Jan 6 21:30:32 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: fglrx
Package: ubuntuone-client 1.0.3-0ubuntu1
PackageArchitecture: all
ProcEnviron:
LANGUAGE=zh_CN.UTF-8
LANG=zh_CN.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-17-generic x86_64

Tags:

Revision history for this message

tx (372046933-qq) wrote on 2010-01-06:

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

Revision history for this message

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

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.