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 1202424 - Custom mode id not set properly
Summary: Custom mode id not set properly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-qxl-xddm
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: David Blechter
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-16 15:08 UTC by Sandy Stutsman
Modified: 2019-10-10 13:54 UTC (History)
17 users (show)

Fixed In Version: qxl-win-unsigned-0.1-24
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-20 01:25:26 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sandy Stutsman 2015-03-16 15:08:46 UTC
Description of problem:
When adding two entries for custom modes in the Windows QXL driver, the mode id's could be set to values that duplicate existing modes.

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

How reproducible:
Always

Steps to Reproduce:
1. In the Windows QXL driver, when appending 2 entries to hold the custom resolution, the id's are set to the index values of the entries.  But because the mode id's the list may not be consecutive (though always increasing), the index may be less that the maximum mode id passed from QEMU. The could lead to the custom id's duplicating id already in the list. 
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Sandy Stutsman 2015-06-08 13:21:52 UTC
Assigned to the qxl driver

Comment 3 Sandy Stutsman 2015-06-08 13:25:38 UTC
Assigned to the qxl driver

Comment 4 Yaniv Kaul 2015-10-18 10:43:09 UTC
Sandy, is the bug stuck on MODIFIED? Where and when is the code available for testing?

Comment 5 David Blechter 2015-10-18 11:46:03 UTC
(In reply to Yaniv Kaul from comment #4)
> Sandy, is the bug stuck on MODIFIED? Where and when is the code available
> for testing?

QA ack is missing, and we are still working on the driver

Comment 6 Sandy Stutsman 2015-10-19 16:10:10 UTC
In the meantime the updated code is here, http://git.app.eng.bos.redhat.com/git/spice/win/qxl.git/

Comment 9 Sandy Stutsman 2015-11-30 14:26:25 UTC
I found this stepping through the code and via an actual bug.  So the change is more a safe guard against it happening in the future.  I didn't find a good way to test it other than stepping through the code.

Comment 16 David Blechter 2019-10-10 13:54:09 UTC
moving from RHEVM product to RHEL 8


Note You need to log in before you can comment on or make changes to this bug.