Tearing in chromium-browser video playback on xubuntu 18.04 (NVIDIA)

[Jarno Suni]

Test video:
https://youtu.be/22ftfoCSPQI
Tested in chromium-browser with setting "Use hardware acceleration when available".

Oh, when I use google-chrome, instead, there is no such tearing.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
BootLog: root: clean, 338350/1038352 files, 2274396/4150016 blocks
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Sun Jul 22 08:53:00 2018
DistUpgraded: 2018-04-14 11:02:07,544 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-45-generic, x86_64: installed
 bbswitch, 0.8, 4.15.0-29-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-128-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-130-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:853b]
InstallationDate: Installed on 2014-09-21 (1399 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1)
MachineType: Dell Inc. OptiPlex 745
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=d012c1bd-7e56-4035-b321-38d20cb14421 ro
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2018-04-14 (98 days ago)
dmi.bios.date: 06/26/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.6.6
dmi.board.name: 0RF703
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 745
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun Jul 22 08:40:45 2018
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input CHESEN PS2 to USB Converter KEYBOARD, id 8
 input CHESEN PS2 to USB Converter KEYBOARD, id 9
 input Logitech USB-PS/2 Optical Mouse MOUSE, id 10
xserver.errors:
 No devices detected.
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: nouveau

[Daniel van Vugt (vanvugt)]

I am removing Xorg from this bug. If Xorg is to blame at all then it's probably already covered by one of the other existing bugs:

https://bugs.launchpad.net/ubuntu/+bugs?field.tag=tearing

[Olivier Tilloy (osomon)]

Jarno Suni, please excuse the lack of feedback on your bug report. Would you mind commenting here to let us know whether the latest chromium update presents the same problem that you originally reported? Thanks in advance.

[Jarno Suni (jarnos)]

Yes, it still happens on Xubuntu 18.04, nvidia driver, sync to vblank set in OpenGL settings in NVIDIA X Server Settings. But I expect it to be better with 19.10 (Xfce 4.14) when using compositor. Chromium Version 80.0.3987.163 (Official Build) Built on Ubuntu , running on Ubuntu 18.04 (64-bit)

[Daniel van Vugt (vanvugt)]

Is this bug just about fullscreen tearing or windowed too?

If it's just fullscreen then it should be marked as a duplicate of bug 1754284.