Ubuntu
ubuntuone-client package

Ubuntu One reported an error after resuming from suspend.

Bug #465749 reported by Danté on 2009-10-30

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

This bug affects 18 people

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

Bug Description

Binary package hint: ubuntuone-client

Summery says it all, really. Wasnt really expecting a fault then...how odd....

ProblemType: Bug
.home.dante..cache.ubuntuone.log.oauth.login.log:
Starting Ubuntu One client version 1.0.2
Quit Error: Method "quit" with signature "" on interface "com.ubuntuone.SyncDaemon.SyncDaemon" doesn't exist
.home.dante..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = True
connect = 0
show_applet = 2
Architecture: i386
Date: Fri Oct 30 22:58:04 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Tags: ubuntu-unr
Uname: Linux 2.6.31-14-generic i686

Tags:

Revision history for this message

Danté (dante-ashton) wrote on 2009-10-30:

.home.dante..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (3.2 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 (861 bytes, text/plain; charset="utf-8")

Revision history for this message

egribali (egribali) wrote on 2009-10-31:

same problem here

Revision history for this message

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

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.