Bug 1684739

Summary:	Screen Rotation with scaling leaves behind "ghost" cursor
Product:	Red Hat Enterprise Linux 8	Reporter:	Porygon <jsolomon>
Component:	mutter	Assignee:	Jonas Ådahl <jadahl>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	fmuellner, jadahl
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-01 07:37:34 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-02 01:29:57 UTC

Version-Release number of selected component (if applicable):
RHEL-8.0.0-20190228.1 (RC-1.0)

Steps to Reproduce: 
 1. Start gnome-shell with Wayland
 2. Open a terminal
 3. Open Settings -> Devices -> Displays
 4. Set scale to 200% or more
 5. Set orientation to something other than current orientation


Actual results: 

 Screen rotates properly, regular cursor changes orientation and is still usable, but a cloned "ghost" cursor sits on the screen.

Expected results:
 Screen should be rotated with no visual artifacts

Additional Details:
Fiji Radeon R9 FURY/NANO Series (rev ca) GPU

Comment 1 Jonas Ådahl 2019-03-02 10:24:48 UTC

Please provide package version for mutter.

Comment 2 Porygon 2019-03-06 23:19:54 UTC

Sorry I missed that, package version is mutter-3.28.3-18.el8.x86_64

Comment 3 Jonas Ådahl 2019-10-28 08:55:49 UTC

Potential fix could be https://gitlab.gnome.org/GNOME/mutter/merge_requests/59.

Comment 4 Jonas Ådahl 2019-10-28 09:06:50 UTC

Said fix is included in GNOME 3.30. RHEL 8.1 includes GNOME 3.32. Could you verify the issue is gone on RHEL 8.1?

Comment 8 RHEL Program Management 2021-02-01 07:37:34 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.