Wed 01 Nov 2017 11:46:41 PM UTC, comment #8:
Hi Dmitri,
I have never run Octave with the command line implementation of :
LIBGL_ALWAYS_SOFTWARE=1
If the default is that this command is not run, then yes, fltk always works, but QT implementation has the intermittent plot success/failure.
Thanks and regards,
Shadders.
|
Wed 01 Nov 2017 11:41:57 PM UTC, comment #7:
OK so it is also an octave bug then (hopefultt fixed in
dev version -- there was a significant qt re-write).
Does it work without LIBGL_ALWAYS_SOFTWARE=1?
Dmitri.
|
Wed 01 Nov 2017 11:30:55 PM UTC, comment #6:
Hi Dmitri,
Setting the graphics to fltk plots all graphs, no issues :
system("glxinfo -B")
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0xffffffff)
Device: llvmpipe (LLVM 4.0, 256 bits) (0xffffffff)
Version: 17.2.2
Accelerated: no
Video memory: 7893MB
Unified memory: no
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 4.0, 256 bits)
OpenGL version string: 2.1 Mesa 17.2.2
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 17.2.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
ans = 0
>>
Regards,
Shadders.
|
Wed 01 Nov 2017 11:26:12 PM UTC, comment #5:
Ok, that looks bad. You can try fltk, but most likely you will have to switch to gnuplot backend.
Dmitri.
|
Wed 01 Nov 2017 11:19:10 PM UTC, comment #4:
Hi Dimitri,
Output is as follows :
>> system("glxinfo -B")
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0xffffffff)
Device: llvmpipe (LLVM 4.0, 256 bits) (0xffffffff)
Version: 17.2.2
Accelerated: no
Video memory: 7893MB
Unified memory: no
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 2.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 4.0, 256 bits)
OpenGL version string: 2.1 Mesa 17.2.2
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 17.2.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
ans = 0
>>
Regards,
Shadders.
|
Wed 01 Nov 2017 11:16:01 PM UTC, comment #3:
Could you start octave as
LIBGL_ALWAYS_SOFTWARE=1 octave
(verify that plots still failing) and then do
(at octave prompt):
octave:> system("glxinfo -B")
and post its output?
Dmitri.
|
Wed 01 Nov 2017 11:10:16 PM UTC, comment #2:
Hi,
Output from the command line :
# glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2) (0x1616)
Version: 17.2.2
Accelerated: yes
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 3.0 Mesa 17.2.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.2.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
For both commands regarding LIBGL, the script still fails to plot the curves for some of the plots. That is, as before, there are 10 plots, but some are blank, and this is random in which ones are blank.
Regards,
Shadders.
|
Wed 01 Nov 2017 10:50:49 PM UTC, comment #1:
Most likely problem is a faulty OpenGL driver for your graphics card.
What is the output of
"glxinfo -B"
(this is a shell command not the octave's) ?
Anyway, you can try to launch octave as:
LIBGL_DRI3_DISABLE=1 octave
and see if that helps; a more radical approach is
LIBGL_ALWAYS_SOFTWARE=1 octave
Please try that and post the results.
Dmitri.
--
|
Wed 01 Nov 2017 10:33:11 PM UTC, original submission:
Hi,
I have an installation of Fedora 26 with the standard Octave v4.2.1 build deployed. In setting the graphics backend to qt, then plotting graphics within a loop, it causes some of the graphics to fail to plot.
Command to set graphics backend :
graphics_toolkit ("qt");
Script that causes the failure has been uploaded (loop_graphicsv2.m)
Regards,
Shadders.
|