|
There is a ping every ~5 seconds and sickel seems to be simply waiting for those. If nickel keeps sending pings even when sickel is not running, where do they go? Best case they are discarded but worst case a buffer fills up somewhere and nickel hangs once its full.
Sending sickel to sleep (STOP, CONT signal) is not an option either; once you wake it, it reboots even though nickel is running fine and dandy.
I wonder what happens if you ever do anything that takes nickel longer than 5 seconds? Opening a large image or PDF perhaps.
My current workaround is: send sickel to sleep (SIGSTOP). And when nickel is back, kill it entire. It's automatically restarted as a d-bus service and does not kill nickel then. The sending to sleep is only to prevent that auto-restart.
Not sure if that's a great solution though.
|