Am I the only one getting video corruption of Qt4-based windows? It seems to only occur when something is drawn "the first time". For instance, in KDE4, right-clicking the desktop for the first time after login will invoke it. As will opening System Settings for the first time, etc.
The window outline will first appear but with its contents filled with a mix of black and other colors, as well as jagged lines. It strikes me as if it's drawing content from old video memory, long since having degenerated into a garbled mess. I've tried disabling effects (such as windows fading in), but to no effect.
It's *particularly* easy to reproduce if you're running KDE4 (perhaps 4.1b1). Right-click the new kmenu, choose 'old style menu' (or something along those lines), and quickly scroll through some of the sections. If you're getting the same as I am, there'll be some furious flashing going on.
I've had this on both my laptop with an Nvidia card (running the proprietary driver), as well as on this system with an integrated Intel 865G chipset (running the open intel driver). I also heard a bird mentioning his proprietary ATI driver exhibited the same problem, so it would seem unrelated to drivers.
Anyone else getting this? It's frustrating.
The window outline will first appear but with its contents filled with a mix of black and other colors, as well as jagged lines. It strikes me as if it's drawing content from old video memory, long since having degenerated into a garbled mess. I've tried disabling effects (such as windows fading in), but to no effect.
It's *particularly* easy to reproduce if you're running KDE4 (perhaps 4.1b1). Right-click the new kmenu, choose 'old style menu' (or something along those lines), and quickly scroll through some of the sections. If you're getting the same as I am, there'll be some furious flashing going on.
I've had this on both my laptop with an Nvidia card (running the proprietary driver), as well as on this system with an integrated Intel 865G chipset (running the open intel driver). I also heard a bird mentioning his proprietary ATI driver exhibited the same problem, so it would seem unrelated to drivers.
Anyone else getting this? It's frustrating.
Comment