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...? In any case, does this still occur on an up to date Tumbleweed system? We've updated the X server, too. Sorry for not being able to answer earlier :(