[GRASS-user] Some new issues since installing some Python tools

Hi all!

I have encountered some GRASS (version 7.8.5 on Ubuntu; Python 3.8.5, wxpython 4.1.1) GUI issues since installing some Python tools (anaconda, etc.) a few weeks ago when I took an online Python course. Everything went well during the course. However, while recently getting back to some GRASS work, I have had these problems using the GRASS GUI:

(1) exporting a map image (any resolution) never completes
(2) saving a new GRASS region, after zooming in, e.g., does nothing and I get no errors
(3) saving a new region from the command line does work

I’m sure I could find other issues. None of these were problems prior to installing the Python tools, so I’m pretty sure that’s where my issue lies. I did build my installation from source and since I started seeing these problems I have re-built from source (twice) after make clean and running configure with options – to no avail. GRASS configures and compiles just fine, without errors.

Could the problem exist due to incompatible installations of gdal or another library? Any suggestions?

Regards,
Tom

Recompiling GRASS will not help. Look at your environment settings. In
terminal examine output of env – most likely it contains some extra
python paths that should not be there.

Usual suspects of not playing nice are any python modules directly
(ctypes, SWIG, ...) utilizing code from external compiled libraries
(GDAL, wxWidgets, PROJ, ...). Make sure you are using only one python
and its modules linking to other shared libraries are compiled with
the same version of shared library. On Ubuntu package manager takes
care of those aspects, in a virtual or mixed environment you are on
your own.

Good luck,
Māris.

Thank you, Māris! I’ll look into these…

Best regards,
Tom

On Fri, Apr 16, 2021 at 2:00 AM Maris Nartiss <maris.gis@gmail.com> wrote:

Recompiling GRASS will not help. Look at your environment settings. In
terminal examine output of env – most likely it contains some extra
python paths that should not be there.

Usual suspects of not playing nice are any python modules directly
(ctypes, SWIG, …) utilizing code from external compiled libraries
(GDAL, wxWidgets, PROJ, …). Make sure you are using only one python
and its modules linking to other shared libraries are compiled with
the same version of shared library. On Ubuntu package manager takes
care of those aspects, in a virtual or mixed environment you are on
your own.

Good luck,
Māris.

Hi Māris!

I found the issue – life is good again! Thank you so much!

Best regards,
Tom

On Fri, Apr 16, 2021 at 2:00 AM Maris Nartiss <maris.gis@gmail.com> wrote:

Recompiling GRASS will not help. Look at your environment settings. In
terminal examine output of env – most likely it contains some extra
python paths that should not be there.

Usual suspects of not playing nice are any python modules directly
(ctypes, SWIG, …) utilizing code from external compiled libraries
(GDAL, wxWidgets, PROJ, …). Make sure you are using only one python
and its modules linking to other shared libraries are compiled with
the same version of shared library. On Ubuntu package manager takes
care of those aspects, in a virtual or mixed environment you are on
your own.

Good luck,
Māris.

Hello Tom,
please in a few words describe the issue and the solution you found.
This will help others facing same error message to find solution by
simple googling.

Good to hear that you are back on a horse,
Māris.

2021-04-16 13:57 GMT+03:00, Thomas Adams <tea3rd@gmail.com>:

Hi Māris!

I found the issue -- life is good again! Thank you so much!

Best regards,
Tom

On Fri, Apr 16, 2021 at 2:00 AM Maris Nartiss <maris.gis@gmail.com> wrote:

Recompiling GRASS will not help. Look at your environment settings. In
terminal examine output of env – most likely it contains some extra
python paths that should not be there.

Usual suspects of not playing nice are any python modules directly
(ctypes, SWIG, ...) utilizing code from external compiled libraries
(GDAL, wxWidgets, PROJ, ...). Make sure you are using only one python
and its modules linking to other shared libraries are compiled with
the same version of shared library. On Ubuntu package manager takes
care of those aspects, in a virtual or mixed environment you are on
your own.

Good luck,
Māris.

Hello Māris,

Yes here is what I found: my installation to anaconda3 was referenced twice in my PATH…

This is what I have, now, that works:

echo $PATH
/home/teaiii/anaconda3/condabin:/home/teaiii/.cargo/bin:/home/teaiii/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

Previously, I was also referencing anaconda3 following “:/usr/local/bin:” – once I removed the reference in my .profile and logged out and back in again, my problem was resolved. Again, I am using GRASS (version 7.8.5 on Ubuntu; Python 3.8.5, wxpython 4.1.1)

Thanks again and best wishes…

Tom

On Mon, Apr 19, 2021 at 1:48 AM Maris Nartiss <maris.gis@gmail.com> wrote:

Hello Tom,
please in a few words describe the issue and the solution you found.
This will help others facing same error message to find solution by
simple googling.

Good to hear that you are back on a horse,
Māris.

2021-04-16 13:57 GMT+03:00, Thomas Adams <tea3rd@gmail.com>:

Hi Māris!

I found the issue – life is good again! Thank you so much!

Best regards,
Tom

On Fri, Apr 16, 2021 at 2:00 AM Maris Nartiss <maris.gis@gmail.com> wrote:

Recompiling GRASS will not help. Look at your environment settings. In
terminal examine output of env – most likely it contains some extra
python paths that should not be there.

Usual suspects of not playing nice are any python modules directly
(ctypes, SWIG, …) utilizing code from external compiled libraries
(GDAL, wxWidgets, PROJ, …). Make sure you are using only one python
and its modules linking to other shared libraries are compiled with
the same version of shared library. On Ubuntu package manager takes
care of those aspects, in a virtual or mixed environment you are on
your own.

Good luck,
Māris.