Based on jpsa's findings above I placed a file .drirc in /home/pi with content
That eliminated the "Can't open file" errors in the libGL log.
Additionally calling mathematica as root
Code: Select all
LIBGL_DEBUG=verbose sudo mathematica >m.txt 2>&1
also eliminated the first 2 lines from the log as I now only get in m.txt
Code: Select all
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
but Mathematica still crashes over XRDP.
This is how far I got. But I am clueless how to proceed. Does this mean we have a driver access problem? Which config needs to be in /home/pi/.drirc ?
Edit:
This is not only Mathematica related.
After installing the mesa-utils package with
running the demo
glxgears with
it shows the same behaviour: Running fine when attached to Screen, KB, Mouse; over XRDP crash with the same errors.
When launching with
Code: Select all
LIBGL_DEBUG=verbose glxgears >g.txt 2>&1
I get the following in g.txt
Code: Select all
libGL: OpenDriver: trying /usr/lib/arm-linux-gnueabihf/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/arm-linux-gnueabihf/dri/swrast_dri.so
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":11.0"
after 160 requests (37 known processed) with 0 events remaining.