A> Why are you discussing this in Baterypatch thread instead of KP50 thread, where someone may read it. You should discuss this in the KP thread. This would be like taking your car to a TV repair shop... no much is going to happen to fix your car.

B> I had this bug in KP49, and just seconds ago rebooted via command line under KP50, and it rebooted cleanly. I rebooted primarily to be sure all the latest new CSSU stuff was in place and happy. That may have been a fluke (as I've had it work under K49 on occasion as well), but so far it's 1 for 1.