I also hit this bug recently. How can anybody rely on this software when it changes a supposedly readonly filesystem? There were no updates since this bug was reported. Not even an acknowledgement...