[Linux] After Game Closes It Does Not Kill All Processes and Subsequently Prevents Launcher from Launching

Whenever I close out Minecraft running on this machine (Ubuntu Linux 18.04) it successfully closes the game, however it does not quit all the processes running. This prevents the launcher from being launched.

After doing some research I found that a 'grep' search for the term 'minecraft' in the terminal returns multiple different results. Here is the output:

ps -ef | grep [M]inecraft 

jrobins+  6387  6383  0 23:43 tty1     00:00:00 /opt/minecraft-launcher/minecraft-launcher --type=zygote --no-sandbox --lang=en-US --log-file=/home/jrobinson/.minecraft/launcher_log.txt --user-agent=Minecraft Launcher/2.1.2482 (bcb98e4a63) Linux (4.18.0-15-generic; x86_64) --launcherui

jrobins+  6402  6383  1 23:43 tty1     00:00:08 /opt/minecraft-launcher/minecraft-launcher --type=gpu-process --no-sandbox --window-depth=24 --x11-visual-id=33 --lang=en-US --log-file=/home/jrobinson/.minecraft/launcher_log.txt --user-agent=Minecraft Launcher/2.1.2482 (bcb98e4a63) Linux (4.18.0-15-generic; x86_64) --launcherui --supports-dual-gpus=false --gpu-driver-bug-workarounds=5,19,30,50,59 --disable-gl-extensions=GL_ARB_occlusion_query GL_ARB_occlusion_query2 --gpu-vendor-id=0x8086 --gpu-device-id=0x0126 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --lang=en-US --log-file=/home/jrobinson/.minecraft/launcher_log.txt --user-agent=Minecraft Launcher/2.1.2482 (bcb98e4a63) Linux (4.18.0-15-generic; x86_64) --launcherui --mojo-application-channel-token=780D91C4EA533CFF7993E125A80AA0C6 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd

jrobins+  7954  6387  3 23:45 tty1     00:00:17 /opt/minecraft-launcher/minecraft-launcher --type=renderer --no-sandbox --disable-databases --primordial-pipe-token=C1A7527E8BEF5ECA86D4C97F2EC72110 --lang=en-US --lang=en-US --log-file=/home/jrobinson/.minecraft/launcher_log.txt --user-agent=Minecraft Launcher/2.1.2482 (bcb98e4a63) Linux (4.18.0-15-generic; x86_64) --launcherui --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553 --disable-accelerated-video-decode --mojo-application-channel-token=C1A7527E8BEF5ECA86D4C97F2EC72110 --channel=6383.1.1530311659 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd

As you can see, there are three processes still running. I follow up the grep search with a kill command on the '6387' process, it closes both 6387 and 7954, and follow that with another kill command for the final 6402 process.

I can then open the launcher and it works just as expected and should be.

Other interesting notes: If i open the launcher, and close the launcher, there are no extra processes running after closure. This incident only occurs whenever I close the game. Whether through the "Quit Game" button, or clicking out using the 'x' in the top right hand corner.