Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault

[Andreas Beckmann]

On 04/07/2023 11.51, jim_p wrote:
> That lib is part of mesa's libglx0, which brings me to another serious question
> I had forgotten for almost a decade. If the system does not use mesa's libs for
> anything, because it uses nvidia's libs, why must it have them installed?

If GLVND is used (e.g. all nvidia drivers newer than the 340 series), 
libGL.so.1 is no longer the implementation, but just a dispatch library, 
and no more replacement of the system libGL.so.1 is needed.
The actual implementations are in
   libglx-{nvidia,nvidia-legacy*,nvidia-tesla*}0
which can coexist with libglx-mesa0.

Things are much easier after the 340 series ...

Pre-GLVND monolithic GL is only used by a certain proprietary EoL 
driver, thus nobody is considering that any more when building software.
Similarily software that doesn't build with gcc-12 or that requires 
python2 gets kicked out unless someone volunteers to port it to current 
compiler/python interpreter versions (something that cannot happen to 
the sourceless nvidia 340 driver).


Andreas