According to debbugs #434180 the bug was really in libx11, which has been fixed already. Therefor closing this bug.
According to debbugs #434180 the bug was really in libx11, which has been fixed already. Therefor closing this bug.