Did some further tests and it seems to me that it is this issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814959 I'll continue watching and commenting on that one then. Spoiler: Switching to TigerVNC is a workaround for me for now (vnc4server / "RealVNC" seems to have the same issue as TightVNC).