Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » Unable to launch Eclipse on SLES 11 (PPC) from remote X Client
Unable to launch Eclipse on SLES 11 (PPC) from remote X Client [message #335766] Tue, 28 April 2009 14:52 Go to next message
Patrick Tiu is currently offline Patrick Tiu
Messages: 3
Registered: July 2009
Junior Member
When I run eclipse 341 on SLES 11 (PPC) from a remote X Client on RHEL 4.6
(x86), I have a X Window System error:

The program 'eclipse' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 13 error_code 2 request_code 156 minor_code 4)
(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.)

All other X applications (e.g. xclock and Java console GUI) start
successfully from the X client.

If running Eclipse locally or through vnc from remote machine or from
remote
X Client on SLES machines, it runs successfully.

Has anyone seen this problem?
Re: Unable to launch Eclipse on SLES 11 (PPC) from remote X Client [message #335796 is a reply to message #335766] Thu, 30 April 2009 00:13 Go to previous message
Ben Vitale is currently offline Ben Vitale
Messages: 247
Registered: July 2009
Senior Member
You may try posting this to the eclipse.platform.swt group. SWT is
responsible for dealing with the windowing system.

Regards,
Ben

Patrick Tiu wrote:
> When I run eclipse 341 on SLES 11 (PPC) from a remote X Client on RHEL
> 4.6 (x86), I have a X Window System error:
> The program 'eclipse' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadValue (integer parameter out of range for operation)'.
> (Details: serial 13 error_code 2 request_code 156 minor_code 4)
> (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.)
>
> All other X applications (e.g. xclock and Java console GUI) start
> successfully from the X client.
>
> If running Eclipse locally or through vnc from remote machine or from
> remote X Client on SLES machines, it runs successfully.
>
> Has anyone seen this problem?
>
Previous Topic:New databinding idiom
Next Topic:Menu labels , mnemonic and key assist view
Goto Forum:
  


Current Time: Thu Oct 23 03:04:00 GMT 2014

Powered by FUDForum. Page generated in 0.01695 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software