This is yet another indication that it is a bug, because so many instances would not be needed to speed up the opening of a new pdf as compared to a cold start. If I open and close 66 pdfs, there remain 66 instances running in the background. Only clean install new versions, that is the To me the current Foxit Reader startup with multiple unclosed instances in the background doesn’t look any faster than a cold start. But now I think I will never do an update. This is why I always disable auto updates. Those usually work quite well, but any later upgrades are very risky, often whack things that were working well before. I guess I will just have to tolerate this bug until a new LM version comes out, and then do a clean install. Only after I initiated an auto upgrade to this latest version did this new problem manifest. I don't know if Foxit Reader was still running in the background back then or not, but even if it did, the old LM version did not get stuck when I wanted to shut it down.

Originally I have installed LM 20.2 Xfce and this issue did not exist. Why would I need to do a manual shutdown of programs (especially those I don't even see running) before I dare to click the shut-down button? Makes no sense, therefore I consider this to be a system bug that needs to be fixed.

Even if this is the case and I can't do anything about it, still Linux Mint supposed to know that when I click the shut-down button, then I mean it, and all running programs should be closed automatically. I am not happy with programs I close to only hide themselves instead of closing.

Foxit reader update getting stuck