Re: [Evolution] evolution crashes when using X11 forwarding [SOLVED]

[Hans-Georg Beyer <Hans-Georg Beyer fhv at>]

Hi Pete,

Hurray! Problem solved.

While your export LIBGL_ALWAYS_INDIRECT=1 did not 
solve the problem, googeling LIBGL_ALWAYS_INDIRECT 
guided me to:

https://www.scm.com/doc/Installation/Remote_GUI.html

There is another environment variable:

export LIBGL_ALWAYS_SOFTWARE=1

that does the trick. 

BTW, this works for evolution, it does not work for glxgears  

Many thanks for paving the way to the solution!

Best,

Hans-Georg

Am Donnerstag, den 19.03.2020, 17:31 +0000 schrieb Pete Biggs:
> > > What is your local machine OS and X server? Do things like
> > > glxgears 
> >
> > Ubuntu 18.04 
> >
> > > or
> > > glxinfo run OK?
> >
> > that works flawlessly. However, it also crashes when started 
> > on the remote machine, see e.g.:
> > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> > hgb@HGB-PC2:~$ glxgears 
> > Xlib:  extension "NV-GLX" missing on display "localhost:10.0".
> > X Error of failed request:  BadValue (integer parameter out of
> > range
> > for operation)
>
> Does the remote machine have the proprietary nVidia drivers
> installed?
> I *think* what's happening is that when programs are run on the
> remote
> machine it sees that there are various GL extensions available, tries
> to use them, and fails because they don't exist on the local machine
> where the GL requests are actually performed.
>
> As for fixing it - I think doing 
>
>   export LIBGL_ALWAYS_INDIRECT=1
>
> before running evolution from the command line might help - it
> certainly does for other GLX issues.
>
> P.
>
>
> _______________________________________________
> evolution-list mailing list
> evolution-list gnome org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list