GLX/EGL X11 clients of Xmir get software rendered (LLVMpipe)

Bug #1496300 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

GLX clients of Xmir get software rendered (LLVMpipe). No idea why...

$ glxinfo | grep OpenGL
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.6, 256 bits)
OpenGL version string: 3.0 Mesa 10.6.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:

$ glmark2
** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
** Failed to set swap interval. Results may be bounded above by refresh rate.
=======================================================
    glmark2 2014.03+git20150611.fa71af2d
=======================================================
    OpenGL Information
    GL_VENDOR: VMware, Inc.
    GL_RENDERER: Gallium 0.4 on llvmpipe (LLVM 3.6, 256 bits)
    GL_VERSION: 3.0 Mesa 10.6.3
=======================================================

Still, LLVMpipe rocks and things are generally smooth.

WORKAROUND:
$ sudo chown $USER /dev/dri/*

Tags: xmir
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Found the problem. It's just the GLX/EGL clients don't have correct permissions configured to access /dev/dri/*

If you run your GLX apps with sudo, it works and you get full hardware acceleration.

summary: - GLX clients of Xmir get software rendered (LLVMpipe)
+ GLX/EGL X11 clients of Xmir get software rendered (LLVMpipe)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Slightly better:

$ sudo glxinfo | grep OpenGL
Failed to open BO for returned DRI2 buffer (100x100, dri2 fake front buffer, named -1).
This is likely a bug in the X Server that will lead to a crash soon.
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Desktop
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.3
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
Failed to open BO for returned DRI2 buffer (100x100, dri2 fake front buffer, named -1).
This is likely a bug in the X Server that will lead to a crash soon.
OpenGL version string: 3.0 Mesa 10.6.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
Failed to open BO for returned DRI2 buffer (100x100, dri2 fake front buffer, named -1).
This is likely a bug in the X Server that will lead to a crash soon.
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.6.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Correct permissions on /dev/dri to solve this bug are set up as part of the Ubuntu login process. And I've just verified Unity8 does it too.

So there's nothing to fix.

Changed in xorg-server (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.