I performed this update: [mbooth@10-2-5-11 .metadata]$ sudo yum history info 150 Loaded plugins: langpacks, presto, refresh-packagekit Transaction ID : 150 Begin time : Thu Mar 14 14:33:32 2013 Begin rpmdb : 3555:4f9f1d640fe13f3267990bc4cbb9d7e32465cfa1 End time : 14:34:55 2013 (83 seconds) End rpmdb : 3555:d5692bf46a47f16ecb75864d7cd6d183dca426f2 User : Mat Booth <mbooth> Return-Code : Success Command Line : update eclipse* java* Transaction performed with: Installed rpm-4.10.3.1-1.fc18.x86_64 @updates Installed yum-3.4.3-51.fc18.noarch @updates Installed yum-metadata-parser-1.1.4-7.fc18.x86_64 @fedora Packages Altered: Updated eclipse-equinox-osgi-1:4.2.2-0.1.git20121217.fc18.x86_64 @updates Update 1:4.2.2-4.fc18.x86_64 @updates Updated eclipse-jdt-1:4.2.2-0.1.git20121217.fc18.x86_64 @updates Update 1:4.2.2-4.fc18.x86_64 @updates Updated eclipse-pde-1:4.2.2-0.1.git20121217.fc18.x86_64 @updates Update 1:4.2.2-4.fc18.x86_64 @updates Updated eclipse-platform-1:4.2.2-0.1.git20121217.fc18.x86_64 @updates Update 1:4.2.2-4.fc18.x86_64 @updates Updated eclipse-swt-1:4.2.2-0.1.git20121217.fc18.x86_64 @updates Update 1:4.2.2-4.fc18.x86_64 @updates Updated java-1.7.0-openjdk-1:1.7.0.9-2.3.7.0.fc18.x86_64 @updates Update 1:1.7.0.9-2.3.8.0.fc18.x86_64 @updates Updated java-1.7.0-openjdk-devel-1:1.7.0.9-2.3.7.0.fc18.x86_64 @updates Update 1:1.7.0.9-2.3.8.0.fc18.x86_64 @updates Updated java-1.7.0-openjdk-javadoc-1:1.7.0.9-2.3.7.0.fc18.noarch @updates Update 1:1.7.0.9-2.3.8.0.fc18.noarch @updates Updated java-1.7.0-openjdk-src-1:1.7.0.9-2.3.7.0.fc18.x86_64 @updates Update 1:1.7.0.9-2.3.8.0.fc18.x86_64 @updates And now Eclipse no longer starts. Instead I simply get the following exception in my workspace .log: !SESSION 2013-03-14 14:42:20.732 ----------------------------------------------- eclipse.buildId=4.2.0.M20130304-1457 java.version=1.7.0_09-icedtea java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_GB Command-line arguments: -os linux -ws gtk -arch x86_64 !ENTRY org.eclipse.osgi 4 0 2013-03-14 14:42:28.868 !MESSAGE Application error !STACK 1 java.util.EmptyStackException at java.util.Stack.peek(Stack.java:102) at java.util.Stack.pop(Stack.java:84) at org.eclipse.e4.ui.css.core.impl.sac.CSSDocumentHandlerImpl.endDocument(CSSDocumentHandlerImpl.java:74) at org.apache.batik.css.parser.Parser.parseStyleSheet(Parser.java:238) at org.eclipse.e4.ui.css.core.impl.dom.parsers.AbstractCSSParser.parseStyleSheet(AbstractCSSParser.java:64) at org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.parseStyleSheet(AbstractCSSEngine.java:180) at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.setTheme(ThemeEngine.java:415) at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.setTheme(ThemeEngine.java:376) at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.restore(ThemeEngine.java:538) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.initializeStyling(PartRenderingEngine.java:1179) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:945) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:638) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:593) at org.eclipse.equinox.launcher.Main.run(Main.java:1447) at org.eclipse.equinox.launcher.Main.main(Main.java:1423)
Have you tried running eclipse -clean ?
Yes, that makes no difference. I also tried starting Eclipse with a brand new, empty workspace. Also no difference. The only fix I have found so far is to downgrade to version 1:4.2.2-0.1.git20121217.fc18 of the following packages: eclipse-equinox-osgi eclipse-jdt eclipse-pde eclipse-platform eclipse-swt
Would you please attach eclipse -clean -debug -consoleLog output?
Created attachment 710064 [details] Debug log output Sure thing, see attached.
Btw, I just noticed that xml-commons-apis was not updated with eclipse but I pushed them as one update see https://admin.fedoraproject.org/updates/FEDORA-2013-3470/xml-commons-apis-1.4.01-11.fc18,eclipse-4.2.2-4.fc18
Aha, updating xml-commons-apis has fixed it. In that case, Eclipse should probably specify a dependency on xml-commons-apis >= 1.4.01-11
I've seen this exception too, but since my update included xml-commons-apis a simple eclipse -clean solve it.
Same exception, same stack trace, same workaround (downgrade those 5 packages) here. I have xml-commons-apis 1.4.01-11 installed, that did NOT fix this bug for me.
*** Bug 922116 has been marked as a duplicate of this bug. ***
*** Bug 922436 has been marked as a duplicate of this bug. ***
Saw the same problem and couldn't start eclipse after the upgrade. "eclipse -clean" fixed the problem, and Eclipse started correctly (and now starts again even without "-clean"). I don't know what "-clean" does, but it didn't seem to have any bad side-effects (it didn't "clean" the list of open projects, loaded files, and so on).
(In reply to comment #11) > Saw the same problem and couldn't start eclipse after the upgrade. "eclipse > -clean" fixed the problem, and Eclipse started correctly (and now starts > again even without "-clean"). > > I don't know what "-clean" does, but it didn't seem to have any bad > side-effects (it didn't "clean" the list of open projects, loaded files, and > so on). I forgot to mention that my update did get xml-commons-apis-1.4.01-11.fc18.noarch (which some previous comments suggested is important), but Eclipse still didn't work. The "eclipse -clean" was necessary to get it back to working.
For the sake of completeness: This is an update that introduces stricter dependency to xml-commons-apis. https://admin.fedoraproject.org/updates/FEDORA-2013-3945/eclipse-4.2.2-5.fc18 Please +1 it to get it mirrored and distributed as soon as possible (if eclipse-4.2.2-4 and latest xml-commons-apis worked for you). Chris, have you run eclipse -clean?
-clean forces Eclipse to reread all bundles. In a regular startup, Eclipse reads all plugins and caches them inside ~/.eclipse (amongst other settings). If one of those bundles is changed, it goes unnoticed unless -clean is run. My common update scenario assumes that each bundle change is followed by Eclipse platform update - to *force* the update. In this case, xml-commons-apis had apparently some delays while it was mirrored, and the Eclipse platform arrived as an update earlier :-(. I apologize for the inconvenience. Here is the update that needs to be released to make it impossible to update Eclipse without xml-commons-apis. Please +1 it. https://admin.fedoraproject.org/updates/FEDORA-2013-3945/eclipse-4.2.2-5.fc18
@Krzysztof Daniel: Yes, I did. I tried several times with no success. Possible reason is that I have _many_ eclipse plugins (from RPM package and from Marketplace) installed. I tried again today using this steps: 1. start "old" eclipse 4.2.1 with -clean parameter 2. update eclipse via yum 3. start "new" eclipse 4.2.2 with -clean parameter And it worked. Thanks a lot for help! Seems to be fixed for me.
Closing per comment 15.