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 1204610

Summary: Tearing with external monitors on i915 driver
Product: Red Hat Enterprise Linux 7 Reporter: adam winberg <adam.winberg>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: adam.winberg, moizerweb, pasteur, tfolinux, tpelka
Target Milestone: rcKeywords: OtherQA
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-15 07:33:43 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 adam winberg 2015-03-23 07:16:40 UTC
Description of problem:
After upgrading to 7.1, tearing started to appear when our HP laptops/desktops with Intel i915 driver are connected to external monitors. It does not always show, but most of the time, specially when toggling the notification area (Super+M) or starting the Activities screen (Super). Using the laptop screen as a third monitor seems to make the problem worse.


Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.99.916-5.el7.x86_64

How reproducible:
Intermittently

Steps to Reproduce:
1. Use two external monitors
2. Toggle notification area
3.

Actual results:
Screen flickering and tearing

Expected results:
No tearing.

Additional info:

Creating an xorg config with 'TearFree' option, like this:
/etc/X11/xorg.conf.d/20-intel.conf:
Section "Device"
   Identifier  "Intel Graphics"
   Driver      "intel"
   Option      "AccelMethod"  "sna"
   Option      "TearFree" "true"
EndSection

solves the problem. Should not be needed though.

Comment 2 Tomas Pelka 2015-05-13 06:11:58 UTC
Adam,

we wasn't able to reproduce but would you be able to test the fixed package once available?

Thanks
-Tom

Comment 3 adam winberg 2015-05-13 06:21:48 UTC
Yes, sure.

Comment 5 elenageorge 2018-10-22 07:29:26 UTC
Many users are facing this issues with Intel graphics card c=screen tearing. I was facing this after updating an Ubuntu 15.10, however reverting some information at https://www.hpsupporthelpline.com/ it was solved.

Comment 7 RHEL Program Management 2020-12-15 07:33:43 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.