Comment # 19 on bug 974627 from Ludwig Nussel

Guys, this is not an easy problem. Max already spent days on debugging and
bisecting this without conclusion. So even if you don't think your area if
responsibility is to blame your experience in debugging strange X quirks would
be very valuable. At this point it is still unclear whether the problem is
actually due to qt doing something wrong. Maybe it' s a behavior change that
suddenly uncovers a bug elsewhere. Maybe is a coincidental combination of qt,
X, YaST and icewm. Any help to shed light on this case appreciated.