I use the i3 window manager on my Linux machine. When I attempt to start Minecraft 1.15.2, the launcher tells me "Game crashed", followed by the generic "An unexpected issue occurred"-message.
I am not able to find any crash reports in my ~/.minecraft directory.
I am also unfortunately not able to attach launcher_log.txt ("Jira could not attach the file as there was a missing token. Please try attaching the file again." — I have tried again multiple times), so I'll have to resort to Pastebin: https://pastebin.com/raw/FxZRteqe
Note that the game starts perfectly fine when I run the launcher under GNOME. I would love to debug this myself, especially considering how few users share my software preferences, but the complete absence of useful crash reports or logs makes that rather difficult.
Linked issues
duplicates 1
Comments 3
I'm pretty sure this is actually entirely unrelated to my window manager and a duplicate of MCL-12973. Not sure why switching window managers coincided with this bug appearing again.
Sorry for the noise. Feel free to close this.
Hello,
Thanks for bringing this to our attention. I've made a note to add Gentoo to our list of Linux OS that we test with. As you say, this looks like MCL-12973 so I will resolve this issue and update that issue once we have addressed this. I'm happy you found a workaround!
Some additional information: after changing the path of the Java executable from the default to
/usr/lib64/openjdk-8/bin/java, the game starts. I'm not sure why the launcher is resolving the target of {{/usr/bin/java}} (this is a symlink in Gentoo, and as the run-java-tool message in the launcher log says, not supposed to be resolved by programs using Java), nor why this doesn't fail under GNOME.