[GRASS-dev] GRASS 8.0 and 8.1 from standalone installers still do not start for unprivileged users on windows 10

Doug Newcomb gistinker at gmail.com
Sun Jan 16 21:52:52 PST 2022


First ,
I must apologize for my intermittent communication, I am not able to check
email regularly this week.
I downloaded the most recent standalone installers tonight and the bug in
7.8.6 https://github.com/OSGeo/grass/issues/1965 is still there in the
WinGRASS-8.1.dev-7e9610cfd-28-Setup.exe
and WinGRASS-8.0.dev-ffb060a9c-36-Setup.exe binaries.


I see https://github.com/OSGeo/grass/pull/2068 has been merged into
8.0 release, but for some reason,

this does not seem to be fixing these standalone builds. Since this is
not an issue with the core grass code,

but with the mswindows/GRASS-Installer.nsi.tmpl file, is there the
possibility that the .nsi.tmpl file is not

being refreshed during the build process?

This all boils down to permissions on the etc/grass80.py file only set
to read/execute for System and Administrative groups,

not for local users.  All of the other python files in the etc
directory of the windows installation have the correct read/execute
permissions ,

as set in line 594 of the mswindows/GRASS-Installer.nsi.tmpl , which
was not changed in pull request 2068.

Pull request 2068 simply changed line 762 to match line 594 to give
the same permissions that all of the other python files in

the etc directory. This worked on the version compiled on my
development computer from source.  Unfortunately,

I will not be able to compile the current source code until I get back
to my development computer late this week.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20220117/eb018a3c/attachment.html>


More information about the grass-dev mailing list