[desktop-discuss] [tools-discuss] Eclipse fails to start in Solaris 10 8/07

[Carlos Morillo]

Hi Alan,


Do you know the patch number to remove so I can get going without getting
this?
Thanks,


Carlos.


On Feb 8, 2008 2:46 AM, Alan Coopersmith <Alan.Coopersmith at sun.com> wrote:

> Nope - it's a bug in X - the recent security patches broke eclipse.
> (A number of Linux distros got bug reports from their users - yours
>  is the first I've seen from someone who actually runs eclipse on
>  Solaris.)
>
> Revised patches are in progress, if you can't wait for them, you can
> escalate via a support contract.
>
> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6660113
>
>     -Alan Coopersmith-           alan.coopersmith at sun.com
>      Sun Microsystems, Inc. - X Window System Engineering
>
> Carlos Morillo wrote:
> > Hi,
> >
> >
> > On a Sun Blade 2000 running Solaris 10 8/07 with the latest in the
> > greatest patches
> > I am getting the error message when I start the eclipse IDE
> >
> > [auyantepui]</home/morillo>% //auyantepui/eclipse/eclipse
> > The program 'Eclipse' received an X Window System error.
> > This probably reflects a bug in the program.
> > The error was 'BadAlloc (insufficient resources for operation)'.
> >   (Details: serial 375 error_code 11 request_code 131 minor_code 5)
> >   (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.)
> > [auyantepui]</home/morillo>% /auyantepui/eclipse/eclipse --sync
> > The program 'Eclipse' received an X Window System error.
> > This probably reflects a bug in the program.
> > The error was 'BadAlloc (insufficient resources for operation)'.
> >   (Details: serial 676 error_code 11 request_code 131 minor_code 5)
> >   (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.)
> > [auyantepui]</home/morillo>% cat /etc/release
> >                        Solaris 10 8/07 s10s_u4wos_12b SPARC
> >            Copyright 2007 Sun Microsystems, Inc.  All Rights Reserved.
> >                         Use is subject to license terms.
> >                             Assembled 16 August 2007
> > [auyantepui]</home/morillo>%
> >
> > [auyantepui]</home/morillo>% uname -a
> > SunOS auyantepui 5.10 Generic_127111-07 sun4u sparc SUNW,Sun-Blade-1000
> > [auyantepui]</home/morillo>%
> >
> >
> > Any ideas?
> >
> >
> > Is it a proble with Gnome???
> >
> >
> >
> > Thanks in advance,
> >
> >
> > Carlos.
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > tools-discuss mailing list
> > tools-discuss at opensolaris.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.opensolaris.org/pipermail/desktop-discuss/attachments/20080208/8d03e504/attachment.html