Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1165840

Summary: Gnome Inefficient Dirty Pixel Update
Product: Red Hat Enterprise Linux 7 Reporter: Matrox <mgi_lnx>
Component: mutterAssignee: Florian Müllner <fmuellner>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: ajax, ayadav, fmuellner, jraising, mclasen, mgi_lnx, rstrode, tpelka, vchoudha
Target Milestone: rcKeywords: OtherQA
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 01:40:22 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:
Bug Depends On:    
Bug Blocks: 1203710, 1297830, 1313485    
Attachments:
Description Flags
dmesg dirty pixel block output for both KDE & Gnome
none
dmesg dirty pixel block output for both KDE & Gnome w/ updated cogl rpms none

Description Matrox 2014-11-19 19:56:19 UTC
Created attachment 959117 [details]
dmesg dirty pixel block output for both KDE & Gnome

When a portion of the screen needs to be updated, instead of simply updating the dirty pixels, the entire screen is being redrawn.  After tracing this from the kernel up to the xorg driver, this inefficiency can be attributed to the data being received by the xorg driver from the drm.  This data has not been optimized.  This yields unnecessary screen updates resulting in a slower user experience.

I have attached the dirty pixel output, for a blinking cursor in a terminal, in both Gnome and KDE.  It is clear that in KDE, the data being passed to the xorg driver has been optimized, while in Gnome it has not.

Version-Release number of selected component (if applicable):
Seen testing RHEL 7 with kernel 3.10.0-123.el7.x86_64

Look at the data being processed in xorg modesetting driver function dispatch_dirty_region to see this problem.

Comment 3 Ray Strode [halfline] 2014-11-20 13:53:50 UTC
Hi,

Thank you for the bug report and analysis.  It's quite helpful.

Would you mind testing these cogl packages:

http://people.redhat.com/rstrode/1165840/

and report whether or not they resolve your issue?

Comment 4 Matrox 2014-11-27 20:36:43 UTC
Created attachment 962250 [details]
dmesg dirty pixel block output for both KDE & Gnome w/ updated cogl rpms

Comment 5 Matrox 2014-11-27 20:42:15 UTC
After installing the suggested cogl packages,  I noticed that now the application window is being updated, in the even of a blinking cursor, instead of the whole screen.  See the newly attached file for the new dirty pixel block data.

Comment 13 Tomas Pelka 2016-02-10 19:03:30 UTC
Hi Matrox,

may I ask you for commit a testing on fixed package(s)?

Thanks
-Tom

Comment 14 Matrox 2016-02-10 19:25:55 UTC
Hi Tom,

Matrox is ready to test a proposed fix.  Please send us the link for the package (s) to test.

Thanks

Comment 15 Tomas Pelka 2016-02-22 12:56:17 UTC
(In reply to Matrox from comment #14)
> Hi Tom,
> 
> Matrox is ready to test a proposed fix.  Please send us the link for the
> package (s) to test.
> 
> Thanks

I will once it is ready.

Thanks
-Tom

Comment 20 Tomas Pelka 2016-09-02 11:17:52 UTC
(In reply to Tomas Pelka from comment #15)
> (In reply to Matrox from comment #14)
> > Hi Tom,
> > 
> > Matrox is ready to test a proposed fix.  Please send us the link for the
> > package (s) to test.
> > 
> > Thanks
> 
> I will once it is ready.
> 
> Thanks
> -Tom

Hi Matrox,

RHEL7.3 Beta should be available, would you please check if this issue is fixed for you?

Comment 21 Matrox 2016-09-12 15:04:56 UTC
Currently under test

Comment 23 Matrox 2016-09-22 19:09:56 UTC
We have been able to verify that the fix is indeed fixed.

We found another issue while testing this, I'm collecting information and will open a new bug.

Comment 24 Tomas Pelka 2016-09-22 19:13:11 UTC
(In reply to Matrox from comment #23)
> We have been able to verify that the fix is indeed fixed.
> 
> We found another issue while testing this, I'm collecting information and
> will open a new bug.

Thank you, please add the new bug to depends field (if it is available for you)

Comment 26 errata-xmlrpc 2016-11-04 01:40:22 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-2016-2258.html