[Ubuntu-x-swat] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

2019-12-08 Thread Matt Austin
** Attachment added: "lspci -k" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+attachment/5310908/+files/lspcik.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.

[Ubuntu-x-swat] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

2019-12-08 Thread Matt Austin
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+attachment/5310910/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.

[Ubuntu-x-swat] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

2019-12-08 Thread Daniel van Vugt
Note that tearing on all-but-one monitor in Xorg sessions is expected. It's an unfortunate feature of Xorg with DRI2. If you can convince the system to use DRI3 and TearFree then that avoids it. But that feature also doesn't exist for all graphics drivers. Please run: lspci -k > lspcik.txt

[Ubuntu-x-swat] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

2019-12-08 Thread Daniel van Vugt
** This bug is no longer a duplicate of bug 1846398 Fractional scaling has significant visible tearing in Xorg sessions -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1853094 Title:

[Ubuntu-x-swat] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock

2019-12-05 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1846398 *** https://bugs.launchpad.net/bugs/1846398 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1846398, so it is being marked as such. Please