Description of problem: When playing back HTML5 video (generally YouTube) in full-screen mode with Haswell integrated graphics: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) there is visual tearing happening. Version-Release number of selected component (if applicable): firefox-35.0.1-5.fc21.x86_64 How reproducible: Every time Steps to Reproduce: 1. Ensure HTML5 mode is enabled on YouTube: https://www.youtube.com/html5 2. Play this video: https://www.youtube.com/watch?v=5xkNy9gfKOg 3. Switch to full-screen mode Actual results: Visible tearing (breaks in vertical lines) Expected results: No tearing Additional info: The tearing doesn't seem to happen if the same video file is downloaded and then played back full screen in another player such as totem. Also, the tearing doesn't seem to happen in non-full-screen mode in the browser.
Can you please test a firefox binary from mozilla.com?
Yes, a Firefox 35.0.1 binary from mozilla.com appears to have the same issue. Strangely enough, I noticed that sometimes, for the first few seconds of full-screen playback, it's basically fine. Then a few seconds after the seek bar and title bar disappear, suddenly it starts tearing. It's like there's a transition between two modes happening and the second mode is the one that has problems. Though, other times you can go to full screen and it shows tearing immediately.
It would be good to report that at https://bugzilla.mozilla.org/ while we're not going to fix that for Fedora only.
Filed in bugzilla.mozilla.org as bug 1134077.
Thanks!
So after looking into this a bit more, it sounds like mutter (the GNOME3 compositor) has a heuristic that it uses to detect when it should unredirect the window. From https://github.com/ValveSoftware/steam-for-linux/issues/2163: "GNOME 3 automatically unredirects some full-screen windows. Games (or SDL2) don't set the recently added _NET_WM_BYPASS_COMPOSITOR hint, so we fall back to heuristics: a non-ARGB32 full-screen / monitor-sized window that does 100 full-screen redraws in a row. If that happens, then the window should be unredirected." When you open a full-screen video for the first time after opening the browser, after a few seconds (probably when 100 frames have been played), suddenly the video starts tearing. If you hit the Windows key to open the overview, which zooms down the video into a frame (presumably forcing it to be redirected again), the tearing stops. When you hit the key again to go back to full screen, it starts tearing again immediately. Sure enough, if you disable unredirection as described here: https://bugzilla.gnome.org/show_bug.cgi?id=741376#c15 the tearing goes away. From what I'm reading, it sounds like the application ends up being responsible for handling vsync to avoid tearing when it's not redirected through the compositor. (I saw a bunch of reports of tearing on Ubuntu with Compiz when the "unredirect full screen" option was turned on.) If that's true and Firefox isn't doing this, then I'm assuming either that needs to be fixed or unredirection should be disabled for it.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still occurring in Fedora 23. It appears that Cinnamon is currently disabling unredirection for full-screen applications by default because of such issues: https://github.com/linuxmint/muffin/commit/d2c9701b673eea9028f4167523ba9775987928ed
Happens on F24 also
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.