It seems that boo#940459 and the workaround in ncurses to fix this behaviour of screen had caused this bug.