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

[Michael]

I got this error at login. I do not know what oneconf is.

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 x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Fri Sep 16 10:23:03 2011
ExecutablePath: /usr/share/oneconf/oneconf-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/oneconf/oneconf-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.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-14 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Nick Moffitt (nick-moffitt)]

I got this crash shortly after doing a dist-upgrade with aptitude (no changes occurred) followed by an apt-get clean. I do not use U1 on this system, so I'm at a loss as to why this software would be even running.

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