However I must admit I have ran out of ideas. (for the same reason as above I haven't tried copying everything clockd related outside the chroot, I will do that as a last resort. Also the fact that the same clockd errors didn't prove to be fatal in other circumstances hint that maybe the clockd problems are unrelated to the fatal error. However the fact that the fatal error contains a function/class called pipDate might just confirm a clockd correlation. I will change the thread title in order to attract some attention.