Is it the same error for what the pull request fixes?
"/Applications/QGIS3.app/Contents/MacOS/grass/etc/colors/grass: Permission
denied"
That should be fixed, but GRASS7 still has unresolved problems in the macOS
package. I haven't had time to look at it.
> On Jul 3, 2018, at 6:02 PM, Mr. Sta
The fix is a pull request that appeared in a later email in this thread, and
that has been merged and should be in the latest release.
> On Jul 3, 2018, at 5:28 PM, Mr. Stace D Maples
> wrote:
>
> This thread is "Mac QGIS 3 GRASS fix, but I don't see anything that fixes the
> problem. Has any
On 23 March 2018 at 11:57, Nyall Dawson wrote:
> On 23 March 2018 at 11:35, Vaclav Petras wrote:
>
>>
>> I'm not sure what exactly you want to use os.path.isfile() for, but
>> etc/colors/grass is a file in GRASS GIS since 7.2, so os.path.isfile() will
>> return True. In unix, you can see if the f
On 23 March 2018 at 11:35, Vaclav Petras wrote:
>
> I'm not sure what exactly you want to use os.path.isfile() for, but
> etc/colors/grass is a file in GRASS GIS since 7.2, so os.path.isfile() will
> return True. In unix, you can see if the file is executable with
> os.access(name, os.X_OK) (not
I figured it out - the break in searchFolder() only breaks the cmd loop,
leaving the walking to continue, eventually finding the last occurrence of the
cmd. I posted my fix to the bug report.
> On Mar 22, 2018, at 8:35 PM, Vaclav Petras wrote:
>
>
>
> On Thu, Mar 22, 2018 at 6:56 PM, Nyall
On Thu, Mar 22, 2018 at 6:56 PM, Nyall Dawson
wrote:
> On 23 March 2018 at 08:47, William Kyngesburye
> wrote:
> > Well, it seems that running any GRASS Processing coughs up this error.
> > Mystery to me, permissions are correct for the app, nothing should be
> > writing to the app, and if it is
Yes, that looks like the source of the problem. The os.walk() finds the color
file named "grass" before it has a chance to find the real "grass72" file at
the top level of the grasspath. Though this is odd since it looks like os.walk
by default should return a folder's info before it walks sub
On 23 March 2018 at 08:47, William Kyngesburye wrote:
> Well, it seems that running any GRASS Processing coughs up this error.
> Mystery to me, permissions are correct for the app, nothing should be
> writing to the app, and if it is trying that's wrong.
>
> The error doesn't help me try to figure
Well, it seems that running any GRASS Processing coughs up this error. Mystery
to me, permissions are correct for the app, nothing should be writing to the
app, and if it is trying that's wrong.
The error doesn't help me try to figure out what's going on. Help would be
appreciated.
> On Mar
