CredentialsError, stuck on "Getting Information, Please wait"

Bug #1266226 reported by Dario Bertini
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubuntu-sso-client (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I've been unable to sync my files with ubuntu one in the last month and a half

It seems the problem is the same as this old bug, that has supposedly been fixed: https://bugs.launchpad.net/ubuntu/+source/ubuntu-sso-client/+bug/986117

inside the log in fact I found these lines:

2014-01-05 17:19:25,802:802.46591568 - ubuntu_sso.main - INFO - CredentialsManagement: emitting CredentialsFound with app_name dbus.String(u'Ubuntu One').
2014-01-05 17:19:25,834:834.37204361 - ubuntu_sso.utils.webclient.qtnetwork - INFO - Proxy is disabled.
2014-01-05 17:19:27,266:266.325950623 - ubuntu_sso.main - INFO - 'CredentialsManagement': emitting 'CredentialsCleared' with args (dbus.String(u'Ubuntu One'),) and kwargs {}
2014-01-05 17:19:27,269:269.14191246 - ubuntu_sso.credentials - ERROR - find_credentials (app_name: Ubuntu One): Problem while getting credentials from the keyring.
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/ubuntu-sso-client/ubuntu_sso/credentials.py", line 104, in inner
    result = yield f(self, *a, **kw)
DBusException: org.freedesktop.Secret.Error.NoSuchObject: The '/org/freedesktop/secrets/collection/login/1833' object does not exist
2014-01-05 17:19:27,271:271.615028381 - ubuntu_sso.main - ERROR - 'CredentialsManagement': emitting 'CredentialsError' with args (dbus.String(u'Ubuntu One'), DBusException(dbus.String(u"The '/org/freedesktop/secrets/collection/login/1833' object does not exist"),)) and kwargs {}
2014-01-05 17:19:27,528:528.160095215 - ubuntu_sso.credentials - INFO - _login_or_register: login_only=True email=None.
2014-01-05 17:19:27,541:541.541099548 - ubuntu_sso.credentials - INFO - find_credentials: self.app_name dbus.String(u'Ubuntu One'), result is {}? False
2014-01-05 17:19:27,542:542.634963989 - ubuntu_sso.main - INFO - CredentialsManagement: emitting CredentialsFound with app_name dbus.String(u'Ubuntu One').
2014-01-05 17:19:35,809:809.231042862 - ubuntu_sso.main - INFO - Shutting down, calling <function shutdown_func at 0x13399b0>.

I tried to reproduce the output of these log lines by killing the syncdaemon and restarting it, but I only got this output once

Still, I think this is related to the actual error, since the stuck ubuntuone-control-panel-qt displays the AUTH_FAILED error underneath

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntu-sso-client 13.10-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Sun Jan 5 17:26:43 2014
InstallationDate: Installed on 2011-10-31 (797 days ago)
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: ubuntu-sso-client
UpgradeStatus: Upgraded to saucy on 2013-10-09 (87 days ago)

Revision history for this message
Dario Bertini (berdario) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubuntu-sso-client (Ubuntu):
status: New → Confirmed
Revision history for this message
Dario Bertini (berdario) wrote :

I worked around this issue with these instructions: https://one.ubuntu.com/help/faq/what-should-i-do-if-authentication-fails-auth_failed-state/

needless to say, I didn't manually remove my computer synchronization... it seems suspicious to me that the web interface shows exactly 10 devices (some of these were devices I reinstalled from scratch), maybe there's an hardcoded limit and by adding new devices old ones might get deactivated? (weird, since it should prefer devices that haven't logged in months, not my main computer)

Also, using seahorse is easy enough, but the ubuntu one preferences should handle this automatically (or at the very least let the user know where this information is stored)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.