octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: the nvidia/osmesa dilema


From: John W. Eaton
Subject: Re: the nvidia/osmesa dilema
Date: Fri, 6 May 2016 16:21:52 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0

On 05/05/2016 06:16 PM, Daniel J Sebald wrote:

For what it's worth, here's the result I get from that:

sebald@ ~/octave/octave/octave $
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libGL.so
/usr/local/src/octave/octave/build1/run-octave --no-gui --silent
graphics_toolkit ('qt')
figure visible off
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has
not been called
[xcb] Aborting, sorry about that.
octave-gui: ../../src/xcb_io.c:274: poll_for_event: Assertion
`!xcb_xlib_threads_sequence_lost' failed.
panic: Aborted -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
Aborted

Sorry, I made a mistake here. The correct thing is to preload the osmesa library. I think that prevents the function from the nvidia libGL library from being used and avoids the crash, at least for me.

jwe




reply via email to

[Prev in Thread] Current Thread [Next in Thread]