Eclipse does not terminate with activated accessibility utilities and sun-java6

Bug #293849 reported by Carsten Maus on 2008-11-04
This bug affects 4 people
Affects Status Importance Assigned to Milestone
eclipse (Ubuntu)

Bug Description

Binary package hint: eclipse

Eclipse does not terminate if the GNOME accessibility utilities are activated. After closing eclipse the process is still running and can only be killed with "kill -9".

Actually, I'm not sure, if this problem appears with the eclipse package from the Ubuntu repositories because I installed the newest version of eclipse by hand. But as a forums thread on ( reports the same problem with the synaptic version of eclipse I assume it shows the same problem.

Furthermore, this seems to be a quite old problem. I found the solution for me (disabling the GNOME accessibility utilities) in a forums thread from 2006:

My configuration:
Intrepid Ibex with all updates
Eclipse Ganymede 3.4.1
sun-java6 (1.6.0_10)

Maybe someone else can confirm (or refute) the problem with the Ubuntu eclipse package.

dennis (dennis-mercer-gmail) wrote :

I'm having the same issue. Also running Intrepid and also have installed eclipse by hand.

Brinley Ang (brinley) wrote :

Hi I have the exact same issue on 64bit Jaunty with Eclipse Ganymede and openjdk6.
And yup, disabling gnome accessibility fixed it for me as well.
Im wondering if this is related to

Brinley Ang (brinley) wrote :

Forgot to mention that I was installing Eclipse Ganymede from source and Eclipse (older 3.1 version) from the ubuntu repo works fine.

Hi I have the exact same issue on 64bit Jaunty with Eclipse 3.5 M7.
I can not disable gnome accessibility because I'm blind and I need this feature to use ubuntu.

Joachim R. (jro) wrote :

Whatever you installed eclipse from package or by hand, and whatever accessibility is activated or not, eclipse never terminates on hardy 64bits, intrepid 64bits, jaunty 64bits.
Whith sun-java6 and openjdk6, eclipse never terminated normally, I always use kill -9 after workspace save.

Matthias Klose (doko) wrote :

please recheck with eclipse-3.5 from karmic

tags: added: eclipse local-binary
Changed in eclipse (Ubuntu):
status: New → Incomplete
Daniel (hackie) wrote :

same problem here.
Using Eclipse 3.5.1 (manually installed and up-to-date)
Ubuntu Karmic (also up-to-date)
sun-java6-bin 6-16-0ubuntu1.9.04

Uninstalled at-spi yesterday because it did not terminate at shutdown ~"AT SPI Registry Wrapper" not responding.

And now when I read this bug I see that eclipse terminates correctly now.

Interesting: When closing eclipse, it closed all windows correctly, saved files and even removed the workspace lock. Only the process remained in task list with state futex_wait_queue_me.

nh2 (nh2) wrote :

I can confirm this for both running Eclipse in OpenJDK and Sun's Java.
Eclipse 3.5.1, installed manually
Ubuntu Karmic Beta
openjdk-6-jre 6b16-1.6.1-1ubuntu3

I have the same futex_wait_queue_me state as Daniel reported.

Changed in eclipse (Ubuntu):
status: Incomplete → Confirmed
Michael Rennie (michael-rennie) wrote :

I also ran into this problem during our test pass for Eclipse 3.6M3. Some additional infos:

1. confirmed using SUN 1.4.20, 1.5.18 and 1.6.16 VMs
2. Ubuntu Jaunty (9.04), kernel 2.6.28-16-generic

This bug is a dupe of (which should be marked confirmed in my opinion).

I also confirmed that disabling Assistive Tech. or just killing the at_spi_registry process is a workaround for the problem.

Benjamin Drung (bdrung) wrote :

Ok, I mark this bug as duplicate of bug #68714 now. Please update the bug description there.

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

Other bug subscribers

Remote bug watches

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