Also the bug was wrongly moved to incomplete in release 5.1. Actually the fix is committed there and no problems were observed so far.
Also the bug was wrongly moved to incomplete in release 5.1. Actually the fix is committed there and no problems were observed so far.