You didn't specify the URL to which to go ("2. go to this url"). I tried both 'https://launchpad.net/+openid-callback' and the really long one (with a nonce!) and, unsurprisingly, got "Your login was unsuccessful: Invalid openid.mode: '<No mode set>'". This seems very reasonable to me--why would someone go to the +openid-callback page unless they are in the middle of an openid dance? It also does not match your description of the bug.
You didn't specify the URL to which to go ("2. go to this url"). I tried both 'https:/ /launchpad. net/+openid- callback' and the really long one (with a nonce!) and, unsurprisingly, got "Your login was unsuccessful: Invalid openid.mode: '<No mode set>'". This seems very reasonable to me--why would someone go to the +openid-callback page unless they are in the middle of an openid dance? It also does not match your description of the bug.
I'm afraid I still do not understand your report.