Hide Forgot
Created attachment 1112651 [details] Crash Log Description of problem: Eclipse crashes on startup. It displays an error dialog pointing to a log, which is attached. Version-Release number of selected component (if applicable): eclipse-mylyn-3.17.0-2.fc24.noarch eclipse-tm-terminal-4.0.0-4.fc24.noarch eclipse-equinox-osgi-4.5.1-6.fc24.x86_64 eclipse-cdt-8.8.0-4.fc24.x86_64 eclipse-emf-core-2.11.1-1.fc24.x86_64 eclipse-linuxtools-libhover-4.2.0-2.fc24.noarch eclipse-jdt-4.5.1-6.fc24.x86_64 eclipse-egit-4.1.1-1.fc24.noarch eclipse-ecf-core-3.12.0-1.fc24.x86_64 eclipse-filesystem-1.0-6.fc24.x86_64 eclipse-p2-discovery-4.5.1-6.fc24.noarch eclipse-swt-4.5.1-6.fc24.x86_64 eclipse-e4-importer-0.1.0-0.5.gite4610b6.fc24.noarch eclipse-remote-2.0.0-2.fc24.noarch eclipse-platform-4.5.1-6.fc24.x86_64 eclipse-rse-3.7.0-6.git97bd591.fc24.noarch eclipse-mylyn-docs-wikitext-3.17.0-2.fc24.noarch eclipse-jgit-4.1.1-2.fc24.noarch eclipse-pde-4.5.1-6.fc24.x86_64 java-1.8.0-openjdk-1.8.0.65-15.b17.fc24.x86_64 How reproducible: Steps to Reproduce: 1. Upgrade to Rawhide (I'm running x86_64, upgraded from F23) 2. Attempt to start eclipse 3. Actual results: It displays an error dialog and then exits. Expected results: Eclipse should start. Additional info: See attached log.
Mat, please investigate.
It appears the problem is a broken symlink : /usr/share/eclipse/droplets/mylyn-commons/eclipse/plugins/org.apache.xmlrpc.server_3.1.3.jar Can you try installing xmlrpc-server and confirm the issue goes away ? It doesn't look like xmlrpc-server should be needed by mylyn-commons so maybe debugging the build might reveal why the symlink is being created.
Confirmed, installing xmlrpc-server makes the problem go away. I'd recommend at least temporarily adding a 'Requires: xmlrpc-server' to the package at least until it can be properly resolved.
I think I've found the issue. It's a packaging bug fixed some time ago but the change was never brought in. xmlrpc.server is a dependency of eclipse-mylyn-tests but instead of the symlink being created within that dropin location, it's created under mylyn-commons. https://github.com/rgrunber/fedoraproject-p2/commit/d5f09aa0fc9df8d920a74415d60a2960aff63768 attempts to explain one such case, which also happened in eclipse-mylyn. I'll update Tycho to include the latest fedoraproject-p2 and then rebuild Mylyn.
http://koji.fedoraproject.org/koji/buildinfo?buildID=710548 should resolve the issue.
Matt has pointed out that Mylyn is not packaged correctly, and it's starting to look like the fedoraproject-p2 changes made to fix all this might have issues. I may end up having to revert the changes to Tycho and simply add a Requires as a workaround.
After some investigating, I've found what I believe is the root cause. The new changes to fedoraproject-p2 that were supposed to (among other things) fix the broken symlink, correctly discovered that eclipse-mylyn has subpackage cycles which, in turn, affected its ability to properly place the links (and every symlink ended up under one subpackage either sdk, or docs) In case anyone is interested, the following edges needed to be broken by moving the offending feature into the sdk subpackage. (org.eclipse.mylyn.context.development.feature.group) mylyn-commons -> mylyn-sdk(org.eclipse.mylyn.context.sdk.feature.group) (org.eclipse.mylyn.commons.development.feature.group) mylyn-commons -> mylyn-sdk(org.eclipse.mylyn.commons.sdk.feature.group) (org.eclipse.mylyn.versions.development.feature.group) mylyn-versions -> mylyn-sdk(org.eclipse.mylyn.versions.sdk.feature.group) (org.eclipse.mylyn.builds.development.feature.group) mylyn-builds -> mylyn-sdk(org.eclipse.mylyn.builds.sdk.feature.group) (org.eclipse.mylyn.docs.development.feature.group) mylyn-docs -> mylyn-sdk(org.eclipse.mylyn.docs.sdk.feature.group) (org.eclipse.mylyn.versions.development.feature.group) mylyn-versions -> mylyn-versions-subclipse(org.eclipse.mylyn.subclipse.feature.group) I'll have a build for this soon.
http://koji.fedoraproject.org/koji/buildinfo?buildID=712129 should resolve the issue (3.18.0-3). Mylyn has also been updated to 3.18.0 since but the issues reported is a packaging one and would have existed even on the newer version.