← Back to team overview

gwibber-bugs team mailing list archive

[Bug 651088] Re: Ubuntu one won't launch, ubuntuone-preferences crashes "gnomekeyring.BadArgumentsError"

 

To recover from this situation, you can erase/move the "by_default" key collection Gwibber creates through the keyring manager of Gnome.
It is found in the ~/.gnome2/keyrings/ directory.
Mine was broken, no way to edit or change password from the seahorse app, and it's still broken afterward once recreated by gwibber; but at least gwibber starts again.
The "Add" button for the twitter  registration still is not showing itself after the login from twitter is done successfully. I cannot add a twitter account to the list still.
So Gwibber is back, but still not functional with Twitter.

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/651088

Title:
  Ubuntu one won't launch, ubuntuone-preferences crashes
  "gnomekeyring.BadArgumentsError"

Status in Gwibber:
  New
Status in Ubuntu One Client:
  Confirmed

Bug description:
  On 10.04.1, rather fresh install (two weeks)
  ubuntuone-client 1.2.2-0ubuntu2

  Worked first but without changing anything in config files, on morning
  Ubuntu one won't launch at all, and starting ubuntuone-preferences in
  terminal output :

  Traceback (most recent call last):
    File "/usr/bin/ubuntuone-preferences", line 1143, in <module>
      prefs_dialog = UbuntuOneDialog()
    File "/usr/bin/ubuntuone-preferences", line 535, in __init__
      self.__construct()
    File "/usr/bin/ubuntuone-preferences", line 975, in __construct
      self.devices.list_devices()
    File "/usr/bin/ubuntuone-preferences", line 377, in list_devices
      token = get_access_token(self.keyring)
    File "/usr/bin/ubuntuone-preferences", line 124, in get_access_token
      'oauth-consumer-key': 'ubuntuone'})
  gnomekeyring.BadArgumentsError

  I tried reinstalling, removing config files... The bug occurs everytime. No trace of anything like it in google, hope I'm not the only one...
  syncdaemon's log attached.