Created attachment 1524767 [details] .metadata/.log Description of problem: I tried to start eclipse with empty workspace and it failed Version-Release number of selected component (if applicable): sh$ rpm -qa eclipse\* | sort eclipse-cdt-9.6.0-4.fc30.x86_64 eclipse-cdt-native-9.6.0-4.fc30.x86_64 eclipse-ecf-core-3.14.4-1.fc30.noarch eclipse-egit-5.2.0-1.fc30.noarch eclipse-emf-core-2.16.0-1.fc30.noarch eclipse-equinox-osgi-4.10.0-2.fc30.x86_64 eclipse-jdt-4.10.0-2.fc30.noarch eclipse-jgit-5.2.0-2.fc30.noarch eclipse-launchbar-2.2.2-1.fc30.noarch eclipse-linuxtools-libhover-7.1.0-1.fc30.noarch eclipse-platform-4.10.0-2.fc30.x86_64 eclipse-remote-3.0.0-0.6.git14c6611.fc30.noarch eclipse-rse-3.7.100-1.fc30.noarch eclipse-swt-4.10.0-2.fc30.x86_64 eclipse-tm-terminal-4.4.0-4.fc30.noarch eclipse-tm-terminal-connectors-4.4.0-4.fc30.noarch How reproducible: Deterministic on my machine (did not try on another laptop) Steps to Reproduce: 1. create empty directory in homedir 2. /usr/bin/eclipse 3. choose directory created in the 1st step as workspace Actual results: failed to open IDE Expected results: IDE started without any problem Additional info: there are some exceptions in .metadata/.log
Can you try forcing Eclipse to clean it's OSGi cache? $ eclipse -clean And if that still doesn't work, can you try starting with a completely fresh configuration area? $ mv ~/.eclipse ~/.eclipse.old $ eclipse If one of these options works, I would like to poke around in your ~/.eclipse(.old) directory.
(In reply to Mat Booth from comment #1) > Can you try forcing Eclipse to clean it's OSGi cache? > > $ eclipse -clean > > And if that still doesn't work, can you try starting with a completely fresh > configuration area? > > $ mv ~/.eclipse ~/.eclipse.old > $ eclipse > That one worked for me. I did not try 1st step. sh$ find ~/.eclipse.old | wc -l 2961 sh$ du -hs ~/.eclipse.old 136M /home/user/.eclipse.old sh$ ls -ln ~/.eclipse.old total 28 -rw-rw-r--. 1 1000 1000 93 Jun 17 2016 eclipse.uuid drwxrwxr-x. 2 1000 1000 4096 Jan 18 2017 org.eclipse.epp.logging.aeri drwxrwxr-x. 4 1000 1000 4096 Jan 29 18:52 org.eclipse.platform_155965261_linux_gtk_x86_64 drwxrwxr-x. 4 1000 1000 4096 Apr 10 2013 org.eclipse.platform_4.2.0_793567567 drwxrwxr-x. 6 1000 1000 4096 Jun 15 2017 org.eclipse.platform_793567567_linux_gtk_x86_64 I need to say that I have not started eclipse for longer time. But I upgraded packages frequently in rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
Do you still experience this issue?
I do not have anymore old laptop and comment 2 helped to me.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 EOL if it remains open with a Fedora 'version' of '31'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.