ubuntuone-login crashed with ValueError in call_async(): Unable to guess signature from an empty dict

Bug #711216 reported by spartan15
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubuntuone-client

crash

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: ubuntuone-client 1.5.3-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic i686
Architecture: i386
Date: Tue Feb 1 13:24:20 2011
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-login
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-login
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=it_IT.utf8
 LANGUAGE=it_IT:it:en_GB:en
 LANG=it_IT.UTF-8
PythonArgs: ['/usr/lib/ubuntuone-client/ubuntuone-login']
SourcePackage: ubuntuone-client
Title: ubuntuone-login crashed with ValueError in call_async(): Unable to guess signature from an empty dict
UbuntuOneSyncdaemonExceptionsLog:

UbuntuOneUserSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 2097152
 on = False
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
spartan15 (spartan15) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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 #711162, 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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.