Comment 27 for bug 292973

Revision history for this message
Wayne Wilkinson (wayne-wilkinson) wrote : Re: X apps are receiwing BadAlloc when working over ssh

I have the same results here. I have three revisions of Solaris that I am logging into, 8, 9, and 10. Solaris 8 will display back to a remote X server with no errors. Solaris 10 and 9 had the same error:

Gdk-ERROR **: The program 'gnome-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 230 error_code 11 request_code 136 minor_code 16)
  (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...

Gdk-ERROR **: The program 'gnome_segv' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 349 error_code 11 request_code 136 minor_code 16)
  (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...

After installing the patch on Solaris 10 (119059-45), but Solaris 9 still gets the same error even after the patch (112785-64) is applied.

Wayne