Bug 1052176

Summary: virt-viewer is not resizing itself till I have second display enabled
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: spice-gtkAssignee: Jonathon Jongsma <jjongsma>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: acathrow, dblechte, fidencio, jjongsma, marcandre.lureau, vbenes
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-19 08:19:54 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:
Bug Depends On: 1075139, 1109400    
Bug Blocks:    
Attachments:
Description Flags
screencast none

Description Vladimir Benes 2014-01-13 12:57:38 UTC 
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 1 RHEL 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 3 Marc-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 4 Vladimir Benes 2014-07-24 11:52:15 UTC 
nope both host and guest were rhel7 based
Comment 5 Marc-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
Comment 6 Vladimir Benes 2014-07-24 12:09:49 UTC 
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?
Comment 7 Jonathon Jongsma 2014-08-13 16:38:49 UTC 
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 8 Marc-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?)
Comment 9 Jonathon Jongsma 2014-08-13 19:50:47 UTC 
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 10 Jonathon Jongsma 2014-08-13 19:55:20 UTC 
I spoke too soon. After rebooting into -123 again, it is failing again.
Comment 11 Jonathon 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 12 Jonathon Jongsma 2014-08-18 16:52:41 UTC 
Vladimir, can you still reproduce this on a freshly-installed and completely-updated RHEL7 vm?