Prev: Trouble cutting and pasting into an X11 application
Next: Using Mail
From: commiebastard on 15 Jun 2010 09:44
I have an X11 application whose graphical display fails to render to
the screen for some reason.

The error I get is:

Xlib: extension "XFree86-VidModeExtension" missing on display "/tmp/
launch-4gaNW3/org.x:0".
Xlib: extension "RANDR" missing on display "/tmp/launch-4gaNW3/org.x:
0".
Xlib: extension "XFree86-VidModeExtension" missing on display "/tmp/
launch-4gaNW3/org.x:0".

Any idea what this error means at all?
From: JF Mezei on 15 Jun 2010 10:32
commiebastard wrote:
> I have an X11 application whose graphical display fails to render to
> the screen for some reason.
>
> The error I get is:
>
> Xlib: extension "XFree86-VidModeExtension" missing on display "/tmp/
> launch-4gaNW3/org.x:0".
> Xlib: extension "RANDR" missing on display "/tmp/launch-4gaNW3/org.x:
> 0".
> Xlib: extension "XFree86-VidModeExtension" missing on display "/tmp/
> launch-4gaNW3/org.x:0".
>
> Any idea what this error means at all?

X terminals ( X servers in X parlance) come with different flavours.
There is the core X stuff, but there are also extensions which allow an
application to offload work to the X terminal.

For instance, VMS used to have "Display postscript" extension. This
allowed an application to send postscript code to the terminal and have
the terminal rasterize it. Without it, the application would have to
parse/execute the postscript and send the individual drawing commands to
generate the desired output. When Compaq widthdrew support for dispay
postscript, a number of applications broke because they expected display
postscript to be available.

Some extensions are "required" by the application, and some just
generate a complain and the application still works. The RANDR extension
is wanted by Wireshark, but Wireshark still works without it.

TO get the list of extensions on your X display:

xdpyinfo -queryExtensions | more

This is what I get on my laptop:

number of extensions: 24
Apple-DRI (opcode: 128, base event: 64, base error: 128)
Apple-WM (opcode: 129, base event: 68, base error: 130)
BIG-REQUESTS (opcode: 135)
DAMAGE (opcode: 150, base event: 116, base error: 166)
DOUBLE-BUFFER (opcode: 142, base error: 144)
Extended-Visual-Information (opcode: 133)
GLX (opcode: 146, base event: 97, base error: 147)
MIT-SCREEN-SAVER (opcode: 137, base event: 90)
MIT-SHM (opcode: 132, base event: 72, base error: 132)
MIT-SUNDRY-NONSTANDARD (opcode: 136)
RENDER (opcode: 148, base error: 161)
SECURITY (opcode: 144, base event: 96, base error: 145)
SGI-GLX (opcode: 146, base event: 97, base error: 147)
SHAPE (opcode: 131, base event: 71)
SYNC (opcode: 139, base event: 93, base error: 141)
TOG-CUP (opcode: 145)
X-Resource (opcode: 149)
XAccessControlExtension (opcode: 143)
XC-MISC (opcode: 141)
XFIXES (opcode: 147, base event: 114, base error: 160)
XINERAMA (opcode: 130)
XInputExtension (opcode: 134, base event: 73, base error: 133)
XKEYBOARD (opcode: 140, base event: 95, base error: 143)
XVideo (opcode: 138, base event: 91, base error: 138)
From: commiebastard on 15 Jun 2010 12:15
On Jun 15, 10:32 am, JF Mezei <jfmezei.spam...(a)vaxination.ca> wrote:
> commiebastard wrote:
> > I have an X11 application whose graphical display fails to render to
> > the screen for some reason.
>
> > The error I get is:
>
> > Xlib:  extension "XFree86-VidModeExtension" missing on display "/tmp/
> > launch-4gaNW3/org.x:0".
> > Xlib:  extension "RANDR" missing on display "/tmp/launch-4gaNW3/org.x:
> > 0".
> > Xlib:  extension "XFree86-VidModeExtension" missing on display "/tmp/
> > launch-4gaNW3/org.x:0".
>
> > Any idea what this error means at all?
>
> X terminals ( X servers in X parlance) come with different flavours.
> There is the core X stuff, but there are also extensions which allow an
> application to offload work to the X terminal.
>
> For instance, VMS used to have "Display postscript" extension. This
> allowed an application to send postscript code to the terminal and have
> the terminal rasterize it. Without it, the application would have to
> parse/execute the postscript and send the individual drawing commands to
> generate the desired output.  When Compaq widthdrew support for dispay
> postscript, a number of applications broke because they expected display
> postscript to be available.
>
> Some extensions are "required" by the application, and some just
> generate a complain and the application still works. The RANDR extension
>   is wanted by Wireshark, but Wireshark still works without it.
>
> TO get the list of extensions on your X display:
>
>  xdpyinfo -queryExtensions | more
>
> This is what I get on my laptop:
>
> number of extensions:    24
>     Apple-DRI  (opcode: 128, base event: 64, base error: 128)
>     Apple-WM  (opcode: 129, base event: 68, base error: 130)
>     BIG-REQUESTS  (opcode: 135)
>     DAMAGE  (opcode: 150, base event: 116, base error: 166)
>     DOUBLE-BUFFER  (opcode: 142, base error: 144)
>     Extended-Visual-Information  (opcode: 133)
>     GLX  (opcode: 146, base event: 97, base error: 147)
>     MIT-SCREEN-SAVER  (opcode: 137, base event: 90)
>     MIT-SHM  (opcode: 132, base event: 72, base error: 132)
>     MIT-SUNDRY-NONSTANDARD  (opcode: 136)
>     RENDER  (opcode: 148, base error: 161)
>     SECURITY  (opcode: 144, base event: 96, base error: 145)
>     SGI-GLX  (opcode: 146, base event: 97, base error: 147)
>     SHAPE  (opcode: 131, base event: 71)
>     SYNC  (opcode: 139, base event: 93, base error: 141)
>     TOG-CUP  (opcode: 145)
>     X-Resource  (opcode: 149)
>     XAccessControlExtension  (opcode: 143)
>     XC-MISC  (opcode: 141)
>     XFIXES  (opcode: 147, base event: 114, base error: 160)
>     XINERAMA  (opcode: 130)
>     XInputExtension  (opcode: 134, base event: 73, base error: 133)
>     XKEYBOARD  (opcode: 140, base event: 95, base error: 143)
>     XVideo  (opcode: 138, base event: 91, base error: 138)

Here's what I get for mine:

number of extensions: 24
Apple-DRI (opcode: 128, base event: 64, base error: 128)
Apple-WM (opcode: 129, base event: 68, base error: 130)
BIG-REQUESTS (opcode: 135)
DAMAGE (opcode: 150, base event: 116, base error: 166)
DOUBLE-BUFFER (opcode: 142, base error: 144)
Extended-Visual-Information (opcode: 133)
GLX (opcode: 146, base event: 97, base error: 147)
MIT-SCREEN-SAVER (opcode: 137, base event: 90)
MIT-SHM (opcode: 132, base event: 72, base error: 132)
MIT-SUNDRY-NONSTANDARD (opcode: 136)
RENDER (opcode: 148, base error: 161)
SECURITY (opcode: 144, base event: 96, base error: 145)
SGI-GLX (opcode: 146, base event: 97, base error: 147)
SHAPE (opcode: 131, base event: 71)
SYNC (opcode: 139, base event: 93, base error: 141)
TOG-CUP (opcode: 145)
X-Resource (opcode: 149)
XAccessControlExtension (opcode: 143)
XC-MISC (opcode: 141)
XFIXES (opcode: 147, base event: 114, base error: 160)
XINERAMA (opcode: 130)
XInputExtension (opcode: 134, base event: 73, base error: 133)
XKEYBOARD (opcode: 140, base event: 95, base error: 143)
XVideo (opcode: 138, base event: 91, base error: 138)
default screen number: 0
number of screens: 1


Looks identical to yours. Do you get the error I got? If so how do you
fix it?
From: JF Mezei on 15 Jun 2010 15:23
commiebastard wrote:

> Looks identical to yours. Do you get the error I got? If so how do you
> fix it?

I do not know if extensions can easily be added to the X11 software.
I'll have to investigate this. It could be just a matter of dropping a
file in the right location and updating a config file to have that
extension loaded. But I am not sure.
 | 
Pages: 1
Prev: Trouble cutting and pasting into an X11 application
Next: Using Mail