Not certain if this is the exact same issue, but a very similar issue can be observed running from the commandline:
``` $ pgrep chromium | xargs kill # kill any running chromium (beware!) $ pgrep chromium | wc -l 0 # There are non running $ /snap/bin/chromium --product-version # command quits immediately. $ pgrep chromium | wc -l 1 $ /snap/bin/chromium # opens a browser. # Quit browser manually. $ pgrep chromium | wc -l 2 $ ps faux | grep chromium # check any processes running. \_/bin/sh /snap/chromium/1100/bin/chromium.launcher --product-version \_/bin/sh /snap/chromium/1100/bin/chromium.launcher ``` This shows that a process remains active after closing or running. The `ps faux` shows the leftover running processes and clearly shows they no longer have a parent: it seems the parent process forks, then quits, but leaves its child running. This hints at a mistake in the forking somewhere in the giant ball of spagetti (sorry) that the snap exectuables, scripts, simlinks and desktop files use to start a snap. ** Bug watch added: github.com/titusfortner/webdrivers/issues #168 https://github.com/titusfortner/webdrivers/issues/168 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859878 Title: Chrome does not quit when closing the window, it remains in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1859878/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
