Opened 7 years ago

Last modified 5 years ago

#847 assigned defect

i2p attempts to start lynx on launch, a terminal-based web browser

Reported by: sponge Owned by: sponge
Priority: minor Milestone:
Component: apps/systray Version: 0.9.4
Keywords: lynx Cc:
Parent Tickets: Sensitive: no

Description

System is terminal only, i2p launches lynx… that will never work!

Subtickets

Change History (12)

comment:1 Changed 7 years ago by sponge

Summary: i2p attepmts to start lynx on launch, a terminal-based web browseri2p attempts to start lynx on launch, a terminal-based web browser

comment:2 Changed 7 years ago by zzz

huh? what could be better for a "terminal-only" system than a "terminal-based web browser"? Why won't it work? What should we do instead?

comment:3 Changed 7 years ago by zzz

Component: router/generalapps/systray
Owner: changed from zzz to sponge
Status: newassigned

no response, reassigning to OP for more info or to close

comment:4 Changed 7 years ago by sponge

Don't launch lynx. It does _NOT_ come up on the terminal. It sits there in limbo, eating RAM with no way to get to the lynx interface. Lynx does not 'pop up' any place, it is headless, and only accessible via serial port console.

comment:5 Changed 7 years ago by dg

lynx runs on Linux servers I've installed on, noticed it on Debian 6/7 & CentOS 5/6 when i2p starts
more or less useless to me and i expect many people who install i2p on a headless boxes..

<+sponge> I propose that —console installs install a config that does not launch the browser, or to provide another switch to turn off the 'launch browser at startup' during install.

disabling the "start browser on i2p init" (paraphrased..) option does fix this

comment:6 Changed 7 years ago by dg

3215 ? Sl 0:13 \_ /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java […]
3298 ? S 0:00 \_ /usr/bin/www-browser http://127.0.0.1:7657/

ps waxf output, trimmed Java crap
this is with the "Open Router Console in web browser at startup" ("net.i2p.apps.systray.UrlLauncher? http://127.0.0.1:7657/") option on, as the default does.

comment:7 Changed 7 years ago by DISABLED

or just change clientApp.4.startOnLoad to false as the default…

comment:8 Changed 7 years ago by sponge

We know that, the point is to do it for you, and to remove stuff that is not going to work.

comment:9 Changed 7 years ago by DISABLED

i see what you mean, in that case i will put my vote on removal of the entire "open a browser" feature.

comment:10 Changed 6 years ago by str4d

Milestone: 0.9.5

comment:11 in reply to:  5 Changed 6 years ago by zzz

Replying to dg:

<+sponge> I propose that —console installs install a config that does not launch the browser, or to provide another switch to turn off the 'launch browser at startup' during install.

@sponge I don't think we can assume a headless install means that all future instantiations are headless.

@sponge Please propose a solution to detect headless at runtime from Java in URLLauncher. See e.g. RouterConsoleRunner?.startTrayApp(), note that it overrides java.awt.headless, possibly before URLLauncher runs.

comment:12 Changed 5 years ago by zzz

related / dup: #1317

Note: See TracTickets for help on using tickets.