I successfully compiled and installed GRASS6.4 with "make -j2 && sudo
checkinstall && sudo ldconfig"
which is usually working perfectly.
But after installing QGIS I can't start GRASS6.4 itself anymore.
I try to launch it from the Terminal like:
x@y:~$ grass64
Cleaning up temporary files ...
Starting GRASS ...
python: can't open file '/usr/lib/grass64/etc/wxpython/gis_set.py':
[Errno 2] No such file or directory
Received EXIT message from GUI.
GRASS is not started. Bye.
it seems that the QGIS installation somehow overwrites some
settings/files that are needed for starting
a pure GRASS session (with GUI).
I am working on Ubuntu 12.04 and QGIS 1.8 is installed via the
instructions from qgis.org:
following lines were added to /etc/apt/sources.list:
deb http://qgis.org/debian precise main
deb-src http://qgis.org/debian precise main
the installation itself was done with:
sudo apt-get update
sudo apt-get install qgis
After uninstalling qgis with "sudo apt-get autoremove qgis" grass64
can be started again without
any problems.
Maybe this is a known issue, but are there any solutions?
On Thu, Aug 23, 2012 at 1:16 PM, Johannes Radinger
<johannesradinger@gmail.com> wrote:
Hi,
I successfully compiled and installed GRASS6.4 with "make -j2 && sudo
checkinstall && sudo ldconfig"
which is usually working perfectly.
But after installing QGIS I can't start GRASS6.4 itself anymore.
I try to launch it from the Terminal like:
x@y:~$ grass64
Cleaning up temporary files ...
Starting GRASS ...
python: can't open file '/usr/lib/grass64/etc/wxpython/gis_set.py':
[Errno 2] No such file or directory
Received EXIT message from GUI.
GRASS is not started. Bye.
it seems that the QGIS installation somehow overwrites some
settings/files that are needed for starting
a pure GRASS session (with GUI).
Please check how many files remained in /usr/lib/grass64/.
Perhaps QGIS removed it to install again GRASS (which failed)?
What if you reinstall again GRASS6.4 with your
"make -j2 && sudo checkinstall && sudo ldconfig"
?
Please check how many files remained in /usr/lib/grass64/.
Perhaps QGIS removed it to install again GRASS (which failed)?
Before installing QGIS (at the time when GRASS is still launching), there is no
grass64 folder in /usr/lib but there is the folder
/usr/local/grass6.4.3SVN. This seems
the location where the command grass64 is probably pointing to.
I am not sure what is the "correct" directory for a selfcompiled GRASS
installation
using checkinstall? And I need to build GRASS myself (different
versions, add ons,
own scripts and add-ons etc.) and the GRASS compilation itself is not
the problem.
After installing QGIS (even from the "ubuntugis-unstable" ppa) the
usr/lib/grass64 is
existing. So the QGIS installation (even without the GRASS plugin)
installs a version
of GRASS64 and this installation seems to change the link of grass64
to the new installation.
So probably just the link for grass64 has to be reset again to my
"real" GRASS6.4?!
I tried to reinstall GRASS GIS after the QGIS installation using
"make -j2 && sudo checkinstall && sudo ldconfig" but the problem still
remains, although
I thought that the ldconfig might solve the problem.
/Johannes
What if you reinstall again GRASS6.4 with your
"make -j2 && sudo checkinstall && sudo ldconfig"
?
Hi!
Just as a suggestion ..
If you are self compiling GRASS - you should probably also self
compile QGIS .. As it seems that QGIS expects some GRASS files in
decent positions you could tell QGIS where to find the GRASS version
you would like to use and compile it ..
Maybe that solves a lot of that problems..
And I hope you don't expect QGIS to work with several versions of
GRASS at the same time (out of the box) - that would not work without
some starting scripts where you set PATHS ..
HTH
kind regards
Werner
On Fri, Aug 24, 2012 at 10:45 AM, Johannes Radinger
<johannesradinger@gmail.com> wrote:
Hi,
Please check how many files remained in /usr/lib/grass64/.
Perhaps QGIS removed it to install again GRASS (which failed)?
Before installing QGIS (at the time when GRASS is still launching), there is no
grass64 folder in /usr/lib but there is the folder
/usr/local/grass6.4.3SVN. This seems
the location where the command grass64 is probably pointing to.
I am not sure what is the "correct" directory for a selfcompiled GRASS
installation
using checkinstall? And I need to build GRASS myself (different
versions, add ons,
own scripts and add-ons etc.) and the GRASS compilation itself is not
the problem.
After installing QGIS (even from the "ubuntugis-unstable" ppa) the
usr/lib/grass64 is
existing. So the QGIS installation (even without the GRASS plugin)
installs a version
of GRASS64 and this installation seems to change the link of grass64
to the new installation.
So probably just the link for grass64 has to be reset again to my
"real" GRASS6.4?!
I tried to reinstall GRASS GIS after the QGIS installation using
"make -j2 && sudo checkinstall && sudo ldconfig" but the problem still
remains, although
I thought that the ldconfig might solve the problem.
/Johannes
What if you reinstall again GRASS6.4 with your
"make -j2 && sudo checkinstall && sudo ldconfig"
?
On Fri, Aug 24, 2012 at 10:51 AM, Werner Macho <werner.macho@gmail.com> wrote:
Hi!
Just as a suggestion ..
If you are self compiling GRASS - you should probably also self
compile QGIS .. As it seems that QGIS expects some GRASS files in
decent positions you could tell QGIS where to find the GRASS version
you would like to use and compile it ..
Maybe that solves a lot of that problems..
And I hope you don't expect QGIS to work with several versions of
GRASS at the same time (out of the box) - that would not work without
some starting scripts where you set PATHS ..
This seems one step forward, I built and installed qgis from source
and before GRASS6.4.3. After removing a package called grass-core
(which probably comes with the QGIS and causes the problems) both
GRASS and QGIS starts. During the QGIS make I set the GRASS prefix
to my original /usr/local/grass6.4.3.
Anyway I couldn't fine anything how to build/install the GRASS-QGIS plugin.
Are there any instructions? Trying to install it via apt-get fails because:
Depends: qgis (= 1.8.0-1~precise1) but 20120824-1 (self-compiled) is
to be installed.
BTW both QGIS and GRASS are installed via checkinstall. I am not
really convinced
if it really needed or if it might cause any problems (with versions
etc)? Would it get
very messy if just "sudo make install" is used? Any recommendations on that?
/johannes
HTH
kind regards
Werner
On Fri, Aug 24, 2012 at 10:45 AM, Johannes Radinger
<johannesradinger@gmail.com> wrote:
Hi,
Please check how many files remained in /usr/lib/grass64/.
Perhaps QGIS removed it to install again GRASS (which failed)?
Before installing QGIS (at the time when GRASS is still launching), there is no
grass64 folder in /usr/lib but there is the folder
/usr/local/grass6.4.3SVN. This seems
the location where the command grass64 is probably pointing to.
I am not sure what is the "correct" directory for a selfcompiled GRASS
installation
using checkinstall? And I need to build GRASS myself (different
versions, add ons,
own scripts and add-ons etc.) and the GRASS compilation itself is not
the problem.
After installing QGIS (even from the "ubuntugis-unstable" ppa) the
usr/lib/grass64 is
existing. So the QGIS installation (even without the GRASS plugin)
installs a version
of GRASS64 and this installation seems to change the link of grass64
to the new installation.
So probably just the link for grass64 has to be reset again to my
"real" GRASS6.4?!
I tried to reinstall GRASS GIS after the QGIS installation using
"make -j2 && sudo checkinstall && sudo ldconfig" but the problem still
remains, although
I thought that the ldconfig might solve the problem.
/Johannes
What if you reinstall again GRASS6.4 with your
"make -j2 && sudo checkinstall && sudo ldconfig"
?
BTW both QGIS and GRASS are installed via checkinstall. I am not
really convinced if it really needed or if it might cause any problems (with
versions etc)? Would it get very messy if just "sudo make install" is used?
Any recommendations on that?
Hi Johannes,
(I am bit late on this but anyway)
uninstalling stuff that have been installed via "make install" (as a superuser
of course) is not easy -- one has to remove them manually! In other words,
one has to to search for (all?) related (qgis) files under several directories,
i.e. ~/.qgis, /usr/local/include/qgis, /usr/local/share/qgis and more.
checkinstall is there to make this process easy. Plus, it creates a .deb file
which might be useful as well.
My knowledge and experiences upon the issue are, of course, limited and maybe
someone else can shed some real light.