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 1045171

Summary: Drawing problem with 24 bits per pixel
Product: Red Hat Enterprise Linux 6 Reporter: Matrox <mgi_lnx>
Component: xorg-x11-serverAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5CC: mgi_lnx, tpelka
Target Milestone: rc   
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: 2017-12-06 11:21:02 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:
Attachments:
Description Flags
Picture of the corruption none

Description Matrox 2013-12-19 19:12:01 UTC
Description of problem:

If the number of bits per pixel is 24, artifacts are seen on the screen. The problem goes away if we set 32 bpp or 16 bpp.


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


How reproducible:

Reproduced consistently on a G200se


Steps to Reproduce:
1.Boot with a G200se
2.Open System Monitor
3.The windows isn't displayed properly

Actual results:

Grey area beside the window.

Expected results:

A well drawn window.

Additional info:

Comment 1 Matrox 2013-12-19 19:12:53 UTC
Created attachment 839212 [details]
Picture of the corruption

Comment 3 Tomas Pelka 2014-11-21 12:32:20 UTC
(In reply to Matrox from comment #0)
> Description of problem:
> 
> If the number of bits per pixel is 24, artifacts are seen on the screen. The
> problem goes away if we set 32 bpp or 16 bpp.
> 
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> 
> Reproduced consistently on a G200se
> 
> 
> Steps to Reproduce:
> 1.Boot with a G200se
> 2.Open System Monitor
> 3.The windows isn't displayed properly
> 
> Actual results:
> 
> Grey area beside the window.
> 
> Expected results:
> 
> A well drawn window.
> 
> Additional info:

Hi could you please retry with 6.6,we did the rebase of Xorg in 6.6.

If that failed again would you be able to test in fixed packages once available?

Thanks
Tom

Comment 4 Matrox 2014-12-04 15:13:35 UTC
RedHat 6.6 was tried and the default depth was found to always be 16bpp.  While different configurations of the xorg.conf file were attempted, the default depth could not be changed.  Since the default depth could not be set to 24bpp, the issue was not replicated.

Was this the intended solution?  Because as it stands, our clients will not be satisfied if they cannot set the depth to 24bpp.

Comment 7 Jan Kurik 2017-12-06 11:21:02 UTC
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:

http://redhat.com/rhel/lifecycle

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:

https://access.redhat.com/