Thank you for your feedback. This bug is now fixed in CVS.
It was caused by a fix for another bug, trying to prevent such bugs in
the future..unfortunately nobody tested the RCs (release candidates) we
release before actual releases and 5.2.3 went out with this bug
unnoticed..
Thank you for your feedback. This bug is now fixed in CVS.
It was caused by a fix for another bug, trying to prevent such bugs in
the future..unfortunately nobody tested the RCs (release candidates) we
release before actual releases and 1.8.6 went out with this bug
unnoticed..