Screen tearing in Firefox fullscreen Youtube videos

Only happens with Firefox, Chromium works fine, but I don’t like to use Chromium.

Setting layers.acceleration.force-enabled = true and/or doing prime-run firefox used to fix tearing completley before the 2020-10-01 update, but ever since then neither of these option, nor both combined work anymore.

System:    Kernel: 5.8.11-1-MANJARO x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 
           root=UUID=2bcd1344-6222-4bb4-84a1-c3e46883dc32 rw "acpi_osi=Windows 2018" quiet 
           Desktop: GNOME 3.36.6 tk: GTK 3.24.23 wm: gnome-shell dm: GDM 3.36.3 Distro: Manjaro Linux 
Machine:   Type: Laptop System: ASUSTeK product: FX503VD v: 1.0 serial: <filter> 
           Mobo: ASUSTeK model: FX503VD v: 1.0 serial: <filter> UEFI: American Megatrends 
           v: FX503VD.308 date: 04/29/2019 
Battery:   ID-1: BAT1 charge: 52.2 Wh condition: 52.2/64.4 Wh (81%) volts: 5.1/15.2 
           model: ASUS A32-K55 type: Li-ion serial: N/A status: Full 
CPU:       Topology: Quad Core model: Intel Core i5-7300HQ bits: 64 type: MCP arch: Kaby Lake 
           family: 6 model-id: 9E (158) stepping: 9 microcode: D6 L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20004 
           Speed: 3160 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 3194 2: 2294 3: 3276 4: 3201 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: 
           disabled, RSB filling 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:591b 
           Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: ASUSTeK driver: nvidia v: 450.66 
           alternate: nouveau,nvidia_drm bus ID: 01:00.0 chip ID: 10de:1c8d 
           Device-3: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo bus ID: 1-7:4 
           chip ID: 13d3:5666 serial: <filter> 
           Display: x11 server: 1.20.9 compositor: gnome-shell driver: modesetting,nvidia 
           alternate: fbdev,intel,nouveau,nv,vesa resolution: <xdpyinfo missing> 
           OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.1.8 
           direct render: Yes 
Audio:     Device-1: Intel CM238 HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:a171 
           Sound Server: ALSA v: k5.8.11-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: d000 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: d000 bus ID: 04:00.0 
           chip ID: 8086:24fd 
           IF: wlp4s0 state: up mac: <filter> 
Drives:    Local Storage: total: 1.20 TiB used: 330.09 GiB (26.8%) 
           SMART Message: Required tool smartctl not installed. Check --recommends 
           ID-1: /dev/mmcblk0 vendor: Samsung model: SP64G size: 59.48 GiB block size: 
           physical: 512 B logical: 512 B serial: <filter> scheme: MBR 
           ID-2: /dev/sda vendor: A-Data model: SU800NS38 size: 238.47 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 8BS scheme: GPT 
           ID-3: /dev/sdb vendor: Seagate model: ST1000LX015-1U7172 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> 
           rev: SDM1 scheme: GPT 
Partition: ID-1: / raw size: 237.97 GiB size: 233.24 GiB (98.01%) used: 51.77 GiB (22.2%) fs: ext4 
           dev: /dev/sda2 
Swap:      Kernel: swappiness: 3 (default 60) cache pressure: 50 (default 100) 
           ID-1: swap-1 type: file size: 10.00 GiB used: 28.2 MiB (0.3%) priority: -2 file: /swapfile 
Sensors:   System Temperatures: cpu: 61.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 242 Uptime: 2h 04m Memory: 15.52 GiB used: 3.99 GiB (25.7%) Init: systemd 
           v: 246 Compilers: gcc: 10.2.0 alt: 9 clang: 10.0.1 Packages: pacman: 1362 lib: 454 
           Shell: Bash v: 5.0.18 running in: gnome-terminal inxi: 3.1.05

Any ideas?

What are your nVidia OpenGL settings?



I think it’s because I’m using hybrid graphics but I don’t get the same menus in X Server Settings


I also have same problem, looks like this problem started after firefox 81 update

1 Like

Anyone? Anything?

The 450 driver still has some issues. try the 455 in TESTING or the 440 in STABLE.

For the moment I chose to downgrade Firefox to v80 and I’ll wait until nvidia-455 reaches stable.

1 Like

Firefox 81.0.2, nvidia-455 and this problem still exists. No problems in brave and other chromium based browsers.

1 Like


Hoping Firefox 82 update fixes it.

Just installed Firefox 82 and sadly the problem persists.


I had the same problem, but they disappeared when I installed this gnome extension:
Disable unredirect fullscreen windows

If you are on gnome you might want to give it a try =)

1 Like

Welcome to Manjaro and please read this:

1 Like

Oh my God, thank you. This does work.


Thank you. This works also with my Intel 620 and mode setting driver. I’m just wondering why the tearing appears every now and then with different Firefox versions. I had this Problem about half a year ago before but it just went away with an update.

For me the tearing is gone with Firefox 83.

It disappeared for me too with Firefox 83.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.