Bug 864038

Summary: Window doesn't maximize
Product: Red Hat Enterprise Linux 6 Reporter: Tomas Jamrisko <tjamrisk>
Component: spice-gtkAssignee: Marc-Andre Lureau <marcandre.lureau>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 6.3CC: acathrow, cfergeau, dblechte, dyasny, pvine
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: 2013-05-10 11:58:40 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
screencast none

Description Tomas Jamrisko 2012-10-08 12:18:49 UTC
Description of problem:
Windows 7 -- both guest and client, vdservice running on guest

Having a relatively small (less than half of screen size in both dimensions) remote-viewer windows on client, and attempting to maximize it using the button in upper right corner results in the window not being scaled up properly -- it attempts to maximize, but ends just halfway there

Version-Release number of selected component (if applicable):
mingw-virt-viewer-0.5.3-11.el6
qemu-kvm-rhev-0.12.1.2-2.295.el6*, spice-server-0.10.1-*
Tools from RHEVM3.0

How reproducible:
Always

Steps to Reproduce:
1. Connect to a Windows 7 guest from a windows 7 client
2. Resize the window to something relatively small
3. Try to maximize
  
Actual results:
Window isn't maximized

Expected results:
It should be

Additional info:

****This bug seems to be *FIXED* in the latest packages which are in RHEVM3.1 to be (qxl-win-unsigned-0.1-15, vdagent-win-0.1-12, virtio-serial from virtio-win-prewhql-0.1-39)****

Comment 1 Marc-Andre Lureau 2012-10-29 18:11:03 UTC
I can't reproduce, can you try with latest mingw-virt-viewer-0.5.3-12 ? Do you have the guest configured with agent & qxl driver? You could also try to record your desktop so we could see what's happening.

Comment 2 Tomas Jamrisko 2012-10-30 15:42:00 UTC
Well, as I mentioned -- this problem can't be reproduced when newer versions of vdagent and qxl are installed on the guest -- so if you believe that the problem doesn't need any further fixes in virt-viewer feel free to close it. 

*However* the problem still happens with new version of virt-viewer (vdagent and qxl have to be older though).

Comment 3 Tomas Jamrisko 2012-10-30 15:46:10 UTC
Created attachment 635678 [details]
screencast

This is what happens when one tries to maximize remote-viewer (2 attempts in total) -- cursor isn't captured

As you can see -- the window first maximizes, and change of resolution to best fit the window causes the window to decrease its size (yet the button still shows it's maximized)

Comment 4 Marc-Andre Lureau 2012-10-30 17:42:15 UTC
thanks for the screencast

(In reply to comment #3)
> As you can see -- the window first maximizes, and change of resolution to
> best fit the window causes the window to decrease its size (yet the button
> still shows it's maximized)

This is a difference of behaviour between gtk on windows and linux. We call gtk_window_resize() even when the window is maximized, and this cause the window to leave the maximize state on Windows. I believe the fix should be in gtk+. Working around that problem in virt-viewer isn't really a practical solution, and will make the code more complicated.

Anyway, given that newer driver/agent solves the issue (since we get exact resolution, we don't need to resize later on), I would lower the issue for now.

Comment 6 RHEL Program Management 2012-12-14 06:51:33 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 8 Marc-Andre Lureau 2013-05-09 19:53:26 UTC
Afaik, this was windows only bug which got fixed in rhev 3.2. right Tomas?

Comment 9 Tomas Jamrisko 2013-05-10 07:33:51 UTC
You are right, it was windows only. And yes, it seems to be fixed. But I have honestly no idea about when, Must have been in 3.2, but since this is reported against spice-gtk, which is only in RHEL...

Comment 10 Marc-Andre Lureau 2013-05-10 11:58:40 UTC
thanks Tomas, let's close as current release then,