GLX extension not working properly with xvfb
up vote
15
down vote
favorite
I have an Ubuntu 14.04 system with the following packages installed:
libegl1-mesa:amd64
libegl1-mesa-drivers:amd64
libgl1-mesa-dri:amd64
libgl1-mesa-dri:i386
libgl1-mesa-glx:amd64
libgl1-mesa-glx:i386
libglapi-mesa:amd64
libglapi-mesa:i386
libgles2-mesa:amd64
libglu1-mesa:amd64
libopenvg1-mesa:amd64
libwayland-egl1-mesa:amd64
mesa-utils
xvfb
I want to start an application under xvfb. I first start xvfb with:
$ Xvfb :1 -screen 0 1024x768x24 +extension GLX +render -noreset >> xsession.log 2>&1 &
and then check the xvfb log file:
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 Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension GLX
which shows no errors. Also, it seems that GLX has been loaded properly.
Now, if I check the server with
$ glxinfo -display :1
I get
name of display: :1
Xlib: extension "GLX" missing on display ":1".
...
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":1".
...
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":1".
...
In fact, the application that I want to start on this server and that needs GLX won't start.
After checking several documentation pages and forums, I have no clue as to what is going wrong here. Why does the X server log file not show any errors if the GLX extension was not loaded correctly? Is there something I should check?
x11 opengl xvfb
asked Jun 17 '14 at 9:45
Giorgio
3751523
add a comment |
up vote
15
down vote
favorite
I have an Ubuntu 14.04 system with the following packages installed:
libegl1-mesa:amd64
libegl1-mesa-drivers:amd64
libgl1-mesa-dri:amd64
libgl1-mesa-dri:i386
libgl1-mesa-glx:amd64
libgl1-mesa-glx:i386
libglapi-mesa:amd64
libglapi-mesa:i386
libgles2-mesa:amd64
libglu1-mesa:amd64
libopenvg1-mesa:amd64
libwayland-egl1-mesa:amd64
mesa-utils
xvfb
I want to start an application under xvfb. I first start xvfb with:
$ Xvfb :1 -screen 0 1024x768x24 +extension GLX +render -noreset >> xsession.log 2>&1 &
and then check the xvfb log file:
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 Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension GLX
which shows no errors. Also, it seems that GLX has been loaded properly.
Now, if I check the server with
$ glxinfo -display :1
I get
name of display: :1
Xlib: extension "GLX" missing on display ":1".
...
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":1".
...
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":1".
...
In fact, the application that I want to start on this server and that needs GLX won't start.
After checking several documentation pages and forums, I have no clue as to what is going wrong here. Why does the X server log file not show any errors if the GLX extension was not loaded correctly? Is there something I should check?
x11 opengl xvfb
asked Jun 17 '14 at 9:45
Giorgio
3751523
In wiki page[1] of Xvfb it says:" Unlike a real display server, Xvfb does not support modern X11 extensions like compositing, Randr or GLX. Xdummy is a newer alternative which supports these extensions as well as providing the same functionality as Xvfb." [1]en.wikipedia.org/wiki/Xvfb
– alpert
Oct 31 '14 at 13:07
@alpertek you should post that as an answer. GLX generally needs a chip-specific driver to be useful.
– XTL
Apr 27 '15 at 14:21
3
the above comments are not correct. we used GLX on Xvfb for several years in OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851
– don bright
Sep 6 '15 at 3:09
Well that comment in wiki was removed in the meantime. en.wikipedia.org/w/…
– Vladimír Čunát
May 4 '16 at 10:59
add a comment |
up vote
15
down vote
favorite
up vote
15
down vote
favorite
I have an Ubuntu 14.04 system with the following packages installed:
libegl1-mesa:amd64
libegl1-mesa-drivers:amd64
libgl1-mesa-dri:amd64
libgl1-mesa-dri:i386
libgl1-mesa-glx:amd64
libgl1-mesa-glx:i386
libglapi-mesa:amd64
libglapi-mesa:i386
libgles2-mesa:amd64
libglu1-mesa:amd64
libopenvg1-mesa:amd64
libwayland-egl1-mesa:amd64
mesa-utils
xvfb
I want to start an application under xvfb. I first start xvfb with:
$ Xvfb :1 -screen 0 1024x768x24 +extension GLX +render -noreset >> xsession.log 2>&1 &
and then check the xvfb log file:
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 Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension GLX
which shows no errors. Also, it seems that GLX has been loaded properly.
Now, if I check the server with
$ glxinfo -display :1
I get
name of display: :1
Xlib: extension "GLX" missing on display ":1".
...
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":1".
...
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":1".
...
In fact, the application that I want to start on this server and that needs GLX won't start.
After checking several documentation pages and forums, I have no clue as to what is going wrong here. Why does the X server log file not show any errors if the GLX extension was not loaded correctly? Is there something I should check?
x11 opengl xvfb
asked Jun 17 '14 at 9:45
Giorgio
3751523
I have an Ubuntu 14.04 system with the following packages installed:
libegl1-mesa:amd64
libegl1-mesa-drivers:amd64
libgl1-mesa-dri:amd64
libgl1-mesa-dri:i386
libgl1-mesa-glx:amd64
libgl1-mesa-glx:i386
libglapi-mesa:amd64
libglapi-mesa:i386
libgles2-mesa:amd64
libglu1-mesa:amd64
libopenvg1-mesa:amd64
libwayland-egl1-mesa:amd64
mesa-utils
xvfb
I want to start an application under xvfb. I first start xvfb with:
$ Xvfb :1 -screen 0 1024x768x24 +extension GLX +render -noreset >> xsession.log 2>&1 &
and then check the xvfb log file:
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 Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension GLX
which shows no errors. Also, it seems that GLX has been loaded properly.
Now, if I check the server with
$ glxinfo -display :1
I get
name of display: :1
Xlib: extension "GLX" missing on display ":1".
...
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":1".
...
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":1".
...
In fact, the application that I want to start on this server and that needs GLX won't start.
After checking several documentation pages and forums, I have no clue as to what is going wrong here. Why does the X server log file not show any errors if the GLX extension was not loaded correctly? Is there something I should check?
x11 opengl xvfb
x11 opengl xvfb
asked Jun 17 '14 at 9:45
Giorgio
3751523
asked Jun 17 '14 at 9:45
Giorgio
3751523
asked Jun 17 '14 at 9:45
Giorgio
3751523
asked Jun 17 '14 at 9:45
Giorgio
3751523
asked Jun 17 '14 at 9:45
Giorgio
3751523
3751523
In wiki page[1] of Xvfb it says:" Unlike a real display server, Xvfb does not support modern X11 extensions like compositing, Randr or GLX. Xdummy is a newer alternative which supports these extensions as well as providing the same functionality as Xvfb." [1]en.wikipedia.org/wiki/Xvfb
– alpert
Oct 31 '14 at 13:07
@alpertek you should post that as an answer. GLX generally needs a chip-specific driver to be useful.
– XTL
Apr 27 '15 at 14:21
3
the above comments are not correct. we used GLX on Xvfb for several years in OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851
– don bright
Sep 6 '15 at 3:09
Well that comment in wiki was removed in the meantime. en.wikipedia.org/w/…
– Vladimír Čunát
May 4 '16 at 10:59
add a comment |
In wiki page[1] of Xvfb it says:" Unlike a real display server, Xvfb does not support modern X11 extensions like compositing, Randr or GLX. Xdummy is a newer alternative which supports these extensions as well as providing the same functionality as Xvfb." [1]en.wikipedia.org/wiki/Xvfb
– alpert
Oct 31 '14 at 13:07
@alpertek you should post that as an answer. GLX generally needs a chip-specific driver to be useful.
– XTL
Apr 27 '15 at 14:21
3
the above comments are not correct. we used GLX on Xvfb for several years in OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851
– don bright
Sep 6 '15 at 3:09
Well that comment in wiki was removed in the meantime. en.wikipedia.org/w/…
– Vladimír Čunát
May 4 '16 at 10:59
In wiki page[1] of Xvfb it says:" Unlike a real display server, Xvfb does not support modern X11 extensions like compositing, Randr or GLX. Xdummy is a newer alternative which supports these extensions as well as providing the same functionality as Xvfb." [1]en.wikipedia.org/wiki/Xvfb
– alpert
Oct 31 '14 at 13:07
In wiki page[1] of Xvfb it says:" Unlike a real display server, Xvfb does not support modern X11 extensions like compositing, Randr or GLX. Xdummy is a newer alternative which supports these extensions as well as providing the same functionality as Xvfb." [1]en.wikipedia.org/wiki/Xvfb
– alpert
Oct 31 '14 at 13:07
@alpertek you should post that as an answer. GLX generally needs a chip-specific driver to be useful.
– XTL
Apr 27 '15 at 14:21
@alpertek you should post that as an answer. GLX generally needs a chip-specific driver to be useful.
– XTL
Apr 27 '15 at 14:21
3
3
the above comments are not correct. we used GLX on Xvfb for several years in OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851
– don bright
Sep 6 '15 at 3:09
the above comments are not correct. we used GLX on Xvfb for several years in OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851
– don bright
Sep 6 '15 at 3:09
Well that comment in wiki was removed in the meantime. en.wikipedia.org/w/…
– Vladimír Čunát
May 4 '16 at 10:59
Well that comment in wiki was removed in the meantime. en.wikipedia.org/w/…
– Vladimír Čunát
May 4 '16 at 10:59
add a comment |
3 Answers
3
active
oldest
votes
up vote
0
down vote
in my log files i see everything is okay up to Initializing built-in extension GLX
but then it is followed by
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86AudioMicMute
Errors from xkbcomp are not fatal to the X server
may be the key issue is with xkbcomp?
answered Oct 31 '14 at 13:01
Ilya Yevlampiev
1011
add a comment |
up vote
0
down vote
In wiki page of Xvfb it says:" Unlike a real display server, Xvfb does not support modern X11 extensions like compositing, Randr or GLX. Xdummy is a newer alternative which supports these extensions as well as providing the same functionality as Xvfb."
answered Apr 28 '15 at 10:46
alpert
45038
For more information, useXdummy -h(there is no manpage as of x11vnc 0.9.13-6 on Arch Linux).
– Lekensteyn
Aug 2 '15 at 14:29
4
this answer is not correct. we used GLX on Xvfb for several years in linux for headless OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851 the wiki has since been updated and that line removed.
– don bright
Sep 6 '15 at 3:09
add a comment |
up vote
0
down vote
Xvfb (X virtual Frame buffer) is a Xsever virtual do not support real hardware acceleration.
You need spawn openGL calls, with virtualGL, fork the real calls via a real 3D Xserver and 2d rendering to Xvfb or another 2D Xserver.
$ Xvfb :1 -screen 0 1024x768x24 +extension GLX +render -noreset >> xsession.log 2>&1 &
$ env DISPLAY=:1 vglrun glxinfo
edited Sep 12 at 9:59
RobotJohnny
719216
answered Sep 12 at 9:53
4l3x
11
While it doesn't support real hardware acceleration, it supports Mesa (software GLX) just fine - I checked some time ago (still in 2018). So you don't need to use a real 3D Xserver, though it's of course an option.
– dirkt
Sep 12 at 11:08
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
in my log files i see everything is okay up to Initializing built-in extension GLX
but then it is followed by
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86AudioMicMute
Errors from xkbcomp are not fatal to the X server
may be the key issue is with xkbcomp?
answered Oct 31 '14 at 13:01
Ilya Yevlampiev
1011
add a comment |
up vote
0
down vote
in my log files i see everything is okay up to Initializing built-in extension GLX
but then it is followed by
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86AudioMicMute
Errors from xkbcomp are not fatal to the X server
may be the key issue is with xkbcomp?
answered Oct 31 '14 at 13:01
Ilya Yevlampiev
1011
add a comment |
up vote
0
down vote
up vote
0
down vote
in my log files i see everything is okay up to Initializing built-in extension GLX
but then it is followed by
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86AudioMicMute
Errors from xkbcomp are not fatal to the X server
may be the key issue is with xkbcomp?
answered Oct 31 '14 at 13:01
Ilya Yevlampiev
1011
in my log files i see everything is okay up to Initializing built-in extension GLX
but then it is followed by
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86AudioMicMute
Errors from xkbcomp are not fatal to the X server
may be the key issue is with xkbcomp?
answered Oct 31 '14 at 13:01
Ilya Yevlampiev
1011
answered Oct 31 '14 at 13:01
Ilya Yevlampiev
1011
answered Oct 31 '14 at 13:01
Ilya Yevlampiev
1011
answered Oct 31 '14 at 13:01
Ilya Yevlampiev
1011
1011
add a comment |
add a comment |
up vote
0
down vote
In wiki page of Xvfb it says:" Unlike a real display server, Xvfb does not support modern X11 extensions like compositing, Randr or GLX. Xdummy is a newer alternative which supports these extensions as well as providing the same functionality as Xvfb."
answered Apr 28 '15 at 10:46
alpert
45038
For more information, useXdummy -h(there is no manpage as of x11vnc 0.9.13-6 on Arch Linux).
– Lekensteyn
Aug 2 '15 at 14:29
4
this answer is not correct. we used GLX on Xvfb for several years in linux for headless OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851 the wiki has since been updated and that line removed.
– don bright
Sep 6 '15 at 3:09
add a comment |
up vote
0
down vote
In wiki page of Xvfb it says:" Unlike a real display server, Xvfb does not support modern X11 extensions like compositing, Randr or GLX. Xdummy is a newer alternative which supports these extensions as well as providing the same functionality as Xvfb."
answered Apr 28 '15 at 10:46
alpert
45038
For more information, useXdummy -h(there is no manpage as of x11vnc 0.9.13-6 on Arch Linux).
– Lekensteyn
Aug 2 '15 at 14:29
4
this answer is not correct. we used GLX on Xvfb for several years in linux for headless OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851 the wiki has since been updated and that line removed.
– don bright
Sep 6 '15 at 3:09
add a comment |
up vote
0
down vote
up vote
0
down vote
In wiki page of Xvfb it says:" Unlike a real display server, Xvfb does not support modern X11 extensions like compositing, Randr or GLX. Xdummy is a newer alternative which supports these extensions as well as providing the same functionality as Xvfb."
answered Apr 28 '15 at 10:46
alpert
45038
In wiki page of Xvfb it says:" Unlike a real display server, Xvfb does not support modern X11 extensions like compositing, Randr or GLX. Xdummy is a newer alternative which supports these extensions as well as providing the same functionality as Xvfb."
answered Apr 28 '15 at 10:46
alpert
45038
answered Apr 28 '15 at 10:46
alpert
45038
answered Apr 28 '15 at 10:46
alpert
45038
answered Apr 28 '15 at 10:46
alpert
45038
45038
For more information, useXdummy -h(there is no manpage as of x11vnc 0.9.13-6 on Arch Linux).
– Lekensteyn
Aug 2 '15 at 14:29
4
this answer is not correct. we used GLX on Xvfb for several years in linux for headless OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851 the wiki has since been updated and that line removed.
– don bright
Sep 6 '15 at 3:09
add a comment |
For more information, useXdummy -h(there is no manpage as of x11vnc 0.9.13-6 on Arch Linux).
– Lekensteyn
Aug 2 '15 at 14:29
4
this answer is not correct. we used GLX on Xvfb for several years in linux for headless OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851 the wiki has since been updated and that line removed.
– don bright
Sep 6 '15 at 3:09
For more information, use
Xdummy -h (there is no manpage as of x11vnc 0.9.13-6 on Arch Linux).– Lekensteyn
Aug 2 '15 at 14:29
For more information, use
Xdummy -h (there is no manpage as of x11vnc 0.9.13-6 on Arch Linux).– Lekensteyn
Aug 2 '15 at 14:29
4
4
this answer is not correct. we used GLX on Xvfb for several years in linux for headless OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851 the wiki has since been updated and that line removed.
– don bright
Sep 6 '15 at 3:09
this answer is not correct. we used GLX on Xvfb for several years in linux for headless OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851 the wiki has since been updated and that line removed.
– don bright
Sep 6 '15 at 3:09
add a comment |
up vote
0
down vote
Xvfb (X virtual Frame buffer) is a Xsever virtual do not support real hardware acceleration.
You need spawn openGL calls, with virtualGL, fork the real calls via a real 3D Xserver and 2d rendering to Xvfb or another 2D Xserver.
$ Xvfb :1 -screen 0 1024x768x24 +extension GLX +render -noreset >> xsession.log 2>&1 &
$ env DISPLAY=:1 vglrun glxinfo
edited Sep 12 at 9:59
RobotJohnny
719216
answered Sep 12 at 9:53
4l3x
11
While it doesn't support real hardware acceleration, it supports Mesa (software GLX) just fine - I checked some time ago (still in 2018). So you don't need to use a real 3D Xserver, though it's of course an option.
– dirkt
Sep 12 at 11:08
add a comment |
up vote
0
down vote
Xvfb (X virtual Frame buffer) is a Xsever virtual do not support real hardware acceleration.
You need spawn openGL calls, with virtualGL, fork the real calls via a real 3D Xserver and 2d rendering to Xvfb or another 2D Xserver.
$ Xvfb :1 -screen 0 1024x768x24 +extension GLX +render -noreset >> xsession.log 2>&1 &
$ env DISPLAY=:1 vglrun glxinfo
edited Sep 12 at 9:59
RobotJohnny
719216
answered Sep 12 at 9:53
4l3x
11
While it doesn't support real hardware acceleration, it supports Mesa (software GLX) just fine - I checked some time ago (still in 2018). So you don't need to use a real 3D Xserver, though it's of course an option.
– dirkt
Sep 12 at 11:08
add a comment |
up vote
0
down vote
up vote
0
down vote
Xvfb (X virtual Frame buffer) is a Xsever virtual do not support real hardware acceleration.
You need spawn openGL calls, with virtualGL, fork the real calls via a real 3D Xserver and 2d rendering to Xvfb or another 2D Xserver.
$ Xvfb :1 -screen 0 1024x768x24 +extension GLX +render -noreset >> xsession.log 2>&1 &
$ env DISPLAY=:1 vglrun glxinfo
edited Sep 12 at 9:59
RobotJohnny
719216
answered Sep 12 at 9:53
4l3x
11
Xvfb (X virtual Frame buffer) is a Xsever virtual do not support real hardware acceleration.
You need spawn openGL calls, with virtualGL, fork the real calls via a real 3D Xserver and 2d rendering to Xvfb or another 2D Xserver.
$ Xvfb :1 -screen 0 1024x768x24 +extension GLX +render -noreset >> xsession.log 2>&1 &
$ env DISPLAY=:1 vglrun glxinfo
edited Sep 12 at 9:59
RobotJohnny
719216
answered Sep 12 at 9:53
4l3x
11
edited Sep 12 at 9:59
RobotJohnny
719216
edited Sep 12 at 9:59
RobotJohnny
719216
edited Sep 12 at 9:59
RobotJohnny
719216
719216
answered Sep 12 at 9:53
4l3x
11
answered Sep 12 at 9:53
4l3x
11
answered Sep 12 at 9:53
4l3x
11
11
While it doesn't support real hardware acceleration, it supports Mesa (software GLX) just fine - I checked some time ago (still in 2018). So you don't need to use a real 3D Xserver, though it's of course an option.
– dirkt
Sep 12 at 11:08
add a comment |
While it doesn't support real hardware acceleration, it supports Mesa (software GLX) just fine - I checked some time ago (still in 2018). So you don't need to use a real 3D Xserver, though it's of course an option.
– dirkt
Sep 12 at 11:08
While it doesn't support real hardware acceleration, it supports Mesa (software GLX) just fine - I checked some time ago (still in 2018). So you don't need to use a real 3D Xserver, though it's of course an option.
– dirkt
Sep 12 at 11:08
While it doesn't support real hardware acceleration, it supports Mesa (software GLX) just fine - I checked some time ago (still in 2018). So you don't need to use a real 3D Xserver, though it's of course an option.
– dirkt
Sep 12 at 11:08
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f137567%2fglx-extension-not-working-properly-with-xvfb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
In wiki page[1] of Xvfb it says:" Unlike a real display server, Xvfb does not support modern X11 extensions like compositing, Randr or GLX. Xdummy is a newer alternative which supports these extensions as well as providing the same functionality as Xvfb." [1]en.wikipedia.org/wiki/Xvfb
– alpert
Oct 31 '14 at 13:07
@alpertek you should post that as an answer. GLX generally needs a chip-specific driver to be useful.
– XTL
Apr 27 '15 at 14:21
3
the above comments are not correct. we used GLX on Xvfb for several years in OpenSCAD test suite. bugzilla.redhat.com/show_bug.cgi?id=904851
– don bright
Sep 6 '15 at 3:09
Well that comment in wiki was removed in the meantime. en.wikipedia.org/w/…
– Vladimír Čunát
May 4 '16 at 10:59