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 1104064

Summary: New display will be zoomed out to a very small display size
Product: Red Hat Enterprise Linux 6 Reporter: CongDong <codong>
Component: virt-viewerAssignee: Jonathon Jongsma <jjongsma>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.6CC: cfergeau, codong, dblechte, jjongsma, juzhou, lcui, marcandre.lureau, mzhan, rbalakri, tzheng, zsong
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-viewer-0.6.0-6.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-14 06:31:24 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:    
Bug Blocks: 1009648    
Attachments:
Description Flags
Screenshot after enable new display
none
virt-viewer log with spice debug option
none
xrandr log in guest none

Description CongDong 2014-06-03 08:08:46 UTC
Description of problem:
When open a new display, the size of the new display will be very small.
Seems like it has been zoomed out.

Version-Release number of selected component (if applicable):
virt-viewer-0.6.0-1.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install a rhel spice guest
2. Connect the guest with virt-viewer
#virt-viewer $vm --debug
3. Enable a new display
View -> Dislays -> Display 2
4. Check the display size of new display

Actual results:
The default display size of the new display is very small

Expected results:
The new display should not be zoomed out.

Additional info:

Comment 2 CongDong 2014-06-03 08:19:42 UTC
Created attachment 901643 [details]
Screenshot after enable new display

The new display is very small

Comment 3 CongDong 2014-06-03 08:31:17 UTC
Created attachment 901656 [details]
virt-viewer log with spice debug option

Comment 4 CongDong 2014-06-03 08:32:17 UTC
Created attachment 901657 [details]
xrandr log in guest

Comment 5 Marc-Andre Lureau 2014-06-04 14:09:03 UTC
weird, I managed to reproduce yesterday, but not today..

Comment 6 Jonathon Jongsma 2014-06-04 21:06:04 UTC
It appears to only affect the gtk2 build.  I can reproduce it consistently on gtk2, but never on gtk3.

Comment 7 Jonathon Jongsma 2014-06-05 17:00:39 UTC
This is the commit that introduced this regression:

commit c34ec01b3d3912e5348e8a4514638ddcfe17cf4e
Author: Marc-André Lureau <marcandre.lureau>
Date:   Thu Jul 18 15:06:00 2013 +0200

    win32: fix first window un-shrinkable at start
    
    The fix 0dca975d64fcf0782ec7b3e3bd965f1bcf47c528 make the first window
    unshrinkable right after start. Wait until the window is mapped and
    remove the dirty-resizable state after (win32/gtk2).


Unfortunately, there's not much detail about exactly *why* this change was introduced (bug references, etc). What was the problem being fixed? The previous commit mentioned here says something about fixing a 50x50 secondary window, but no details about what conditions this occurred in, etc. Marc-Andre, can you comment on this?

Comment 8 Marc-Andre Lureau 2014-06-05 17:08:43 UTC
(In reply to Jonathon Jongsma from comment #7)
> 
> Unfortunately, there's not much detail about exactly *why* this change was
> introduced (bug references, etc). What was the problem being fixed? The

problem fixed: -> " fix first window un-shrinkable at start"

> previous commit mentioned here says something about fixing a 50x50 secondary
> window, but no details about what conditions this occurred in, etc.
> Marc-Andre, can you comment on this?

It could be that the bug was private, and I have been asked by daniel to not reference private rhbz bug in git commit. But here it is just referenced in previous commit indeed bug #978362

Comment 9 Marc-Andre Lureau 2014-06-05 17:27:41 UTC
(In reply to Marc-Andre Lureau from comment #8)
> previous commit indeed bug #978362

by previous, I mean next (reading log backward). A search for the patch in mailing list can also gives some clues.

Comment 10 Marc-Andre Lureau 2014-06-05 17:29:31 UTC
(In reply to Jonathon Jongsma from comment #6)
> It appears to only affect the gtk2 build.  I can reproduce it consistently
> on gtk2, but never on gtk3.

are you testing on rhel6? metacity vs mutter could also make a difference.

Comment 11 Jonathon Jongsma 2014-06-05 18:55:51 UTC
I can reproduce it on both rhel 6 and fedora 20 (with gtk2)

Comment 12 Marc-Andre Lureau 2014-06-06 17:34:09 UTC
is this a rhel-only bug again? I can't reproduce with win7 guest.

Comment 13 Marc-Andre Lureau 2014-06-06 17:37:29 UTC
ok, I can reproduce with rhel6 guest though

Comment 14 Marc-Andre Lureau 2014-06-10 19:20:59 UTC
Jonathon sent a working patch: https://www.redhat.com/archives/virt-tools-list/2014-June/msg00071.html

Comment 15 CongDong 2014-06-11 03:24:56 UTC
I found it's easy to reproduce with one display.

Steps:
1. prepare a spice rhel guest with only one display
2. # virt-viewer $vm
3. Click "View" -> "Zoom" -> "Normal Size"

Result:
the display will be very small

Comment 16 Jonathon Jongsma 2014-06-11 03:29:18 UTC
oh, this is a slightly different failure case.  My fix doesn't solve the scenario in comment #15...

Comment 17 Jonathon Jongsma 2014-06-11 20:13:01 UTC
follow-up patch to fix second symptom: https://www.redhat.com/archives/virt-tools-list/2014-June/msg00091.html

Comment 19 CongDong 2014-06-18 10:05:30 UTC
I can reproduce with:
virt-viewer-0.6.0-5.el6.x86_64

Verify with: virt-viewer-0.6.0-7.el6.x86_64

Steps:
Scenario 1:
1. prepare a spice rhel guest with only one display
2. # virt-viewer $vm
3. Click "View" -> "Zoom" -> "Normal Size"
4. Click "View" -> "Zoom out" for several times
5. Click "View" -> "Zoom" -> "Normal Size"
6. Click "View" -> "Zoom in" for several times
7. Click "View" -> "Zoom" -> "Normal Size"

Scenario 2:
1. Install a rhel spice guest
2. Connect the guest with virt-viewer
#virt-viewer $vm --debug
3. Enable other 3 displays
View -> Dislays -> Display (2,3,4)
4. Check the display size of new display

Result:
Scenario 1:
step 3, the display size is not changed.
Step 5, step 7, display can resize to the normal size

Scenario 2:
Step3, new display comes out with normal size.

As the result, set VERIFIED

Comment 20 errata-xmlrpc 2014-10-14 06:31:24 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1379.html