Software centre fails to load previous purchases due to Error

[Mark East]

When I click on 'Re-install previous purchases' in the software centre it hangs for a while with the loading icon and then returns to the main page. I get the same thing when turning on recommendations. When I run from the terminal I see that it is throwing the following error:

2012-05-07 20:19:53,569 - softwarecenter.backend.login_sso - ERROR - _on_credentials_error for Ubuntu Software Center: dbus.Dictionary({dbus.String(u'errtype'): dbus.String(u'AssertionError'), dbus.String(u'message'): dbus.String(u'Assertion failed.')}, signature=dbus.Signature('ss')) ()

The machine is on 12.04 and was upgraded from 11.10. I see that it is due to credentials but I have cleared $HOME/.cache/software-centre and deleted the software centre entry in passwords and encryption keys. I must have missed something. Just to note that this is not happening on my other machines which are a mix of upgraded 12.04 and fresh install 12.04. If something like this happens it should probably prompt the user to re-enter credentials if it does happen.

Can anyone give me a work around at present because at the moment I cant install my purchased game and I would quite like to play it :).

[Gary Lasker (gary-lasker)]

Hi Mark! Thanks for your email. We have had some people report this (see bug 994632) and the problem turned out to be that, after upgrading, they are missing the ubuntu-sso-client-gtk package. Please type the following in a terminal to see if it's installed:

  $ apt-cache policy ubuntu-sso-client-gtk

If it is not installed, please just install it as shown:

  $ sudo apt-get install ubuntu-sso-client-gtk

If will mark this bug as a duplicate of bug 994632. If it turns out that this was not the cause of the problem you are seeing, please note that here and reopen it.

Thanks again for your help!

[Mark East (feasty)]

Hi Gary, Yeah it wasn't installed. I've installed it and it's now working again. Thanks.

[Gary Lasker (gary-lasker)]

Great news, thank you, Mark! The fix for this issue (bug 994632) is already commited and will be hitting the SRU queue soon.

Thank you again for your help and for your quick response!