FS#35349 - [xorg-server-xephyr] does not have GLX

Attached to Project: Arch Linux
Opened by Star Brilliant (m13253) - Saturday, 18 May 2013, 12:06 GMT
Last edited by Jan de Groot (JGC) - Monday, 01 July 2013, 10:52 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Laurent Carlier (lordheavy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Xephyr does not have GLX

Also affected Ubuntu: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1079096
However it has been resolved for Ubuntu.

Additional info:
xorg-server-xephyr: 1.14.1-1
linux: 3.9.2-1
xf86-video-intel: 2.21.6-1

$ uname -a
Linux brilliant-laptop 3.8.11-1-ARCH #1 SMP PREEMPT Wed May 1 20:18:57 CEST 2013 x86_64 GNU/Linux

$ glxinfo | grep renderer
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 540M] (rev ff)

$ cat /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "sna"
Option "TearFree" "true"
EndSection


Steps to reproduce:
$ Xephyr :2 &
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation

$ DISPLAY=:2 glxinfo
name of display: :2
Error: couldn't find RGB GLX visual or fbconfig
Error: couldn't find RGB GLX visual or fbconfig

This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 01 July 2013, 10:52 GMT
Reason for closing:  Implemented
Additional comments about closing:  Will be in 1.14.2-2.
Comment by Star Brilliant (m13253) - Saturday, 18 May 2013, 12:14 GMT
Append:
There is a patch attached to the bug report on launchpad: https://launchpadlibrarian.net/134196349/xephyr.diff

Maybe it is necessary to apply such a patch.
Comment by Star Brilliant (m13253) - Wednesday, 05 June 2013, 15:26 GMT
I have been waiting for almost one month.
I want to know whether the patch will be accepted.

I consider this problem more as a 'compiling preference' rather than a 'bug', so it is not related to upstream.
That patch just simply enable the GLX extension which is not enabled by default.


I have no idea whether you will accept the patch, however, if you are going to decide to refuse the patch, please read below:
I have looked at the ABS tree and found something similar (autoconfig-nvidia.patch), that is a 'compiling preference', too.
This autoconfig-nvidia.patch, which enables nouveau or vesa driver when needed, is similar to xephyr.diff, which enables GLX extension when needed.

By the way, I have not tested this patch. Please test whether the patch I have Googled out works.
Comment by Laurent Carlier (lordheavy) - Friday, 07 June 2013, 22:49 GMT
Patch sent upstream

Loading...