Eclipse Community Forums: Eclipse Platform » Unable to launch Eclipse on SLES 11 (PPC) from remote X Client

Help

Home

Home » Eclipse Projects » Eclipse Platform » Unable to launch Eclipse on SLES 11 (PPC) from remote X Client

Show: Today's Messages :: Show Polls :: Message Navigator

Unable to launch Eclipse on SLES 11 (PPC) from remote X Client [message #335766]

Tue, 28 April 2009 14:52

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?

Report message to a moderator

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

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?
>

Report message to a moderator

Previous Topic:	New databinding idiom
Next Topic:	Menu labels , mnemonic and key assist view

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 18:04:59 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter