[Octave-bug-tracker] [bug #44478] test __osmesa_print__.cc-tst crashes on Ubuntu with Nvidia drivers

[José Luis García Pallero]

Follow-up Comment #16, bug #44478 (project octave):

I have also problems with NVIDIA and OpenGL. I use Debian Sid and I have a
NVIDIA Quadro K2100M in my laptop. I use the NVIDIA driver directly from
nvidia.com (not the official Debian package). The principal problem with the
GL NVIDIA libraries is that the FLTK drawing doesn't work. But I can fix this
issue changing several symbolic links in /usr/lib/x86_64-linux-gnu/. I have
installed the packages libgl1-mesa-swx11, libgl1-mesa-swx11-dev, libgles1-mesa
and libgles2-mesa. When I install the NVIDIA driver, the original links to GL
and GLES libraries are changed to point to the NVIDIA libraries and then FLTK
in Octave crash. I use this script in order to restore the links:


#!/bin/bash
cd /usr/lib/x86_64-linux-gnu
rm libGL.so libGL.so.1
rm libGLESv1_CM.so libGLESv1_CM.so.1
rm libGLESv2.so libGLESv2.so.2
ln -s libGL.so.1.6.0 libGL.so.1
ln -s libGL.so.1 libGL.so
ln -s libGLESv1_CM.so.1.1.0 libGLESv1_CM.so.1
ln -s libGLESv1_CM.so.1 libGLESv1_CM.so
ln -s libGLESv2.so.2.0.0 libGLESv2.so.2
ln -s libGLESv2.so.2 libGLESv2.so


Then, the GL and GLES libraries point to the ones installes with
libgl1-mesa-swx11, libgl1-mesa-swx11-dev, libgles1-mesa and libgles2-mesa and
I can use FLTK:


-rw-r--r-- 1 root root 7700082 ene 15 15:02 /usr/lib/x86_64-linux-gnu/libGL.a
lrwxrwxrwx 1 root root      17 mar 10 09:15
/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so -> libGLESv1_CM.so.1
lrwxrwxrwx 1 root root      21 mar 10 09:15
/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1 -> libGLESv1_CM.so.1.1.0
-rw-r--r-- 1 root root   18232 ene 15 15:01
/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0
-rwxr-xr-x 1 root root   51096 feb 27 15:24
/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.346.47
lrwxrwxrwx 1 root root      14 mar 10 09:15
/usr/lib/x86_64-linux-gnu/libGLESv2.so -> libGLESv2.so.2
lrwxrwxrwx 1 root root      18 mar 10 09:15
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2 -> libGLESv2.so.2.0.0
-rw-r--r-- 1 root root   26424 ene 15 15:01
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2.0.0
-rwxr-xr-x 1 root root   75416 feb 27 15:24
/usr/lib/x86_64-linux-gnu/libGLESv2.so.346.47
-rw-r--r-- 1 root root     671 feb 27 15:24
/usr/lib/x86_64-linux-gnu/libGL.la
lrwxrwxrwx 1 root root      10 mar 10 09:15 /usr/lib/x86_64-linux-gnu/libGL.so
-> libGL.so.1
lrwxrwxrwx 1 root root      14 mar 10 09:15
/usr/lib/x86_64-linux-gnu/libGL.so.1 -> libGL.so.1.6.0
-rw-r--r-- 1 root root 4330248 ene 15 15:01
/usr/lib/x86_64-linux-gnu/libGL.so.1.6.0
-rwxr-xr-x 1 root root 1317432 feb 27 15:24
/usr/lib/x86_64-linux-gnu/libGL.so.346.47
-verbatin-

The problem is that each time I upgrade Debian, the GL links point again to
the official NVIDIA GL libraries (although they were installed via the
independent nvidia *.run driver instead from the official Debian packages!),
so I should run my script after each system upgrade

But today I have compiled Octave and I have installed the libosmesa6 and
libosmesa6-dev packages. I think there is not any osmesa libraries in the
NVIDIA driver, but in my Octave make check I obtain the same osmesa_print
crash. The osmesa libraries points always to the same files. They don't change
even where I install the NVIDIA driver


lrwxrwxrwx 1 root root      18 ene 15 15:01
/usr/lib/x86_64-linux-gnu/libOSMesa.so -> libOSMesa.so.8.0.0
lrwxrwxrwx 1 root root      14 ene 15 15:01
/usr/lib/x86_64-linux-gnu/libOSMesa.so.6 -> libOSMesa.so.8
lrwxrwxrwx 1 root root      18 ene 15 15:01
/usr/lib/x86_64-linux-gnu/libOSMesa.so.8 -> libOSMesa.so.8.0.0
-rw-r--r-- 1 root root 3889448 ene 15 15:02
/usr/lib/x86_64-linux-gnu/libOSMesa.so.8.0.0


I don't know if this information could help, but someone in the maintainers
list recommends me to share it here

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44478>

_______________________________________________
  Mensaje enviado vía/por Savannah
  http://savannah.gnu.org/