This is still an issue in 1.13-pre1.
The problem seemed to resolve itself when I ran the Minecraft.exe launcher with Wine. Perhaps this has to do with what versions of Java are being used?
In my ordinary Minecraft launcher profile, where the game does crash as described in this report: java.version is 1.8.0_161, java.vendor is Oracle Corporation, I launch the launcher with /usr/bin/java -jar Minecraft.jar, and the actual executable the launcher uses to start Minecraft (the "Executable" field in the 1.13 profile) is /usr/lib/jvm/java-8-oracle/jre/bin/java.
In my Wine-based Minecraft launcher profile, where the game doesn't crash: java.version is 1.8.0_25, java.vendor is Oracle Corporation, I launch the launcher with wine Minecraft.exe, and the "Executable" field is Z:\home\florrie\Downloads\jre-x64\1.8.0_25\bin\javaw.exe.
I guess it could be an issue with running Java 1.8.0_161 instead of 1.8.0_25? I haven't tested with 1.8.0_25 through the launcher without using wine, yet, though.
Good to know this isn't specific to just my computer, @unknown! (I thought it might be, since I read somewhere that 1.13 running LWJGL 3 would make it better for Linux computers. And that's probably mostly true, just not in this case.)
Yes, it's still an issue in 18w01a.
This looks to be an issue again in 1.13, with LWJGL 3.
Some new, more specific details:
Using Java from oracle (java.com) - not OpenJDK - makes no difference.
The game does not hang immediately once the menu opens - rather, the game runs properly for about two seconds, then the computer hangs.
I was able to get the computer to stop hanging by pressing down on the power button once, which requested the computer to suspend; doing so caused Minecraft to close, after which the computer suspended. Unsuspending the computer worked fine.
Since my last update on this issue, I had to restore my computer altogether from a backup, and I ended up having to reinstall Java. The issue does not persist. I now run, according to java -version, OpenJDK Runtime Environment (build 10.0.2+13-Debian-1). (This is the same binary set in "Java Settings (Advanced)" of my Minecraft profile.)
While this isn't an actual update on whether the issue still exists, I expect it had to do with bad/mixed-up Java versions; so if anyone else has this issue, running the version of Java I mentioned above might work.