Ubuntu
ubuntuone-client package

crashed when clicked on applet

Bug #466076 reported by skippergimp on 2009-10-31

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 4 people

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

Bug Description

Binary package hint: ubuntuone-client

tried to click on cloud and it crashed. So far, only happened the once. Might be a one off.

ProblemType: Bug
.home.danny..cache.ubuntuone.log.oauth.login.log:
Starting Ubuntu One client version 1.0.2
[Errno socket error] [Errno -2] Name or service not known
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Quit Error: Method "quit" with signature "" on interface "com.ubuntuone.SyncDaemon.SyncDaemon" doesn't exist
.home.danny..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = False
connect = 0
show_applet = 1
bookmarked = True
Architecture: i386
Date: Sat Oct 31 05:12:49 2009
DistroRelease: Ubuntu 9.10
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
Uname: Linux 2.6.31-14-generic i686

Tags:

Revision history for this message

skippergimp (dapo-dapoland) wrote on 2009-10-31:

.home.danny..cache.ubuntuone.log.syncdaemon.exceptions.log.txt Edit (493 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 (3.6 KiB, text/plain; charset="utf-8")

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