gwibber-bugs team mailing list archive
-
gwibber-bugs team
-
Mailing list archive
-
Message #00921
[Bug 651088] Re: Ubuntu one won't launch, ubuntuone-preferences crashes "gnomekeyring.BadArgumentsError"
Recently I've lost access to Ubuntu One through my Ubuntu 10.04.02.
Terminal output looks very much the same as in Julien's case:
ubuntuone-preferences
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
Hector's work around seemed to do the trick and ubuntu one preferences
windows appeared but unfortunately I didn't manage to synchronize:
ubuntuone-preferences
Removing stale, deceptive pid file.
Apache CouchDB has started, time to relax.
Browse your desktop CouchDB at file:///home/mc/.local/share/desktop-couch/couchdb.html
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in maybe_handle_message
self._handler(*args, **kwargs)
File "/usr/bin/ubuntuone-preferences", line 1084, in got_newcredentials
self.present()
File "/usr/bin/ubuntuone-preferences", line 1075, in present
self.dialog.request_quota_info()
File "/usr/bin/ubuntuone-preferences", line 687, in request_quota_info
callback=self.got_quota_info)
File "/usr/bin/ubuntuone-preferences", line 170, in make_rest_request
token = get_access_token(keyring)
File "/usr/bin/ubuntuone-preferences", line 124, in get_access_token
'oauth-consumer-key': 'ubuntuone'})
BadArgumentsError
ERROR:ubuntuone-preferences:Invalid request token: ML9......................................
ERROR:ubuntuone-preferences:Uwierzytelnienie się nie powiodło.
ERROR:ubuntuone-preferences:Invalid request token: ML9......................................
ERROR:ubuntuone-preferences:Uwierzytelnienie się nie powiodło.
ERROR:ubuntuone-preferences:[Failure instance: Traceback (failure with no frames): <class 'dbus.exceptions.DBusException'>: org.freedesktop.DBus.Python.KeyError: Traceback (most recent call last):
File "/usr/lib/pymodules/python2.6/dbus/service.py", line 702, in _message_cb
retval = candidate_method(self, *args, **keywords)
File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/dbus_interface.py", line 1313, in get_info
mdobj = self.fs.get_by_path(path.encode('utf-8'))
File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/filesystem_manager.py", line 550, in get_by_path
mdid = self._idx_path[path]
KeyError: '/home/mc/.ubuntuone/Purchased from Ubuntu One'
]
--
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.