Created attachment 65347 [details] Image disorted by scrolling Version: unspecified OS: Linux When i do vertical scrolling (using mousewheel, keup/keydown, pgup/pgdown) the content of scrolled window becomes disorted and unreadable (see attachment). I have reproduced this in allmost any application, which uses vertically scrolled windows (ie Eclipse, Opera, Wireshark and others). The problem disappears when I turn off desktop effects. Reproducible: Always Steps to Reproduce: Do few up and down scrolls in some app (ie Eclipse, Opera, Wireshark). Actual Results: Image becomes disorted. Expected Results: Image not being disorted :-)
None of the applications you mentioned are KDE applications. Is the bug also visible with KDE applications?
Yes, I have been able to reproduce this bug in Amarok (middle column showing wiki, lyrics), Kate, Konqueror, Kopete (chat window). Minimizing and maximizing the app clears the image, until I scroll again. Also, when I reboot system, everything works fine for a while (5 minutes to several hours), but then every app starts to break again.
Please add the following information: - KDE version - video driver type and version - output from running "kwin --replace &" in Konsole if possible
KDE version 4.7.2 Ndvidia driver: NVRM version: NVIDIA UNIX x86_64 Kernel Module 173.14.30 Sat Apr 16 21:49:29 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro NVS 135M/PCI/SSE2 OpenGL version string: 2.1.2 NVIDIA 173.14.30 OpenGL shading language version string: 1.20 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 173.14.30 GPU class: Unknown OpenGL version: 2.1.2 GLSL version: 1.20 X server version: 1.10.4 Linux kernel version: 3.0 Direct rendering: yes Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes
Can you please attach you /etc/X11/xorg.conf?
Here it is: Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" Option "Xinerama" "0" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" # HorizSync source: edid, VertRefresh source: edid Identifier "Monitor0" VendorName "Unknown" ModelName "Chi Mei Optoelectronics corp." HorizSync 30.0 - 75.0 VertRefresh 60.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "Quadro NVS 135M" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 Option "TwinView" "1" Option "TwinViewXineramaInfoOrder" "DFP-0" Option "metamodes" "DFP-0: nvidia-auto-select +0+0, DFP-1: nvidia-auto-select +1280+0" SubSection "Display" Depth 24 EndSubSection EndSection
I dare to say it is an NVIDIA issue. You could try to disable OpenGL shaders in the advanced compositing settings.
it's the legacy one. however i errrr "scheduled" to mention to add Option "DamageEvents""true" Option "BackingStore" "true" to the device section - be carefull with the second. It might improve twinview performance but also cause freezes (and i neither know about that chip nor driver version) You can also experiment with Option "OnVBlankDemandInterrupts" "true"/"false" It's a powersaving feature which might be related (true is the powersaving mode)