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 1105633

Summary: qt applications crash with SIGSEGV when run under VM with cirrus driver
Product: Red Hat Enterprise Linux 6 Reporter: Todd Allen <redhatbugzilla>
Component: qtAssignee: Jan Grulich <jgrulich>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5CC: rvokal, 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:01:09 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
patch that fixes the problem (backported from 4.8.0-0.23.rc1
none
simple example program none

Description Todd Allen 2014-06-06 15:25:27 UTC
Created attachment 902956 [details]
patch that fixes the problem (backported from 4.8.0-0.23.rc1

Description of problem:
Do this under a VNC console using the cirrus driver.  (This is the default configuration with older qemu/virt-manager.)
Built a simple Qt application using qt-4.6.2-28.el6_5.  (I'll attach a simple example.)  Run it.  It dies with SIGSEGV.  If you use the same X11 session but run the application remotely so that it is not a local display, it avoids the SIGSEGV, but the display is stretched by 4/3 with striped colors.

Version-Release number of selected component (if applicable):
4.6.2-28.el6_5

How reproducible:
Always

Steps to Reproduce:
1. qmake
2. make
3. ./it

Actual results:
SIGSEGV (or, from a remote system, strange window)

Expected results:
A window with a single button that does nothing.

Additional info:
This bug does not happen with 4.6.2-26.el6_5.  It was introduced in 28.el6_5 because of the change of default graphicssystem to raster.

This bug existed in qt-4.8.0-0.23.rc1.fc16.  See bug 749647.  It also has been reported as QTBUG-21754: https://bugreports.qt-project.org/browse/QTBUG-21754.

To verify that this was the same bug as those two, I did the trivial backport to 4.6.2-28 of the patch in qt-4.8.0-0.23.rc1.fc16.  It fixes both the SIGSEGV and the strange display.  I'll attach that patch.

Comment 1 Todd Allen 2014-06-06 15:27:24 UTC
Created attachment 902957 [details]
simple example program

Comment 4 Than Ngo 2014-11-04 17:19:45 UTC
(In reply to Todd Allen from comment #1)
> Created attachment 902957 [details]
> simple example program

Thanks for the testcase, i can reproduce this crash.

Comment 5 Jan Grulich 2015-06-02 13:45:25 UTC
It's too late for RHEL 6.7, but we can try to include this in RHEL 6.8.

Comment 7 Jan Kurik 2017-12-06 11:01:09 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/