I see this with games as well as on my (composited) desktop when scrolling very fast in firefox, for example. Let me try to explain: If you would cut the screen horizontally in 3 pieces the line between the middle and the down piece is where the tearing appears. It appears even with vsync. I tried to capture it with gtk-rekordmydesktop but for some reason the video is tear-free.
Please attach /var/log/Xorg.0.log and the output of dmesg.
Created attachment 90433 [details] dmesg output for DRM/radeon I'm seeing this too with a PITCAIRN chip (stack detailed below). Though the tearing (one, 27" monitor with 2560x1440, KDE 4.11, composited) appears like five ccentimeters from the top whenever there is fast movement or quick image changes. I'm not seeing this with Catalyst. (Sorry for not reporting this earlier, but I totally forgot to.) No error/warning (except not finding some cyrillic font) is logged to Xorg.0.log – do you still want to have it? Stack used: GPU: "PITCAIRN" (ChipID = 0x6819) Linux: 3.12.1 libdrm: 2.4.49-2 (Debian package) LLVM: SVN:trunk/r195435 libclc: Git:master/8e0ea3a263 Mesa: Git:master/aad2511c6d GLAMOR: Git:master/b418b13126 DDX: Git:master/d571d6af70 KWin: 4.11.3-2 (Debian package)
Created attachment 90445 [details] /var/log/Xorg.0.log As Kai said there's nothing important in Xorg.log/dmesg, I attach it anyway.
Created attachment 90446 [details] dmesg output Sorry, wrong file (just woke up).
Created attachment 90447 [details] /var/log/Xorg.0.log
Comment on attachment 90433 [details] dmesg output for DRM/radeon I think I've to withdraw my "me too". I certainly did see this in the past, but the stack I detailed in comment 2 was wrong: I wasn't add KDE 4.11.3-2 (I hadn't restarted X). Now, really on 4.11.3-2, I'm unable to reproduce the tearing. What I've seen might have been an KWin issue then. Sorry for the noise.
Well, I'm seeing this with XFCE4 and fglrx is tear-free.
Does it work better with EXA instead of glamor?
(In reply to comment #8) > Does it work better with EXA instead of glamor? No.
Your options right now are basically: * Use fullscreen apps, and make sure the compositing manager unredirects fullscreen windows. * Using an OpenGL compositing manager may help to avoid tearing with non-fullscreen apps as well. * Use EXA with Option "EXAVSync" (but read the radeon manpage about its caveats).
(In reply to Michel Dänzer from comment #10) > Your options right now are basically: > > * Use fullscreen apps, and make sure the compositing manager unredirects > fullscreen windows. > * Using an OpenGL compositing manager may help to avoid tearing with > non-fullscreen apps as well. > * Use EXA with Option "EXAVSync" (but read the radeon manpage about its > caveats). I'm now on LXQT with compton as compositor. The tearing is still there.
(In reply to Thomas Rohloff from comment #11) > I'm now on LXQT with compton as compositor. The tearing is still there. What command line parameters / configuration are you using for compton? Something like compton --backend glx --glx-swap-method 2 --unredir-if-possible works well for me. With current xf86-video-ati Git master, you can also try Option "TearFree", which should prevent tearing even without a compositing manager. Its downside is that it disables DRI page flipping ATM.
Created attachment 119001 [details] .compton.conf This is my compton config file. Tearing happens with (unredirected) fullscreen apps, too.
Added glx-swap-method = 2 to the config. Tearing still there.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/474.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.