Bug 1690170

Summary: [nvidia binary] Panning incorrectly sets boundaries and creates artifacting outside of boundaries
Product: Red Hat Enterprise Linux 8 Reporter: Porygon <jsolomon>
Component: mutterAssignee: Jonas Ådahl <jadahl>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: csoriano, fmuellner, jadahl, jkoten, tpelka
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: mutter-3.32.2-33.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:09:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Porygon 2019-03-18 23:18:26 UTC 
Version-Release number of selected component (if applicable):
libXrandr-1.5.1-7.el8.x86_64
kernel-4.18.0-74.el8.x86_64
RHEL-8.0.0-20190228.1 (RC-1.0)

Steps to Reproduce: 

1. Boot a machine running nvidia binary drivers
2. log into a gnome-shell session with Xorg
3. open a few windows, maximize one or two
4. drag non-maximized windows outside the "bounds" created by the resolution change
5. open a terminal and execute xrandr --output DP-0 --mode 640x480 --panning 1920x1080 (replace output with your actual output, mode should be some low resolution, panning should be monitor's max/native resolution)


Actual results: 

activity bar and maximized windows are aligned with the mode set resolution, panning and dragging a window outside this boundary creates flickering and artifacts.

Expected results:

maximized windows and gnome-shell elements match the defined panning resolution, user is able to pan the smaller mode set viewport around this larger area using the mouse.

Additional info:
tested on Geforce GTX 1050ti (PCI ID 10DE:1c82)
Comment 10 errata-xmlrpc 2020-04-28 16:09:06 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1766