hi everybody:
                When I run mricrogl I got the error:
Gdk-ERROR **: The program 'MRIcroGL' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 2147 error_code 1 request_code 150 minor_code 168)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Aborted


the system of mine  is rhel6.4
the version of microgl is lx64.zip
I don't know how to solve the problem,Who can help me ?

Is the first part of the message the detailed error with --sync?

No,I just run MricroGL,


compute-0-1 mricrontab]$ ./MRIcroGL

Gdk-ERROR **: The program 'MRIcroGL' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 2147 error_code 1 request_code 150 minor_code 168)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Aborted

When I run it with --sync I still  get the same error:
ompute-0-1 mricrontab]$ ./MRIcroGL --sync

Gdk-ERROR **: The program 'MRIcroGL' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 4350 error_code 1 request_code 150 minor_code 168)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Aborted

Hi! It might have something to do with the graphics card or lack thereof in your system. If you do not have a compatible graphics card, it will not work correctly.