Recent Forum Posts
From categories:
page »

Just added updated 'preview' releases for GRASS 7.4 and 7.6 with all the fixes included.

I just posted the latest, advanced GRASS 7.7 Mac binary. It has many bug fixes for the Mac, as well as new features. As with all my new binaries, this is fully 64 bit and uses advanced wxPython 4. As far as I can tell, the only remaining serious bug is that the digitizer is still broken.

These fixes should be ported to versions 7.6 and 7.4 very soon. I will post new binaries for those as soon as the fixes are in. The development team is moving to release a new stable v. 7.4.2 soon, followed by a stable 7.6.0. Building on a Google Summer of Code project, we are now testing migration to Python 3.


Thanks. I can now reproduce this. It needs to be reported as a bug.

Re: GRASS 7 crashing by cmbarton54cmbarton54, 26 Jul 2018 20:17

I've just posted a new GRASS 7.5 dev binary. Mostly it is a fix for m.nviz.image.

Re: Releases and updates by cmbarton54cmbarton54, 26 Jul 2018 20:14

I am using the button on the right side of the map layer that says "Click to edit layer settings" on mouse over and then selecting remove from the menu that pops up.

The app did not crash when I right clicked on the layer and selected remove bust crashes everytime I use the button.

Re: GRASS 7 crashing by putnajoeputnajoe, 23 Jul 2018 20:30

This is odd. I am running the same OS and just tried it with 7.4.0 and 7.1. No problem.

How are you removing the layers? Using right click? The remove button on the button bar? Other means?

Re: GRASS 7 crashing by cmbarton54cmbarton54, 12 Jul 2018 00:06

I did just try the North Carolina data and the same behavior exists with a segmentation fault occurring when removing a raster map layer.

Re: GRASS 7 crashing by putnajoeputnajoe, 11 Jul 2018 22:11

I have tried GRASS 7.4.0 and GRASS 7.4.1 on High Sierra 10.13.5 as the bundled versions would be great so SIP does not have to be disabled. I was using the spearfish data that our Geography professor who uses the application always uses and just tried to add and remove any raster map layer from the list. The error in the terminal when the program crashes is /Applications/ line 3: 9516 Segmentation fault: 11 /Applications/ "$@" for GRASS 7.4.1 and /Applications/ line 3: 9375 Segmentation fault: 11 /Applications/ "$@" for GRASS 7.4.0. I will try the South Carolina data.

Re: GRASS 7 crashing by putnajoeputnajoe, 11 Jul 2018 22:06

Could you describe this in more detail? Which version of GRASS, which OS? Describe the sequence of actions that causes the crash. Are there any error messages in the terminal or console? Have you tried this with the standard GRASS demo data from South Carolina?

Re: GRASS 7 crashing by cmbarton54cmbarton54, 11 Jul 2018 19:45

GRASS 7 is crashing every time when removing a raster layer on macOS when using the app bundled with the frameworks. Any suggestions on how to correct this? Thank you.

GRASS 7 crashing by putnajoeputnajoe, 11 Jul 2018 18:55

I've just posted a new
GRASS 7.5 dev binary with some additional bug fixes for interface issues and more general updates.

I've also made new versions of the download links. Hopefully these work better and do not produce corrupted files.

Re: Releases and updates by cmbarton54cmbarton54, 11 Jun 2018 22:20

I just posted a new GRASS 7.5 dev binary. It has a fix for the menu bar bug switching between 2D and 3D mode.

New GRASS 7.5 dev binary by cmbarton54cmbarton54, 07 Apr 2018 00:09

I just updated these stable versions with a bug fix for a problem in setting display and output fonts.

Releases and updates by cmbarton54cmbarton54, 07 Apr 2018 00:08


Someone else had a similar problem but other people have not. My guess (truly a guess) is that is some kind of issue with downloading from Google drive, the only place I have available to post the binaries right now. If you send me your email, I can try to provide a temporary alternative download location and see if that works. Contact me at moc.liamg|notrab.leahcim.c#moc.liamg|notrab.leahcim.c.


Right. It is not compiled with PostGIS support at the present. This is a compiler option that may or may not be easy to implement. At the moment, I'm still trying to make sure that the new way of compiling works and get GRASS to the level of functionality that it was with the old method. I also am hoping to work with others on the dev team to deal with several nasty bugs that have appeared with the switch to 64bit wxPython. I do hope to be able to compile new versions in the coming weeks with some bug fixes.

When trying to install GRASS 7.x, on opening the unzipped dmg image, I receive the following message:

The following disk images could not be opened
image: grass-7.4.0.dmg
reason: no mountable file systems

Though results for GRASS 7.4 are shown, the problem occurs with all three GRASS 7. disk images on the grassmac site.

The files were downloaded using both Safari (twice) and then Chrome (once) under OS 10.11.6 (El Capitan) w/o success via the Finder.

I then tried running the UNIX clean-up utilities
Then I tried a second reboot

all to no avail.

I was able to mount the disk image using terminal:

$ hdiutil attach -noverify -nomount ./GRASS-7.4.0.dmg
$ diskutil mountDisk /dev/disk2


the newly mounted image was empty. Disk Utility could 'see' the mounted device, and was able to run First Aid, which yielded the following:

'Problems were found with the partition map which might prevent booting'

but couldn't fix the read-only dmg. Everything else, according to Disk First Aid, seemed okay.

I note that these most recent images were not tested under OSXs earlier than Sierra (10.12). Perhaps this [my running El Capitan 10.11] is the problem?

Any suggestions/help [to get GRASS installed] would be greatly appreciated.

Thanks very much, in advance.


didn't try though

hi there,

the 7.4.0 and 7.2.2 .app do not support postgis currently.
It gives:

pg: no such driver available
WARNING: Unable to start driver <pg>
WARNING: Unable open database <v4> by driver <pg>

And v.out.postgis command not available at all.
Seems like it needs to be compiled —with-postgres


Postgresql/postgis support by alex_melnykalex_melnyk, 27 Mar 2018 09:14

I've just posted some fixes and enhancements to the GRASS binaries on this site. It looks like it will not be easy (maybe not possible) to build GRASS with libLAS support for direct LiDAR processing the way I am now compiling binaries. There is hope for the future if the GRASS team adopts PDAL as a replacement for no longer supported libLAS (in the works). In the meantime, I've added LAStools command line tools for LiDAR processing and translation to ASCII formats that GRASS can read. Type lasinfo [return] from the command line to see some of this, with more information at:

Also, I've managed to add a fix to a problem found by Rob Shepard. Attempting to create a new LOCATION from an EPSG code failed. It works now. These should all be available in the fully bundled GRASS binaries on the download page.

You did not explain this issue very clearly. But I think I figured out what you did.

1. You started GRASS and tried to create a new location from EPSG code. You got the error above.

2. Then, instead of trying to create a location a different way, you tried to launch GRASS by opening the and running the ../bin/grass74 file, bypassing the startup scripts.

I might be able to fix #1 and am lookin into it, though I don't understand why this variable is not set by default.

For #2, you can't start GRASS that way. The startup scripts set up the GRASS environment so it can find all the many parts of the program it needs.

page »
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License