exequtic
commented
1 month ago For me, this problem is a real pain in the ass. I spent a lot of time trying to detach the terminal process from the plasmashell process so that it would be independent, but without success. I mistakenly thought I had fixed it, but later it turned out I hadn't.
launching the script with kstart, so if plasmashell crashes, it will not close with it
It seems you were right. I quickly checked, and now, together with kstart, restarting plasmashell no longer closes the terminal. When I have time, I'll see what I can do about it. Thanks for the find!
QueenOworld
I have had 2 instances of apdatifier crashing during a system upgrade because of plasmashell crashing and forcing me to boot a recovery environment because I didn't fix everything caused by a crash mid system upgrade. I did a lot of searching and came to the solution of launching the script with kstart, so if plasmashell crashes, it will not close with it. I couldn't modifiy apdatifier in such a way to make it work, so my temporary solution is to recreate what the upgrade script does exactly, as well as visually match it, and change the line that runs sh.exec(cmd.upgrade) in tools.js to be sh.exec(`kstart ~/.local/bin/upgradescript`) This works fine, and it no longer crashes along with plasmashell, but I couldn't figure out how to implement updating plasmoids, so it isn't 100% exact. If apdatifier could be changed in a way that launches its scripts as its own process, no longer as a child of plasmashell, that would be very nice, as crashing mid system upgrade really sucks. I don't know if kstart is the best solution for this, but as far as I know, it works and would just need the plasmoid to be modified to use it.