Created attachment 434760 [details]
Screenshot of corruption that doesn't refresh
Description of problem:
When using a scroll wheel to move a page up and down, the screen doesn't refresh when another window is in front and has the focus.
Version-Release number of selected component (if applicable): RHEL 6.0 snap8
How reproducible: reliably
Steps to Reproduce:
1. Open up TCMS in Firefox.
2. Put the open window in front of the TCMS window.
3. Hover over TCMS window and use scroll wheel on mouse to traverse up and down.
Actual results: TCMS window has corrupted table rows and doesn't refresh unless you hover over them with the mouse cursor.
Expected results: Screen would refresh without corruption
[bsanford@dhcp70-187 Desktop]$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
Created attachment 434762 [details]
The only corruption that is seen with the table rows in TCMS are covered by the window that is in focus.
I used TCMS as an example to a Firefox issue. You can use Bugzilla in Firefox or load a Firefox web page and the corruption will still have the same behavior.
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
What versions of firefox and xulrunner is this with?
Firefox version I am using is 3.6.7 and Mozilla XULRunner 184.108.40.206 - 20100714041006.
Is this still happening with the latest updates (i.e., snap11)?
Thank you for your bug report. This issue was evaluated for inclusion
in the current release of Red Hat Enterprise Linux. Unfortunately, we
are unable to address this request in the current release. Because we
are in the final stage of Red Hat Enterprise Linux 6 development, only
significant, release-blocking issues involving serious regressions and
data corruption can be considered.
If you believe this issue meets the release blocking criteria as
defined and communicated to you by your Red Hat Support representative,
please ask your representative to file this issue as a blocker for the
current release. Otherwise, ask that it be evaluated for inclusion in
the next minor release of Red Hat Enterprise Linux.
(In reply to comment #8)
> Is this still happening with the latest updates (i.e., snap11)?
bsanford: I am seeing it still and I believe I have 822.0 installed - the kernel is 2.6.32-66.el6.x86_64
In the end, I think these logs would be helpful. Please add drm.debug=0x04 to the kernel command line, restart computer, and attach
* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)
to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 442164 [details]
(In reply to comment #11)
> In the end, I think these logs would be helpful. Please add drm.debug=0x04 to
> the kernel command line, restart computer, and attach
> * your X server config file (/etc/X11/xorg.conf, if available),
> * X server log file (/var/log/Xorg.*.log)
Created attachment 442165 [details]
(In reply to comment #11)
> * output of the dmesg command, and
Created attachment 442166 [details]
(In reply to comment #11)
> * system log (/var/log/messages)
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
This request was erroneously denied for the current release of
Red Hat Enterprise Linux. The error has been fixed and this
request has been re-proposed for the current release.
Matej, I don't have the logs of that machine anymore.
Move to 6.3.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: