Bug 1258842

Summary:	Backport mutter fixes from mutter 3.17.90 to mutter 3.14.4 ( RHEL 7.2 workstation )
Product:	Red Hat Enterprise Linux 7	Reporter:	jigar <jraising>
Component:	mutter	Assignee:	Florian Müllner <fmuellner>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	fmuellner, jcking, justin.garrison, kcleveng, mclasen, tpelka, vbenes
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	mutter-3.14.4-11	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 07:20:46 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 jigar 2015-09-01 11:58:26 UTC

Description of problem: Screen flickering/flashing as described here https://bugzilla.gnome.org/show_bug.cgi?id=728464 . The issue occurs in gnome-shell with NVIDIA drivers. It is reproducible in firefox, files, terminal.


Version-Release number of selected component (if applicable): 3.14.4

How reproducible: Frequently

The following patches need to be backported to mutter-3.14.4 from upstream:

https://bug728464.bugzilla-attachments.gnome.org/attachment.cgi?id=276413 

https://bug728464.bugzilla-attachments.gnome.org/attachment.cgi?id=298718

https://bug728464.bugzilla-attachments.gnome.org/attachment.cgi?id=308756

https://bug728464.bugzilla-attachments.gnome.org/attachment.cgi?id=308790

https://bug728464.bugzilla-attachments.gnome.org/attachment.cgi?id=309156


Actual results: Screen flickers in mutter when using NVIDA drivers.


Expected results: Screen should not flicker. 


Additional info: The backport is needed before the RHEL 7.2 ga comes out.

Comment 4 Rui Matos 2015-10-14 12:27:07 UTC

*** Bug 1270532 has been marked as a duplicate of this bug. ***

Comment 8 errata-xmlrpc 2015-11-19 07:20:46 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://rhn.redhat.com/errata/RHBA-2015-2216.html