If this is the case, then spawning things from the builtin terminal may too prevent update even when code is not in memory.Īlso, if for some reason kill doesn't end those processes you have to force the SIGKILL signal, default is SIGTERM and won't kill bugged processes.
The PIDs you pass to kill command may not be snaps. It seems like snap tracks the processes launched by snaps even if they aren't snaps themselves ( comment on this). Then you retry sudo snap refresh and it doesn't update code, and just produce the popup saying "you have XX days to.".
You run killall code, code is the command name to launch Visual Studio Code, and you get that the process isn't running at all. And in some situations it doesn't close them on exit. Real life example: Visual Studio Code seems to spawn processes like Android's ADB, omnisharp, etc. Or sudo snap refresh and it should work this time. Where those numbers are some random PIDs. Once you know the PIDs, you can simply run: sudo kill 44332 It will produce an output similar to this: Cannot update because it has associated apps running.Īnd most important, it will tell you the PIDs of the associated processes in the next line. Why? Because that one will fail too, but it will tell you why it fails for that specific package.
If you don't know the name, you can use sudo snap refresh -list to get it. Replacing for the name of what you are trying to update. If the notification still popups after the suggested killall offending_process_name, try running: sudo snap refresh Devs need to implement a system that automatically downloads security updates, and that they take effect when you restart the program. It is not like I leave my laptop on suspend every night, I shut it down every day, thus shutting down the browser, and even then the update is not automatic.
0 kommentar(er)
