** Description changed:

- Binary package hint: python-launchpadlib
+ [Impact]
  
- Running lp:svammel to do a dry run mass bugfiling against LP, I get
- prompted to authorize my system to connect to launchpad, which is neat.
- But on a subsequent invocation of the tool, it fails with:
+ [Development Fix]
+ 
+ [Stable Fix]
+ 
+ [Test Case]
+ 
+ [Regression Potential]
+ 
+ [Original Report]
+ Running lp:svammel to do a dry run mass bugfiling against LP, I get prompted 
to authorize my system to connect to launchpad, which is neat.  But on a 
subsequent invocation of the tool, it fails with:
  
   Traceback (most recent call last):
    File "file-failures.py", line 50, in <module>
      init(args.serviceroot, 'testing', '~/.launchpadlib/cache/')
    File "/home/vorlon/devel/linaro/svammel/config.py", line 96, in init
      set_launchpad(service_root, appid, cachedir)
    File "/home/vorlon/devel/linaro/svammel/config.py", line 72, in 
set_launchpad
      lp = Launchpad.login_with(appid, root, cachedir)
    File "/usr/lib/pymodules/python2.7/launchpadlib/launchpad.py", line 538, in 
login_with
      credential_save_failed, version)
    File "/usr/lib/pymodules/python2.7/launchpadlib/launchpad.py", line 341, in 
_authorize_token_and_login
      authorization_engine.unique_consumer_id)
    File "/usr/lib/pymodules/python2.7/launchpadlib/credentials.py", line 273, 
in load
      return self.do_load(unique_key)
    File "/usr/lib/pymodules/python2.7/launchpadlib/credentials.py", line 322, 
in do_load
      return Credentials.from_string(credential_string)
    File "/usr/lib/pymodules/python2.7/launchpadlib/credentials.py", line 89, 
in from_string
      credentials.load(StringIO(value))
    File 
"/usr/lib/python2.7/dist-packages/lazr/restfulclient/authorize/oauth.py", line 
165, in load
      CREDENTIALS_FILE_VERSION, 'consumer_key')
    File "/usr/lib/python2.7/ConfigParser.py", line 610, in get
      raise NoOptionError(option, section)
   ConfigParser.NoOptionError: No option 'consumer_key' in section: '1'
  
  At James Westby's suggestion, I had a peek inside gnome-keyring with
  seahorse and found this as the 'password' value of the 'network
  password' token:
  
    [1]
  
  Presumably there should be a real password here instead. :)
  
  People experiencing this problem can work around it by opening their
  gnome keyring, and deleting the broken password.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745801

Title:
  system-based authorization broken in gnome-keyring: NoOptionError: No
  option 'consumer_key' in section: '1'

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpadlib/+bug/745801/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to