This one should be now fixed too. Just as I mentioned earlier, the fix will be available with the next major version (6.0) around one month from now or with the next development version on this Sunday.
Again, thank you for the report, and I'm sorry for the problem.