minecraft-java-edition – Minecraft 1.8.9 Won’t Start on Linux? Here’s How to Fix It

minecraft-java-edition

I use Minecraft: Java Edition on a Linux system. Whenever I try to launch versions 1.8.9 and before, the doesn't start, and as soon as I hit the "Play" button, the Launcher re-opens stating that the game has crashed. The game runs perfectly if I play it in earlier versions.

I was able to generate a crash report by enabling "Open output log when games start" in the Settings menu. It's a bit lengthy, so I made a Pastebin for it… https://pastebin.com/KN2Ac9vb

I would like to know what's going wrong, and how to fix this error so I can play 1.8.9 properly.

Best Answer

According to this question on stackoverflow, this is due to an issue in your Java install. Grabbing an earlier version of (or even just reinstalling) Java should fix it. Alternate JDKs may also work.

Related Solutions

Minecraft – How to run mods with 1.7.2

This Reddit post states that Forge ModLoader is incompatible with Java 8 Update 20 and later. It has been fixed for recent Minecraft 1.7.10 builds, however, there is currently no fix for 1.7.2 and 1.6.4. In the meantime, try rolling back to an earlier version of Java (version 7, or a Java 8 build prior to Update 20).

Minecraft Java Edition – How to Fix Crashing Before or During Startup

The two important parts of your crash log are:

#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000005cfb6e7e, pid=360, tid=0x00000000000023e4

and

# Problematic frame:
# C  [atio6axx.dll+0xfa6e7e]

This is a known issue (though it's not a bug in Minecraft). The file atio6axx.dll is what Minecraft uses to talk to AMD/Radeon brands of video cards, and when it causes an EXCEPTION_ACCESS_VIOLATION (0xc0000005) it means that there is a problem with those graphics drivers.

To fix this,

Confirm that your graphics drivers are fully up to date.
If they are fully up to date, this means there is a bug in the latest AMD drivers, and you'll have to wait for AMD to fix them. In that case you might want to report the bug to AMD.