Comment 8 for bug 598464

Revision history for this message
Michael Nelson (michael.nelson) wrote :

The QA fix for this landed a few days ago on devel (r11209) which was merged into db-devel (r9570), but still waiting for staging to be updated to include this revision (r9565 at time of writing).

To QA:

1) Visit login.staging.launchpad.net and create a new account there (ie. an SSO only account)
2) After completing the verification and being logged in, visit staging.launchpad.net and ensure the oops is not triggered.