Description of problem: When invoking the "New Java Class" dialog, you cannot complete the dialog because the "Finish" button is unreactive. It does not respond to clicks nor hitting "enter" when it has focus. Nothing is uttered on stderr when you attempt it. Version-Release number of selected component (if applicable): 3.5.2-2.fc13 How reproducible: always (for us) Steps to Reproduce: 1. eclipse 2. new java project 3. new java class Actual results: unreactive new java class dialog "finish" button Expected results: Dialog to disappear, new class to be created Additional info: Searching around, there are large numbers of reports of this issue, and similar issues, being partially solved by exporting GDK_NATIVE_WINDOWS=true in the environment. This does not help in our case since /usr/bin/eclipse already does this: $ cat $(which eclipse) #!/bin/sh # Work around bugs.eclipse.org/290395 export GDK_NATIVE_WINDOWS=true /usr/lib/eclipse/eclipse "$@" Invoking /usr/lib/eclipse/eclipse without exporting the variable makes no difference to this particular issue. Reproducible every time for several users on all machines of our 69 machine Fedora 13 lab.
When clicking the "Finish" button, I get the following in <workspace>/.metadata/.log: !ENTRY org.eclipse.ui 4 0 2010-11-04 17:24:53.450 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at org.eclipse.jdt.internal.ui.JavaPlugin.getTemplateContextRegistry(JavaPlugin.java:793) at org.eclipse.jdt.internal.ui.JavaPlugin.getTemplateStore(JavaPlugin.java:838) at org.eclipse.jdt.internal.ui.wizards.NewElementWizard.warnAboutTypeCommentDeprecation(NewElementWizard.java:145) at org.eclipse.jdt.internal.ui.wizards.NewClassCreationWizard.performFinish(NewClassCreationWizard.java:74) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:752) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:135) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
I just tried switching the java alternative to the sun jre, $ java -version java version "1.6.0_22" Java(TM) SE Runtime Environment (build 1.6.0_22-b04) Java HotSpot(TM) Server VM (build 17.1-b03, mixed mode) no change. I haven't tried switching the jdk yet: $ javac -version Eclipse Java Compiler 0.894_R34x, 3.4.2 release, Copyright IBM Corp 2000, 2008. All rights reserved.
It appears you don't use OpenJDK. Any particular reason why? How did you install Eclipse? Using yum or upstream precompiled tarballs? I'm using Eclipse Version: 3.5.2, Build id: M20100211-1343 with $ java -version java version "1.6.0_18" OpenJDK Runtime Environment (IcedTea6 1.8.2) (fedora-43.1.8.2.fc13-x86_64) OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode) and it works without a problem. You may want to try installing OpenJDK: $ yum install java-1.6.0-openjdk
We do use the OpenJDK. We install eclipse via kickstart package group '@eclipse'. When I said I'd just tried switching the java alternative, I meant from the default OpenJDK to the Sun JRE, to see if that fixed it (it didn't). The lab's normal configuration is: [njd33@mill04 ~]$ java -version java version "1.6.0_18" OpenJDK Runtime Environment (IcedTea6 1.8.1) (fedora-42.b18.fc13-i386) OpenJDK Server VM (build 14.0-b16, mixed mode) [njd33@mill04 ~]$ rpm -q eclipse-platform java-1.6.0-openjdk eclipse-platform-3.5.2-2.fc13.i686 java-1.6.0-openjdk-1.6.0.0-42.b18.fc13.i686
I noticed your openjdk was newer than mine so I upgraded but the bug remains [njd33@mill04 ~]$ rpm -q eclipse-platform java-1.6.0-openjdk eclipse-platform-3.5.2-2.fc13.i686 java-1.6.0-openjdk-1.6.0.0-43.1.8.2.fc13.i686
For what it's worth, I've just tried eclipse-SDK-3.6.1-linux-gtk.tar.gz from upstream and it worked.
Can you try fedora 14 with the shipped Eclipse SDK 3.6.1?
Yes probably. We should be able to try that this week on one machine at least. Deploying F14 on all our Linux cluster machines would be a major job, though, so if that does work, I'd be more inclined to try and backport it to F13 or deploy the upstream eclipse via our configuration management system. I am not up to speed on Fedora release policies. Is F13 dead now F14 is released? (We just upgraded them to F13 prior to the F14 release: unfortunately our window of opportunity is not lined up nicely with Fedora release cycles).
(In reply to comment #8) > Yes probably. We should be able to try that this week on one machine at least. > Deploying F14 on all our Linux cluster machines would be a major job, though, > so if that does work, I'd be more inclined to try and backport it to F13 or > deploy the upstream eclipse via our configuration management system. > > I am not up to speed on Fedora release policies. Is F13 dead now F14 is > released? > > (We just upgraded them to F13 prior to the F14 release: unfortunately our > window of opportunity is not lined up nicely with Fedora release cycles). F13 will be EOLed in 7 months.I really want to help fixing the problem but I can't reproduce. Is there smth suspicious in the Error Log? Can you run eclipse -clean -debug -consolelog and reproduce the unreactive finish button and send me the output? Are there any chances that you have replaced Fedora's junit/junit4 with jars coming from elsewhere? Are there any broken links in /usr/lib[64]/eclipse and subdirs?
Hello, $ eclipse --clean --debug --consolelog 2>&1 | tee out CompilerOracle: exclude org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith CompilerOracle: exclude org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding.<init> CompilerOracle: exclude org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates.instantiateTemplate CompilerOracle: exclude org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage.addBinding CompilerOracle: exclude org/python/pydev/editor/codecompletion/revisited/PythonPathHelper.isValidSourceFile CompilerOracle: exclude org/python/pydev/ui/filetypes/FileTypesPreferencesPage.getDottedValidSourceFiles Note that no output was generated by clicking on the "Finish" button: the above all happened in the lead up to that. The .metadata/.log file gets a backtrace as in comment #1 when I click the "Finish" button. I think it's very unlikely that we could have replaced Fedora's junit packages. The only custom repository we configure is Adobe's Flash. There are no broken links in /usr/lib/eclipse. These are 32-bit systems so there is no /usr/lib64.
$ yum list all | grep junit ant-junit.i686 1.7.1-13.fc13 @anaconda-InstallationRepo-201005130056.i386 junit.i686 3.8.2-6.4.fc12 @anaconda-InstallationRepo-201005130056.i386 junit4.i686 4.6-1.fc13 @anaconda-InstallationRepo-201005130056.i386 junit-demo.i686 3.8.2-6.4.fc12 fedora junit-javadoc.i686 3.8.2-6.4.fc12 fedora junit-manual.i686 3.8.2-6.4.fc12 fedora junit4-demo.i686 4.6-1.fc13 fedora junit4-javadoc.i686 4.6-1.fc13 fedora junit4-manual.i686 4.6-1.fc13 fedora junitperf.noarch 1.9.1-4.2.fc12 fedora junitperf-demo.noarch 1.9.1-4.2.fc12 fedora junitperf-javadoc.noarch 1.9.1-4.2.fc12 fedora maven-surefire-provider-junit.noarch 2.3-7.7.fc12 fedora maven-surefire-provider-junit4.noarch 2.3-7.7.fc12 fedora I haven't seen that '@anaconda-Install...' annotation before.
well i have the same bug here. but when i remove eclipse-phpeclipse-1.2.3-1.fc13.noarch i don't have the bugs anymore
eclipse-phpeclipse.noarch 1.2.3-1.fc13 @Fedora 13 - i386 I can confirm that removing this package fixes the problem for me. Yay!
I have rebuilt for f13 the F14 package of eclipse it seems to work for me can you give it a try http://wpublic.int-evry.fr/~doutrele/eclipse-phpeclipse-1.2.3-2.fc13int.noarch.rpm
The problem returns if I install that package. I tried removing .eclipse and using a fresh workspace to be sure. eclipse-phpeclipse.noarch 1.2.3-2.fc13int installed
I'm changing the component to be eclipse-phpeclipse and requesting the maintainer to take the needed action to fix the problem.
indeed i got other report for my users they still have the bug too. then it didn't solve the problem
(In reply to comment #16) > I'm changing the component to be eclipse-phpeclipse and requesting the > maintainer to take the needed action to fix the problem. Thanks for the heads-up. I will try to take a look at this next week. PHPEclipse seems problematic on the latest versions of Eclipse *sigh*
Is there any update on this bug? i have soon some courses which need to use php eclipse on the same computers than regulars java eclipse users
is there any update on this bug? We have a course that need phpeclipse
I would strongly recommend people to use http://eclipse.org/pdt/ and getting it packaged into Fedora.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug is still there. eclipse-phpeclipse noarch 1.2.3-3.fc15 on my system. After its removal I can confirm that I can now create the Java class .
Should we retire eclipse-phpeclipse? Mat?