I found, that I get the same problem when using svn trunk.
After switching to the 2.2 branch, the problem disappears.

So if you're using trunk, please file a bug report, and switch to 2.2. in the mean time.

Marc

Reply via email to