launchpad login service does not work with w3m
Bug #645024 reported by
Anand Kumria
This bug report is a duplicate of:
Bug #683337: Backport button element support to Lucid.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Undecided
|
Unassigned | ||
Bug Description
Whilst attempting to assist in the collection of information for #640432, I've been asked to run 'apport-collect 640432'.
Since the bug involves the X server, it means I am running the command from the console.
apport-collect fires up w3m in order to authenticate me but I am unable to proceed since the Launchpad login service does not work with w3m (I believe it is because w3m does not support the <button type="submit" ... >).
I think it is critical that launchpad allow logins from textual browsers in order that users collecting information on breakage of their graphical environment as able to assist as much as possible.
Revision history for this message
| Anand Kumria (wildfire) wrote | #1 |
To post a comment you must log in.
This is basically #556927. elinks does work but you need to login twice.
Once so that your login credentials are cached.
Then you need to abort apport-collect.
When you run it (apport-collect) again, elinks will see that you have a cookie, and then launchpad will throw you to the oauth screen to authorise apport-collect to provide information.