-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please improve 'Missing dependency' error message #21250
Comments
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Markus Neteler (Markus Neteler) ... I would be glad to know the GRASS startup script name Processing expects. I tick again "Causes crash or corruption" because it simply doesn't work so far.
|
Author Name: Markus Neteler (Markus Neteler) See also bug #21142 |
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Alexander Bruy (@alexbruy) Fixed in changeset "75926f52aaf479bbe663978b05b7ba216cea137e".
|
Author Name: Alexander Bruy (@alexbruy) "Missing dependency" message was removed from Processing during UI/UX improvements. But I added GRASS path to the similar message, hope it helps.
|
Author Name: Markus Neteler (Markus Neteler)
Original Redmine Issue: 13188
Affected QGIS version: 2.10.1
Redmine category:processing/grass
Assignee: Victor Olaya
Using QGIS 2.10 on Linux (also elsewhere), does not let me run GRASS GIS 7 through processing any more.
The issue is likely that Processing searches for a specific name to start GRASS 7 ('grass', 'grass7', 'grass70', 'grass-7', ... who knows??) which is not present on the system as such.
Subsequently the following error message pops up but does not tell me what it was actually looking for:
Solution: include in the message the command string which failed (the hardcoded? name which Processing actually expects here so that the user can create a link to the true startup script name of GRASS 7). The current error message above is rather useless as such.
I tried to find the name Processing expects in the Python code but could not identify it.
A lot of people have this issue (see gis.stackexchange.com etc) but no clue how to solve it.
The text was updated successfully, but these errors were encountered: