Activity log for bug #201342

Date Who What changed Old value New value Message
2008-03-12 09:28:45 litemotiv bug added bug
2008-03-12 15:56:03 Travis Watkins compiz: importance Undecided Wishlist
2008-03-12 15:56:03 Travis Watkins compiz: status New Confirmed
2008-03-12 15:56:03 Travis Watkins compiz: milestone later
2009-06-15 04:53:19 Robert Ancell compiz (Ubuntu): importance Wishlist Low
2009-06-15 04:53:19 Robert Ancell compiz (Ubuntu): status Confirmed Triaged
2009-06-15 04:53:41 Robert Ancell summary Compiz uses single refreshrate with separate X screens Uses single refreshrate with separate X screens
2009-06-15 04:53:47 Robert Ancell summary Uses single refreshrate with separate X screens Uses single refreshrate for separate X screens
2009-06-19 13:03:31 PsYcHoK9 removed subscriber PsYcHoK9
2009-11-10 15:59:23 ChrT compiz (Ubuntu): status Triaged Confirmed
2009-11-11 01:57:42 Travis Watkins compiz (Ubuntu): status Confirmed Triaged
2010-06-05 11:52:52 Gordon nominated for series Ubuntu Maverick
2011-10-03 06:40:01 Daniel van Vugt summary Uses single refreshrate for separate X screens Tearing on secondary monitors even when "Sync To VBlank" is turned on.
2011-10-03 06:49:37 Daniel van Vugt bug added subscriber Daniel van Vugt
2011-10-31 06:46:35 Daniel van Vugt description Binary package hint: compiz When using 2 separate X screens with Vsync on, Compiz should honor each screen's refreshrate independently. Instead it pushes a single refresh, causing tearing on one of the screens when both screens are not in perfect sync. Ubuntu Hardy compiz-core 1:0.7.2-0ubuntu1 Dell XPS M1330 laptop (Intel Core2Duo T7500, 2GB ram, Nvidia 8400M GS, internal monitor and external Dell 2405FPW) Steps to reproduce: 1) Use a dual-monitor setup with 2 separate X screens 2) Start Compiz with Vsync enabled 3) Move a window around both screens You will find that screen 0 shows no sign of tearing, screen 1 will show a single large tearline running down the screen, timed at the clock difference between both screens. A bit more information taken from a post to Nvidia corp.: [question] i have a twinview setup with 2 lcd's: nvidia-settings says screen 1 has a 59.99hz refreshrate, screen 2 has 59.95hz. as a result, with vsync on (without is undoable), one of the screens always has one major tearline running down very slowly. the other one is smooth. depending on which screen i make primary, the other one starts to tear. so i guess that sort of makes sense, as the screens are slightly out of sync, but isnt there a way to make both screen vsync correctly? i tried running 2 separate x screens but that doesnt seem to be the solution (compiz is still only using 1 global refreshrate). [answer] In TwinView, there's only one video memory surface for the screen, so it's only possible to sync to one or the other. To sync to both at the same time, you'd need to wait for the refreshes to line up again, which happens every 1/(59.99 Hz - 59.95 Hz) = 25 seconds = unacceptable. One thing you could try is to use identical mode timings for both screens, if your display devices can handle it. With two separate X screens, you can swap each one independently so you should be able to get tear-free swaps on both screens. If Compiz can't do it, that sounds like a bug in Compiz. -AaronP, Nvidia Corporation. Binary package hint: compiz When using 2 separate X screens with Vsync on, Compiz should honor each screen's refreshrate independently. Instead it pushes a single refresh, causing tearing on one of the screens when both screens are not in perfect sync. Ubuntu Hardy compiz-core 1:0.7.2-0ubuntu1 Dell XPS M1330 laptop (Intel Core2Duo T7500, 2GB ram, Nvidia 8400M GS, internal monitor and external Dell 2405FPW) WORKAROUND: Enable "Force full screen redraws (buffer swap) on repaint" in the Workarounds section of CCSM. If you don't have ccsm installed, you can get it by installing package "compizconfig-settings-manager". TEST CASE: 1) Use a dual-monitor setup with 2 separate X screens 2) Start Compiz with Vsync enabled 3) Move a window around both screens You will find that screen 0 shows no sign of tearing, screen 1 will show a single large tearline running down the screen, timed at the clock difference between both screens. A bit more information taken from a post to Nvidia corp.: [question] i have a twinview setup with 2 lcd's: nvidia-settings says screen 1 has a 59.99hz refreshrate, screen 2 has 59.95hz. as a result, with vsync on (without is undoable), one of the screens always has one major tearline running down very slowly. the other one is smooth. depending on which screen i make primary, the other one starts to tear. so i guess that sort of makes sense, as the screens are slightly out of sync, but isnt there a way to make both screen vsync correctly? i tried running 2 separate x screens but that doesnt seem to be the solution (compiz is still only using 1 global refreshrate). [answer] In TwinView, there's only one video memory surface for the screen, so it's only possible to sync to one or the other. To sync to both at the same time, you'd need to wait for the refreshes to line up again, which happens every 1/(59.99 Hz - 59.95 Hz) = 25 seconds = unacceptable. One thing you could try is to use identical mode timings for both screens, if your display devices can handle it. With two separate X screens, you can swap each one independently so you should be able to get tear-free swaps on both screens. If Compiz can't do it, that sounds like a bug in Compiz. -AaronP, Nvidia Corporation.
2011-10-31 16:02:11 Curtis Gedak bug added subscriber Curtis Gedak
2011-11-14 18:12:11 Owais Lone bug added subscriber Owais Lone
2012-08-21 07:01:53 Daniel van Vugt bug task added compiz
2012-08-21 07:02:59 Daniel van Vugt branch linked lp:~compiz-linaro-team/compiz/gles2
2012-08-21 07:04:20 Daniel van Vugt compiz: status New In Progress
2012-08-21 07:04:32 Daniel van Vugt compiz: assignee Compiz Linaro Team (compiz-linaro-team)
2012-08-21 07:05:09 Daniel van Vugt compiz: importance Undecided Low
2012-08-21 07:05:13 Daniel van Vugt compiz: milestone 0.9.8.0
2012-08-23 02:11:43 Daniel van Vugt compiz: status In Progress Fix Committed
2012-08-23 02:14:58 Daniel van Vugt bug task added ubutter
2012-08-23 02:16:27 Daniel van Vugt ubutter: status New Fix Committed
2012-08-23 02:16:36 Daniel van Vugt ubutter: importance Undecided Low
2012-08-27 08:17:11 Daniel van Vugt compiz: status Fix Committed Fix Released
2012-09-01 15:23:09 Launchpad Janitor compiz (Ubuntu): status Triaged Fix Released
2012-09-20 06:52:10 Daniel van Vugt ubutter: status Fix Committed Fix Released