Eclipse won't start anymore

Bug #184044 reported by Wander
2
Affects Status Importance Assigned to Milestone
eclipse (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: eclipse

When starting eclipse, I get the following error:

wander@wander-laptop:~$ eclipse
searching for compatible vm...
  testing /usr/lib/jvm/java-gcj...not found
  testing /usr/lib/kaffe/pthreads...not found
  testing /usr/lib/jvm/java-6-sun...found
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 604 error_code 11 request_code 148 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.)

I allso get a popup describing that the JVM existed abnormally.

I've allso tried this with the stock eclipse downloaded from www.eclipse.org and I get the same error, so it might not be an error with eclipse itself.

Revision history for this message
Wander (w-winkelhorst) wrote :

I just want to add: This morning eclipse worked OK so it's probably an error that is caused by an update. (Somewhere around 18-01-2008)

My colleague also has the same problem (but uses Gnome instead of KDE and has an older laptop than I do)

Revision history for this message
fnuzbit (fnuzbit) wrote :

I'm getting the same bug. Eclipse was working perfectly this morning, then I did an update and now eclipse throws an almost identical error:

fnuzbit@fnuzbit:~$ /opt/eclipse/eclipse-3.3.1/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 436 error_code 11 request_code 146 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.)

My configuration is:
  gutsy
  eclipse-3.3.1
  java-6-sun

Does anyone know what recent update could be the cause?

Revision history for this message
Markus Korn (thekorn) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 183969, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.