Log-in loop when authenticating to Launchpad with Lynx

[Stewart Johnston]

I'm trying to report a bug from a tty, since I don't have a working desktop any more (since the last round of updates).

When logging into Launchpad with Lynx I am asked to sign in with my usual username and password, then get taken to an OpenID transaction in progress page with a Continue link.
Then taken to the "Authenticate to Launchpad" page with my Launchpad username & email address along with a "Sign in" link.
Selecting that brings me back to the OpenID transaction in progress page with a Continue link.
Back to Authenticate, back to Continue, etc etc.

I must be logged in, because my name & email address are displayed correctly on the authenticate page.

[Guilherme Salgado (salgado)]

I was able to login using w3m, you might want to give that a try

[Stewart Johnston (stooj)]

Not sure how to get apport defaulting to w3m, but will investigate.

[Gary Poster (gary)]

I am able to login with lynx. I did it yesterday.

Maybe this is a UI-on-lynx issue somehow? I'm marking incomplete so you can give us more information on how to duplicate, or what the problem is.

[Gary Poster (gary)]

I just had a bit of trouble with lynx on Lucid: no REFERER header on the last step of the process. By adding the following to /etc/lynx-cur/local.cfg , I was able to proceed again as usual:

REFERER_WITH_QUERY:PARTIAL

[Martin Erik Werner (arand)]

I get no success with REFERER_WITH_QUERY:PARTIAL

For me it seems to go through the login and confirmation ok but then get stuck after the confirmation of login has been sent.
What is seen is a "continue" form submit button in the upper right, and an "openid transaction in progress" text in the upper right. when activating the button it churns for a while and returns to the exact same spot.

[Martin Erik Werner (arand)]

The above problem was seen I used ubuntu-bug (apport-cli) to try to send a bug report.
If I simply navigate to launchpad an try to sign in there I get thrown back to the homepage after the "yes continue log me in"-page, with the homepage stating that I am not logged in.

it works with elinks but not with w3m or links2

[Gary Poster (gary)]

I'd like to support lynx. I have added this page to the help wiki to gather our collective wisdom: https://help.launchpad.net/API/EndUserHints

However, I cannot duplicate the problem that arand describes. It works on Lucid for me just fine.

(Moreover, fwiw, elinks did not work for me, but perhaps if you describe what you did on the EndUserHints page I, and others, could follow your steps.)

I have tried to dupe. This is what I saw, ignoring the various Cookie questions that lynx asks me.

- "OpenID transaction in progress" "Continue" -> I pressed the right arrow.
- "Launchpad Login Service" -> I typed in my email address and password, and then tabbed to the "(Submit)" and pressed Return.
- "Authenticate to https://edge.launchpad.net/" "Launchpad Login Service" "Logged in as Gary Poster" ... -> I again tabbed to "(Submit)" (next to "Yes, sign me in") and pressed Return
- "Authorize application to access Launchpad on your behalf" ... "The application identified as launchpad-branch-lander wants to access Launchpad on your behalf. What level of access do you want to grant?" ... -> I tabbed to "Change Anything" and pressed Return.
- "Almost finished ..." -> I pressed q y Return to quit Lynx, confirm, and have my launchpadlib application proceed.

I have not touched my lynx.cfg from a vanilla Lucid install, and only added the local.cfg with the one value I described earlier. Is yours a fresh Lucid install or an upgrade? If an upgrade, perhaps we should compare our lynx.cfg.

Gary

[Gary Poster (gary)]

Because of bug 586908, I wonder: are any of the people reporting problems with lynx using edge (one of the legion of Launchpad beta testers)? If not, the two bugs have a higher probability of being related.

[Gary Poster (gary)]

I believe the cookie problem I describe in comment seven for bug 586908 must be the same cause as this login problem. This would mean that everyone who uses lynx (or any browser that has strict interpretation of RFC 2109 in regards to cookie domains) and is *not* a Launchpad beta tester (https://edge.launchpad.net/~launchpad-beta-testers) will be unable to log in.

I'm going to mark this as a dupe of the other bug, since it describes the larger problem.