How to Install Eclipse IDE on Fedora Linux
You’ll learn how to grab the right Eclipse package, make sure Java is ready, and get the IDE running without chasing error messages. No “you need a corporate license” nonsense – just straight‑up steps that work on recent Fedora releases.
1. Verify you have a working JDK first
Eclipse bundles its own Java runtime, but if you’re already using OpenJDK for other projects it’s cleaner to use that instead. Run:
java -version
If the output shows Java 11 or higher, you’re good. If nothing comes up or you see an older version, install a recent JDK:
sudo dnf install java-latest-openjdk
Why this matters: Eclipse will refuse to start if it can’t find a supported JRE, and the error logs are way less helpful than a clear “Java missing” message.
2. Grab the right download from eclipse.org
Head over to eclipse.org/downloads and pick Eclipse IDE for Java Developers (or whatever flavor you need). Make sure you select the Linux tarball, not the Windows or Mac ones. I’ve seen folks accidentally grab a .zip file that only works on Windows and then wonder why nothing launches.
Download it to a folder you’ll remember – e.g., ~/Downloads. On Fedora 38/39 the latest Eclipse still ships as a .tar.gz bundle; there’s no official RPM, so extracting it is all you need.
3. Extract the tarball and run Eclipse
cd ~/Downloads tar -xzf eclipse-java-*.tar.gz
You’ll get an eclipse directory. Inside that, a single executable called eclipse. Start it with:
~/Downloads/eclipse/eclipse
The first launch will trigger the “Eclipse is not installed properly” dialog if you’re running a Wayland session without the proper GTK libraries. If that happens, add the following to your .desktop file or use a wrapper script:
export GDK_BACKEND=x11 ~/Downloads/eclipse/eclipse
Why this matters: Fedora’s default Wayland session can trip up older Java GUIs; forcing X11 ensures the SWT toolkit renders correctly.
4. Pin Eclipse to your desktop for future launches
If you’re happy with the manual start, create a simple launcher:
cat > ~/.local/share/applications/eclipse.desktop <<EOL [Desktop Entry] Name=Eclipse IDE Comment=Java development environment Exec=/home/you/Downloads/eclipse/eclipse Icon=eclipse Terminal=false Type=Application Categories=Development;IDE; EOL
Replace /home/you with your actual home path. Now you’ll see Eclipse in the application menu, and it will remember your workspace between sessions.
5. Common hiccups and how to squash them
- “Could not find or load main class” – Make sure you’re running the binary from the extracted folder, not a stale symlink that points at an older version.
- Segmentation fault on launch – This usually indicates missing libraries. Installing gtk3 and libX11 via sudo dnf install gtk3 libX11 often fixes it.
- “Eclipse cannot determine the Java Runtime” – Explicitly set JAVA_HOME in a wrapper script:
export JAVA_HOME=$(dirname $(readlink -f $(which java))/../) ~/Downloads/eclipse/eclipse
This points Eclipse straight to the JDK you installed with dnf.
- Wayland “cannot open display” – The quick fix above (GDK_BACKEND=x11) works, or run Eclipse from an Xorg session instead of Wayland if you want no extra fuss.
6. Optional: Install via Flatpak for easier upgrades
If you prefer not to manage the tarball manually, Fedora’s Flatpak repo ships Eclipse. It pulls its own JRE and keeps everything sandboxed:
sudo dnf install flatpak flatpak install flathub org.eclipse.java
Launch it with flatpak run org.eclipse.java. The downside? Each update is a full download; the tarball approach gives you quicker incremental installs.
That’s all there is to it. Grab the tarball, make sure Java is in place, and you’re ready to code on Fedora. If anything goes sideways, check that library list above – it’s saved me from a lot of head‑scratching.
