Are you still able to reproduce this bug with the latest packages (eg. 4:4.2.2-1)? I can't reproduce this problem here but it might be related to your display driver as well.