I don't have any ideas off hand, but maybe there is some kernel prerequisite with cryptlib or a bug outside of Mystic that I don't know about?
Yeah, I don't think it is a mystic bug but rather something with the Linux kernel related to cryptlib. It doesn't occur when mis is run in "server"
mode, only daemon. I'm assuming there is probably a difference to the kernel and access to libraries when running as a background process.
I'm happy that I found a reproducible way to fix it though. Either a kernel patch/update or reinstalation of linux-image always seems to do the trick :)
Thanks,
Mike
--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Stellar Darkness BBS (21:4/162)