Ubuntu
ubuntuone-client package

ubuntuone-client-applet crashed with AttributeError in from_token_and_callback()

Bug #450386 reported by Matthew Paul Thomas on 2009-10-13

This bug report is a duplicate of: Bug #415272: ubuntuone crash on start. 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

Apport says:

ProblemType: Crash
.home.mpt..cache.ubuntuone.log.oauth.login.log:
Starting Ubuntu One client version 1.0.0
[Errno socket error] [Errno -2] Name or service not known
.home.mpt..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
show_applet = 1
connected = False
connect = 0
bookmarked = True
Architecture: i386
Date: Tue Oct 13 14:00:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/ubuntuone-client-applet
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: wl
Package: ubuntuone-client-gnome 1.0.0-0ubuntu1
ProcCmdline: /usr/bin/python /usr/bin/ubuntuone-client-applet
ProcEnviron:
LANGUAGE=en_NZ.UTF-8
PATH=(custom, user)
LANG=en_NZ.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
PythonArgs: ['/usr/bin/ubuntuone-client-applet']
SourcePackage: ubuntuone-client
Title: ubuntuone-client-applet crashed with AttributeError in from_token_and_callback()
Uname: Linux 2.6.31-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare video

Tags:

Revision history for this message

Matthew Paul Thomas (mpt) wrote on 2009-10-13:

Traceback.txt Edit (661 bytes, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (747 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-10-13: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #423383, so 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. Please continue to report any other bugs you may find.