Justin This was just the same code with debug logs. I understand now what's happening and I'm going to propose a fix on GitHub, as soon as I have a good solution.
This log shows what's happening:
pisi_callback: signal: error isn't handled by
My thoughts on why it receives an 'error' signal:
I have a very fast M.2 SSD and I disabled login on startup, because I use full disk encryption. When the package manager searches for updates, my network connection isn't established yet or changes at this very moment. The PiSi package manager (eopkg) doesn't like that, aborts and returns an error signal.
I don't know what eopkg is actually doing, this is just an assumption.
Simple fix in line 221 (untested):
It's still dangerous in my opinion, because if PiSi/eopkg gives us a different error signal in the future, ScUpdateApp could loop again endlessly.