Ubuntu
ubuntuone-client package

ubuntuone.SyncDaemon.State - ERROR - CONNECTED_WITH_METAQ --[SYS_CONNECTION_MADE]--> ERROR!!!

Bug #487112 reported by antok on 2009-11-23

This bug report is a duplicate of: Bug #457147: BadTransition: SYS_CONNECTION_MADE - Ubuntu One crashes coming out of sleep/hibernate. 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

may it duplicate with any other report

ProblemType: Bug
.home.antok..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = True
connect = 0
show_applet = 0
bookmarked = True
Architecture: i386
Date: Mon Nov 23 21:17:48 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
LANG=id_ID.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic i686

Tags:

Revision history for this message

antok (ananto-sulistyo) wrote on 2009-11-23:

.home.antok..cache.ubuntuone.log.oauth.login.log.txt Edit (273.9 KiB, text/plain; charset="utf-8")
.home.antok..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (497 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 (1.1 KiB, text/plain; charset="utf-8")

Jakob Unterwurzacher (jakobunt) on 2009-11-23

summary:

- maybe network
+ ubuntuone.SyncDaemon.State - ERROR - CONNECTED_WITH_METAQ
+ --[SYS_CONNECTION_MADE]--> ERROR!!!

Revision history for this message

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

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