juju-quickstart fires up w3m on a server machine, which is not useful
Bug #1292028 reported by
Robie Basak
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-quickstart |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When testing juju-quickstart, I used an Ubuntu cloud image. I expected it to finish by giving me a URL to view the Juju GUI, or something like that. Instead, it fired up w3m, which isn't capable of accessing the Juju GUI anyway. Quitting w3m didn't give me a useful URL to access, either.
I am used to trying things out on test VMs, instead of letting them trample on my main desktop machine.
Tools like ubuntu-bug seem to be able to detect this situation, and give me a URL to visit from an alternate machine. It would be nice if juju-quickstart can also do this.
Revision history for this message
| Francesco Banconi (frankban) wrote | #1 |
| Changed in juju-quickstart: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Francesco Banconi (frankban) wrote | #2 |
| Changed in juju-quickstart: | |
| importance: | Medium → Low |
To post a comment you must log in.
We should check if there is an X session available and assume --no-browser if that's not the case.
I agree it does not make sense to open the GUI (a js app) using a term browser.