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 1147495

Summary: Screen corruption when exceeding certain resolution
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Jamrisko <tjamrisk>
Component: xorg-x11-drv-qxlAssignee: Default Assignee for SPICE Bugs <rh-spice-bugs>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: marcandre.lureau, rbalakri
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-08 16:36:47 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
Corrupted screen none

Description Tomas Jamrisko 2014-09-29 12:09:22 UTC
Created attachment 942294 [details]
Corrupted screen

Description of problem:
Guest can be rendered incorrectly when width crosses a certain threshold. 

Version-Release number of selected component (if applicable):
On guest:
xorg-x11-drv-qxl-0.1.1-9.el7
xorg-x11-server-Xorg-1.15.0-27.el7.x86_64

On host:
qemu-kvm-1.5.3-73.el7.x86_64
spice-server-0.12.4-6.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Connect to the guest
2. Resize (fullscreen)

Actual results:
Screenshot

Additional info:
The display breaks when width crosses 1366, which is resolution of my laptops display, not sure if this is relevant in any way.

Comment 2 Tomas Jamrisko 2014-10-08 16:25:19 UTC
Ok, so. Had to give it another go, because the steps to reproduce aren't exactly clear. The thing is, it's not reproducible anymore. No packages were updated on neither client, guest or host. The only change that was done to the guest, was edited domain xml (added usb controller). 

However, back then, it was relatively easy to reproduce.

I have one external monitor connected to my laptop, which in this case served as a host.
The resolutions are 1920x1080 and 1366x768. 
When I started the guest and connected to it, switching to fullscreen usually ended in corrupted screen (it never returned to normal, as it usually does), until another resize.

So I tried resizing the window, and it failed when it reached the mentioned width, regardless of height/total area.

Maybe there were some other factors contributing to it, that I'm not aware of :(. Anyway, feel free to close as insufficient_data.

Comment 3 Marc-Andre Lureau 2014-10-08 16:36:47 UTC
until there is a way to reproduce, and given the lack of details (logs etc) I think we should close indeed. feel free to reopen if it happens again.