Opened 5 years ago
Last modified 4 years ago
#3957 new defect
Clicking Help on first screen does nothing
Reported by: | jidanni | Owned by: | |
---|---|---|---|
Priority: | trivial | Milestone: | 7.8.3 |
Component: | Startup | Version: | git-releasebranch78 |
Keywords: | help, Debian | Cc: | |
CPU: | Unspecified | Platform: | Linux |
Description
It's the user's very first use...
$ grass
Then click Help. Nothing happens. Some error message should appear somewhere.
Maybe this help button should be greyed out unless the current screen is doing a action that has a help page.
Change History (10)
comment:1 by , 5 years ago
Keywords: | help added |
---|---|
Milestone: | → 7.8.2 |
Version: | unspecified → git-releasebranch78 |
comment:2 by , 5 years ago
OK, today it is working. Standard Debian sid install. BROWSER=chromium. Maybe it is now working because I have initialized the databases, etc. However a vanilla
# su - some_vanilla_account $ DISPLAY=:0 grass BROWSER=chromium DISPLAY=:0 grass Starting GRASS GIS... (gis_set.py:16417): dbind-WARNING **: 01:53:33.208: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
and then clicking Help does nothing.
comment:3 by , 5 years ago
Same with
$ GRASS_HTML_BROWSER=lynx DISPLAY=:0 grass $ GRASS_HTML_BROWSER=chromium DISPLAY=:0 grass
comment:5 by , 5 years ago
Keywords: | Debian added |
---|---|
Platform: | Unspecified → Linux |
comment:6 by , 5 years ago
Putting them on the command line exports them.
$ a=b set|grep a=b $ a=b env|grep a=b a=b
comment:9 by , 5 years ago
Milestone: | → 7.8.3 |
---|
comment:10 by , 4 years ago
If you have xdg-open
available, this should just work. It's the default in grass.py
for all systems except Windows and macOS.
I'm getting some strange behavior when I actually set the variable:
GRASS_HTML_BROWSER=firefox grass GRASS_HTML_BROWSER=chromium grass
However, in that case, not even g.manual is working. Anybody else observing this? If yes, can you just open a new issue on GitHub for that?
Replying to jidanni:
That's unexpected. It should open a browser and therein the helptext.html.
It respects the env variable
GRASS_HTML_BROWSER
and, if undefined, it searches for numerous candidates:Maybe your's is missing?
The question is: which operating system do you use? And: is any web browser installed?