The identical issue has been reported against 5.5.18, which has the fix for this bug included. So it cannot be a duplicate of bug #705688. Or bug #705688 has not been really fixed in 5.5.18. This should be clarified before changing the status of this bug. Reverting the original status.
The identical issue has been reported against 5.5.18, which has the fix for this bug included. So it cannot be a duplicate of bug #705688. Or bug #705688 has not been really fixed in 5.5.18. This should be clarified before changing the status of this bug. Reverting the original status.