On Tue, Oct 03, 2017 at 13:16:11 -0700, Mike Miller wrote: > Octave team may want to discuss whether Octave should be built with > "--without-osmesa" until a proper solution can be found upstream. > Because it's basically a useless feature in Octave now without the > LD_PRELOAD hack. Should we add "--without-OSMesa" to Octave? The current situation in unstable is it is completely useless for all users with mesa >= 17.2 unless they run Octave with "LD_PRELOAD=libGLX_mesa.so.0". It has previously been known to be broken in this way for users with Nvidia hardware and proprietary drivers. This now applies to all Mesa users. Background: we have been told before by Mesa upstream that having a single executable attempt to use both Mesa libGL and OSMesa is not supported. Octave has been doing this anyway and mostly getting away with it. But something about the new libglvnd dispatch scheme seems to have broken this. A proper upstream solution will probably involve isolating OSMesa in a separate executable that Octave can send data to via IPC for rendering. Other ideas for fixing this situation are very welcome. -- mike
Attachment:
signature.asc
Description: PGP signature