Hello,
Thanks for zour report. > I installed eclipse-sdk, and selected "Eclipse" from the Gnome menu. Running eclipse in a terminal gives you additional informations like the runtime that is used to execute Eclipse > It popped up a little box to announce it was starting, and then > displayed another window with a little progress bar. For a while it ate > all CPU, and then after about 30 seconds, it stopped using CPU -- but > did not appear to progress any further. I gave up and killed it after a > few minutes. > > Here's the state of the progress bar when it hung: > > [######################################## ] > Loaded org.eclipse.jdt.core Eclipse SDK > > I don't have kaffe installed, so I don't think it's the same hanging > problem to do with kaffe as reported earlier. As you have java-gcj-compat installed I think eclipse uses this as its runtime. Unfortunately this currently breaks due to a binutils bug. A workaround is either to use another runtime to execute eclipse or to run the following command in a separate terminal: while true ; do killall c++filt 2>/dev/null ; done Downgrading binutils to an older version from snaphost.debian.net helps also. > BTW reportbug only shows direct dependencies, so here's the output of > "aptitude search ~i~djava": The direct dependencies are okay. Cheers, Michael -- Escape the Java Trap with GNU Classpath! http://www.gnu.org/philosophy/java-trap.html Join the community at http://planet.classpath.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]