> Karl Dalen wrote:
> > (Details: serial 14 error_code 3 request_code 159
> minor_code 2)
>
> That is an error from an X extension call, but GTK
> has thrown away
> the information about which one, and since the codes
> are dynamically
> assigned based on your server configuration, we can't
> tell from here.
Thanks for your replies.
I just found that indeed this is a generic gtk problem. Any gtk application
I run remotely from nv fails with the same error:
% gtk-demo
The program 'gtk-demo' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 14 error_code 3 request_code 159 minor_code 2)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
:
Notice that running locally works fine and also if I log
in to sparc2 from a Linux machine (running Xorg ver. 7.1.1)
there is no gtk error. Could it be that the newer X server
in nv in some way picks up on something. It did work in Solaris 10.
Also, if I log into the Linux machine gtk works so
obviously it's a problem with gtk-X interface in communication
between Solaris 10 and Nevada.
>
> To debug this further, a developer will also need you
> to run:
> xdpyinfo -queryExt | grep "opcode: 159"
> so that we can know what request code 159 is assigned
> to in your
> server configuration.
% xdpyinfo -queryExt | grep "opcode: 159"
XINERAMA (opcode: 159)
/Karl
This message posted from opensolaris.org
