Minecraft process doesn't completely exit on some linux setups

[RyanTheAllmighty]

What happened?

After exiting Minecraft from within the game, the process stays around and the launcher doesn't show again (because the process is still active according to the operating system).

Kill Minecraft button does nothing. Likely process has been sent a kill signal, but is hung or otherwise not responding.

Have seen this with 3 users:

1. Installed through deb file on Pop!_OS 22.04
2. Installed through flatpak on Linux Mint (unknown version)
3. Installed through deb file on Linux Mint (unknown version)

Need to see if it's something we can reproduce and understand what's going on, and maybe also see if we can send custom kill signals to the MC process on linux for these cases if we cannot determine any other cause

[Doomsdayrs]

I've seen this happened in other programs too.

The way to solve it is to forcefully kill a process, using kill -9 PID

[CoolCat467]

I have also seen this on my system using java -jar ATLauncher.jar, and my current workaround is to always launch ATLauncher manually from the terminal and if it ever hangs with Logging in to Minecraft or Minecraft itself won't close with the Kill Minecraft button, I can just control+C in the terminal that's running ATLauncher and everything closes.

[DanQuin9]

Just to add to this, it is also happening on my EndeavorOS system with atlauncher installed through the AUR.

Log shows minecraft hanging at

Shutting down map thread

This happens on Prism launcher as well where the game will not fully shutdown but the Kill button in Prism Launcher does kill minecraft once it hangs unlike ATlauncher. Some modpacks close fine.

Current workaround for me is to use the Kill Minecraft option instead of hitting Quit from in game. I'll see if I can upload some logs later.