Community
Participate
Working Groups
Created attachment 150673 [details] example launch config that causes the problem I20091027-0100 Steps 1. create a brand new PDE launch configuration 2. set it to run using an EE 3. debug it 4. wait for the target to load, then shut it down 5. notice in the debug view of your host that the target appears to have terminated, but the launch and the process think otherwise. Selecting either of them will give you the option to terminate (the terminate button enables). Selecting the terminate button will eventually produce an error dialog saying "Terminate failed" with no entry in your log. I tested this using Sun 1.4.20, 1.5.18 and 1.6.16. Kernal: 2.6.28-16-generic
I should also note that restarting my host has no effect.
Confirmed in Linux. Marking as critical. Only happens if you shut down Eclipse using the close button or File > Exit. If you shut down the process without letting the workspace close normally everything terminates fine.
Appears to be caused by Ubuntu's user assistance tools, which both Mike and myself had activated to use the Orca screen reader. https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/293849
Confirmed that the assistance tools are required to reproduce. Disabling them (from the System > Preferences > Assistive Technologies dialog) and restarting solves the problem. This bug has existed for some time in the ubuntu database. It has been confirmed, but no suggestions on the root cause. There is a duplicate or at least related bug in Platform IDE - Bug 269586
The at-spi-registry process is to blame (Gnome accessibility technology service provider interface registry). Killing this process will allow eclipse to shut down. Relevant bugs in Gnome: https://bugzilla.gnome.org/show_bug.cgi?id=546542 https://bugzilla.gnome.org/show_bug.cgi?id=405368 It does not appear anyone in Gnome is actively investigating.
