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.
Description of problem:
when I log into gnome session I get maximized virt-viewer with correct resolution .After changing size nothing happens. It should be redrawn but it's not. After opening second display it starts working correctly again. I suspect that this makes boxes working a bit oddly as well.
Version-Release number of selected component (if applicable):
mesa-9.2.5-1.20131218.el7.x86_64
virt-viewer-0.5.7-4.el7.x86_64
spice-gtk3-0.20-7.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1.start virt machine
2.connect to it via virt-viewer -c qemu:///system RHEL7
3.log into session
4.resize it a bit
Actual results:
resolution not corrected
Expected results:
resolution should be always correct
Additional info:
after view-> displays -> second enabled I can see correct resizing, after turning it off I am all the way back to original buggy behavior
Comment 1RHEL Program Management
2014-03-22 06:15:20 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3Marc-Andre Lureau
2014-07-10 19:23:27 UTC
What is the host? If host is rhel6, please try again with qemu-kvm-0.12.1.2-2.429.el6. thanks
Comment 5Marc-Andre Lureau
2014-07-24 12:01:05 UTC
can you try again with current builds? provide xrandr output before and after resizing. Also if it's a rendering glitch, a small screencast could help. thanks
Created attachment 920523[details]
screencast
I hope there is everything recorded there. I probably set resolution to 1680x1050 at some point to suit my external screens. But this shouldn't change the behaviour to this, right?
By the way, I can reproduce this with a rhel7 guest and a rhel6 host running qemu-kvm-0.12.1.2-2.438.el6
Comment 8Marc-Andre Lureau
2014-08-13 17:32:36 UTC
(In reply to Jonathon Jongsma from comment #7)
> By the way, I can reproduce this with a rhel7 guest and a rhel6 host running
> qemu-kvm-0.12.1.2-2.438.el6
it works fine for me, with -436.
In guest, I have mutter-3.8.4-10, kernel 3.10.0-123
Jonathon, do you want to investigate the bug further (assign the bug to you?)
Aha, my RHEL7 guest has mutter 3.8.4-10 and kernel 3.10.0-131. If I revert to using kernel -123, it works OK.
Comment 10Jonathon Jongsma
2014-08-13 19:55:20 UTC
I spoke too soon. After rebooting into -123 again, it is failing again.
Comment 11Jonathon Jongsma
2014-08-14 22:19:43 UTC
In trying to debug this issue, I managed to corrupt my test vm disk (presumably from accidentally running it manually under qemu while it was already running under libvirt). After setting up a fresh rhel7 guest, I can no longer reproduce this issue.
Comment 12Jonathon Jongsma
2014-08-18 16:52:41 UTC
Vladimir, can you still reproduce this on a freshly-installed and completely-updated RHEL7 vm?