Comment # 6 on bug 1042873 from Peter S�tterlin

(In reply to Max Staudt from comment #5)
> It's really strange that these problems would occur with the compositor
> *disabled*, but not with it enabled. It sounds like a Mesa issue, but then
> it would occur with the intel driver, too. So it may really be an X server
> issue...?

Not sure - maybe a caching/redrawing issue?

> In any case, does this still occur on an up to date Tumbleweed system? We've
> updated the X server, too.

IIRC the default has been switched to intel, which I am using now, without
issues.  I can try to switch to kmodesetting and have a look (just have to find
how to override intel...)