Opened 6 years ago
Closed 5 years ago
#2085 closed defect (fixed)
QGIS - can't find GRASS data
Reported by: | bakaniko | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | OSGeoLive13.0 |
Component: | OSGeoLive | Keywords: | QGIS, quickstart, GRASS |
Cc: | osgeolive@… |
Description
can't find GRASS data for quickstart. Files are corrupted or absent
They should be in /home/user/grassdata/nc_basic_spm_grass7/PERMANENT
There is some files but they weight 0 or 80 octets
Change History (12)
comment:2 by , 6 years ago
I believe that this problem is related to the permissions limitation imposed by GRASS. We've brought this up in the past: https://trac.osgeo.org/osgeolive/ticket/868, and never really resolved the problem, in my opinion.
The PERMANENT mapset is actually located under /usr/local/share which is owned by root. When you run GRASS as user1 you cannot start in that mapset, only the user1 mapset. But then you have read-only access to the data in the PERMANENT mapset. This is all by design, and works fine.
However, when running QGIS you cannot access the GRASS data under the PERMANENT, not with the QGIS Browser and not the GRASS Tools plugin. The error that appears is:
Unable to make mapset element: .tmp/osgeo Permission denied
In the QGIS quickstart there is a Note: explaining:
Please open a terminal and execute the following: "sudo chmod -R 0755 /usr/local/share/grass/nc_basic_spm_grass/"
If we are going to put that into the quickstart, then why not just have it done in the build script?
The other alternative is to put some layers into the user1 mapset (instead of PERMANENT) - which is read/write for user - and have the QGIS quickstart access only on those. Other layers will stay in PERMANENT for read only use (in GRASS) in multiuser workshop situations.
Regards, Micha
comment:3 by , 6 years ago
Also discussed 2 years ago: https://trac.osgeo.org/osgeolive/ticket/1740
I wonder what happened between 11.0 (when the ticket was closed) and 12.0 ??
comment:4 by , 6 years ago
It is not a good security practice to have user accounts have permissions outside their home folder, and this is something that has been discussed a lot in the past. This is why we have included the workaround in the quickstart and not in the build scripts.
comment:5 by , 6 years ago
Regarding security practice I totally agree, but the QGIS quickstart doesn't work as is.
My "Plan B" is to stock the user1 mapset with some layers, and change the QGIS quickstart to use only those. That leaves the GRASS permissions setup as it should be, and side-steps the problem with QGIS accessing GRASS data.
comment:6 by , 6 years ago
Milestone: | OSGeoLive12.0 → OSGeoLive13.0 |
---|
Ticket retargeted after milestone closed
comment:9 by , 5 years ago
comment:10 by , 5 years ago
Summary: | QGIS quickstart - can't find GRASS data → QGIS - can't find GRASS data |
---|
comment:11 by , 5 years ago
comment:12 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
12dev beta2