[GRASS-dev] SESSION_MANAGER environment variable not defined

[Moritz Lennert]

Are you using Unity ? GNOME ? KDE ? A session over ssh ?

I'm really no windows management and graphical environment expert, but 
apparently some windows managers do not set this variable.

Moritz

On 13/01/15 13:02, Andy Wickert wrote:
> After the uninstall, I have:
>
> Python 2.7.8
> wxPython 2.8.12.1
>
> 'echo $SESSION_MANAGER' returns nothing both inside and outside the
> GRASS GIS environment in terminal.
>
> ---
> Andrew D. Wickert
> INSTAAR & Geological Sciences, University of Colorado Boulder
> Now at:
> Universität Potsdam
> Institut für Erd- und Umweltwissenschaften
> Haus 29, Rm. 153
> Karl-Liebknecht-Str. 24-25
> 14476 Potsdam-Golm, Deutschland
>
>
> On Tue, Jan 13, 2015 at 11:50 AM, Moritz Lennert
> <mlennert at club.worldonline.be <mailto:mlennert at club.worldonline.be>> wrote:
>
>     On 13/01/15 11:02, Andy Wickert wrote:
>
>         Markus, you're a genius! I just tried starting the version of GRASS
>         available on the apt repositories and got this message:
>
>         awickert at dakib:~$ grass
>         Cleaning up temporary files ...
>         Starting GRASS ...
>         ERROR: wxGUI does not support wxPython 3.0.0.0 yet.
>         Error in GUI startup. If necessary, please
>         report this error to the GRASS developers.
>         Switching to text mode now.
>         Hit RETURN to continue...
>
>         So I think that what you are saying is that wxPython 3 somehow
>         becomes
>         the default / interferes with GRASS. I did:
>
>         awickert at dakib:~$ sudo apt-get remove python-wxgtk3.0
>
>         and now everything works. Well, hopefully my removal of wxPython 3
>         doesn't break something else, so hm, is there a way to ensure
>         that GRASS
>         GIS always looks for wxPython 2?
>
>
>
>     The idea is rather to try to solve any errors concerning wxPython 3
>     as it is more and more becoming the default in Linux distributions.
>     Anna has been quite active in trying to solve any specific wxPython3
>     issues.
>
>     On my Debian Testing system I have Python 2.7.8 and wxPython:
>     3.0.1.1 and I do not see your error. So it would be interesting to
>     explore what happens on your system. What graphical environment are
>     you running in ? What does 'echo $SESSION_MANAGER' in a terminal
>     give you ?
>
>     Moritz
>
>