After upgrading from Fedora 34 to Fedora 35, without changing anything in the hardware setup, I started seeing weird "screen tearing" artifacts - e.g., when I move the mouse over a menu and the shaded item changes, the shade doesn't just move at once but for a visible fraction of a second I see some scan lines with the old color and scan lines with the new colors. I did a few experiments and noticed that: 1. The problem is just with X11 - with Wayland it doesn't happen. 2. In X11 the problem appears to happen - and is very visible - in specific applications such as telegram-desktop and wine, but I couldn't reproduce it in other applications. 3. It seems that certain window managers somehow makes the system immune to this problem. I had the problems when I was using the ctwm window manager, but couldn't reproduce it with the default Gnome window manager. According to my $HOME//.local/share/xorg/Xorg.0.log, my X driver is intel_drv.so, compiled for 1.20.11, module version = 2.99.917 and the actual chipset is "Integrated Graphics Chipset: Intel(R) HD Graphics 4600" It turns out that this is a known bug in the Intel driver, described in https://linuxreviews.org/HOWTO_fix_screen_tearing. That page mentions a fix, which I tried, and worked perfectly! The fix is to create a file /etc/X11/xorg.conf.d/20-intel-gpu.conf with the content: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "true" EndSection With that, after restarting X, the tearing problems are completely gone. I couldn't find any negative side-effects, although the output of https://www.vsynctester.com/ isn't great. The line [ 49490.737] (**) intel(0): TearFree enabled Now appears in Xorg.0.log. I think that maybe this option should be made the default, because whatever the negative side-effects of this option are, without it many applications look absolutely terrible. In any case, I think it won't affect most Fedora users (who use Wayland by default) but those who need it, will have a really hard time figuring out how to fix it (I was really lucky to find the aforementioned linuxreviews.org page - at first, I didn't even know how to call the ugly artifacts I was seeing). What I really don't understand, though, is how did I only start seeing this issue now, when upgrading to Fedora 35. I have been using the same hardware, and the same window manager (ctwm), for several years now - and have never had these problems ever. So what changed in Fedora 35 regarding the Intel driver?
I am also experiencing this issue, and can confirm the workaround does fix the tearing. However, numerous applications using the GPU stop working with this option enabled: glxgears, vkcube, kitty (terminal emulator) all fail to redraw when this option is enabled. Either the first frame is displayed and frozen, or just a black frame.
I confirm this issue, options TearFree or TripleBuffer on "true" fixing the tearing, but steam, battle.net, glxgears does't work (vkcube works). I was upgrade Fedora 33 by F34 to F35. My laptop have i7-4710HQ with i915 and GeForce GTX 860M.
Hi, I got (apart of others) this same problem but I am not sure about trying this workaround. Any help? I would appreciate it. The output I got for "$grep drivers /var/log/Xorg.0.log" is: ``` [ 33.270] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 33.292] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 33.296] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so ```
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.