when I try to run eclipse, the splash screen comes up, then it dies with a pop window error. The window says, "Problems during startup. Check the ".log" file in the ".metadata" directory of your workspace." I was using the 2.1.3-r3 ebuild. So that shouldn't be a problem. I posted the entire output of the .log file last time, but I will also include it in the this email, along with the java -version and emerge info output. They are below. java -version java version "1.4.1" Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.1-01) Java HotSpot(TM) Client VM (build Blackdown-1.4.1-01, mixed mode) emerge info Portage 2.0.50-r8 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3.20040420-r0, 2.6.5-gentoo-r1) ================================================================= System uname: 2.6.5-gentoo-r1 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.4.16 ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=i686 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://gentoo.chem.wisc.edu/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apache2 apm arts audiofile avi berkdb bonobo cdr crypt cups divx4linux dvd encode esd evo foomaticdb gd gdbm gif gnome gpm gstreamer gtk gtk2 gtkhtml icq imagemagick imlib java joystick jpeg libg++ libwww lirc mad mikmod motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png postgres python quicktime readline samba sdl slang spell ssl svga tcpd truetype usb x86 xml2 xmms xv yahoo zlib" .log file contents (this is repeated over and over for every time I tried to start the app and it failed, so I only included it once): !SESSION ---------------------------------------------------------------------- !ENTRY org.eclipse.core.launcher 4 0 Jun 25, 2004 24:45:20.10 !MESSAGE Exception launching the Eclipse Platform: !STACK java.lang.ExceptionInInitializerError at org.eclipse.core.internal.plugins.RegistryLoader.processManifestFile(RegistryLoader.java:89) at org.eclipse.core.internal.plugins.RegistryLoader.processPluginPathFile(RegistryLoader.java:136) at org.eclipse.core.internal.plugins.RegistryLoader.processPluginPathEntry(RegistryLoader.java:127) at org.eclipse.core.internal.plugins.RegistryLoader.processManifestFiles(RegistryLoader.java:104) at org.eclipse.core.internal.plugins.RegistryLoader.parseRegistry(RegistryLoader.java:63) at org.eclipse.core.internal.plugins.RegistryLoader.parseRegistry(RegistryLoader.java:71) at org.eclipse.core.internal.runtime.InternalPlatform.parsePlugins(InternalPlatform.java:890) at org.eclipse.core.internal.runtime.InternalPlatform.loadRegistry(InternalPlatform.java:834) at org.eclipse.core.internal.runtime.InternalPlatform.loaderStartup(InternalPlatform.java:684) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.eclipse.core.internal.boot.InternalBootLoader.startup(InternalBootLoader.java:1040) at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:838) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.eclipse.core.launcher.Main.basicRun(Main.java:291) at org.eclipse.core.launcher.Main.run(Main.java:747) at org.eclipse.core.launcher.Main.main(Main.java:583) Caused by: java.lang.ClassCastException at org.apache.xerces.parsers.SAXParser.<init>(SAXParser.java:95) at org.eclipse.core.internal.plugins.PluginParser.initializeParser(PluginParser.java:80) at org.eclipse.core.internal.plugins.PluginParser.<clinit>(PluginParser.java:44) ... 23 more Reproducible: Always Steps to Reproduce: 1. 2. 3. the only other thing I can think to mention, was that I initially tried to emerge eclipse months ago, and I got this problem. This time I installed from a later ebuild, and the new one it comes up in my Gnome menu as eclipse-2.1.3. Last time it just came up as eclipse in the gnome menu. I never unmerged the initial eclipse I installed and merging the newer version did not seem to unmerge the old, as the menu item for it still exists in my gnome menu. Clicking either gnome menu item gives the same error, which is decribed above. The only difference is the type of window that pops up with the error. The newer version of eclipse seems to have prettier windows, but the contents of the error message are the same. I have no idea if this is relevant, but thought I would include it, as I find it strange. I have been having this error for some time, but have only now been trying to work it out. The first version of eclipse I emerged months ago, did not come up when I listed all packages installed. Since I have emerged with ebuild 2.1.3-r3 it now does come up in the list. But like I said both programs seem to be installed on my system. Depending which gnome menu item I choose (eclipse or eclipse-2.1.3) I get different different style error windows. I have no idea why the old version is still there or how I can go about unmerging it. Could this have something to do with the problem?
I don't know if this is the problem, but try to emerge the latest blackdown and then recompile eclipse: emerge -C blackdown-jdk eclipse-sdk ACCEPT_KEYWORDS="~x86" emerge blackdown-jdk emerge eclipse-sdk However, there's eclipse 3.0 launched, I think we should focus on that.
What you should try is probably this: 1) emerge unmerge eclipse-sdk 2) check that /usr/lib/eclipse-2 (and /usr/lib/eclipse) are both empty, if not, delete the contents 3) remerge emerge 4) post your results here
I found the old eclipse that I installed months ago, it was in the /opt directory. I manually deleted it from there as there was no way to unmerge it. Then I did the following: emerge -C blackdown-jdk eclipse-sdk ACCEPT_KEYWORDS="~x86" emerge blackdown-jdk emerge eclipse-sdk It works now. Thanks for the help. I wonder if the newer version of the blackdown jdk did the trick, or if it was something else. I wouldn't mind trying to test eclipse 3.0. How do I emerge it? When I "emerge search eclipse" the only thing that comes up is eclipse-sdk-2.1.3-r3. I see no 3.0 versions. Although in the portage eclipse directory I see ebuilds for eclipse 3.0. Anyone want to tell me how to merge it, or do I need to figure it out on my own? MikeyB
ok, got eclipse 3.0 working as well with eclipse-sdk-3.0.0_rc3.ebuild. All my system info is in this bug, anything else I should do? thanks again for the help. MikeyB
This is indeed rather inconclusive. I've seen a few people get sig 11 with blackdown after upgrading kernels, but it may be totally unrelated. Since none of us developers have been able to reproduce this, and you guys have fixed it by deleting old eclipses and updating blackdown, I'll write this off as a fluke for now. If, however, you figure out how to reliably reproduce the problem, I'd very much like you to reopen the bug with the required steps, and I'll have another bash at it.
