Yes, this was a bug in 1.1.2, which was buggy. So I moved to 1.2.0, which was not in the repo at the time, but without this bug.

--
darkpenguin

Reply via email to