I've just confirmed that this problem still exists in my JJ AMD64 system. After removing at-spi and rebooting, for the first time in months, Eclipse fully shut down the Sun JVM without me having to do a manual kill -9. I've been running Eclipse Galileo 3.5, and just upgraded to 3.5.1. This happened in both versions.
My present system information:
/usr/bin/java -version
java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
uname -a
Linux krumm 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:48:52 UTC 2009 x86_64 GNU/Linux
I've just confirmed that this problem still exists in my JJ AMD64 system. After removing at-spi and rebooting, for the first time in months, Eclipse fully shut down the Sun JVM without me having to do a manual kill -9. I've been running Eclipse Galileo 3.5, and just upgraded to 3.5.1. This happened in both versions.
My present system information:
/usr/bin/java -version
java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
uname -a
Linux krumm 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:48:52 UTC 2009 x86_64 GNU/Linux