apport-collect: login to launchpad impossible in text mode using w3m (elinks works)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical SSO provider |
New
|
Undecided
|
Unassigned | ||
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
Sometimes it is necessary to run apport-collect in the absence of X (i.e. when reporting a bug on a headless server). In this scenario, apport-collect uses w3m to attempt to login to Launchpad. With w3m, it is impossible to "click" on the "Continue" button after entering one's Launchpad credentials. As a result, apport-collect is useless when run in text mode.
To workaround (from bug 645024):
apt-get install elinks
Login twice with elinks - once by using it to log into LP, and then once to get the cookie.
So - run apport-collect, login, abort apport-collect.
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.
affects: | launchpad → launchpad-foundations |
Changed in launchpad-foundations: | |
status: | Confirmed → Incomplete |
summary: |
apport-collect: login to launchpad impossible in text mode using w3m + (elinks works) |
description: | updated |
Changed in launchpad: | |
status: | Triaged → Invalid |
Changed in canonical-identity-provider: | |
assignee: | nobody → MANUELA BELLO NAYA (m-bnaya) |
status: | New → Invalid |
status: | Invalid → Opinion |
information type: | Public → Private |
Changed in launchpad: | |
status: | Invalid → Opinion |
assignee: | nobody → MANUELA BELLO NAYA (m-bnaya) |
information type: | Private → Private Security |
information type: | Private Security → Public |
Changed in canonical-identity-provider: | |
status: | Opinion → New |
Changed in launchpad: | |
status: | Opinion → Triaged |
assignee: | MANUELA BELLO NAYA (m-bnaya) → nobody |
Changed in canonical-identity-provider: | |
assignee: | MANUELA BELLO NAYA (m-bnaya) → nobody |
Can also confirm for links2 and lynx
Theses are able to activate the continue button, yet gets stuck after that, returning over and over again to the continue screen.