oneconf-service crashed with TypeError in _sso_login_result(): 'NoneType' object is not subscriptable

[John Belton]

This failure appeared when I was confirming the "system update" confirm in the terminal having already run it using update manager as I had two update that didn't complete a couple of days ago without using this. I don't know why it crashed unless my password may have been corrupted at some point but I can't think why?

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: oneconf 0.2.6.2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Fri Sep 16 11:17:56 2011
ExecutablePath: /usr/share/oneconf/oneconf-service
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/oneconf/oneconf-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
PythonArgs: ['/usr/share/oneconf/oneconf-service']
SourcePackage: oneconf
Title: oneconf-service crashed with TypeError in _sso_login_result(): 'NoneType' object is not subscriptable
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/oneconf/networksync/__init__.py", line 82, in _sso_login_result
     authorizer = OAuthAuthorizer(token_key=credential['token'],
 TypeError: 'NoneType' object is not subscriptable
UpgradeStatus: Upgraded to oneiric on 2011-09-04 (11 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

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 #851997, 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.