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 1096718 - The resolution of guest shows incorrect after switch to full-screen again with option --full-screen=auto-conf
Summary: The resolution of guest shows incorrect after switch to full-screen again wit...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-viewer
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Virt Viewer Maint
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1096717 1109400
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-12 10:38 UTC by tingting zheng
Modified: 2015-03-05 13:39 UTC (History)
9 users (show)

Fixed In Version: virt-viewer-0.6.0-1.el7
Doc Type: Bug Fix
Doc Text:
Launching the application with --full-screen=auto-conf, leaving fullscreen mode, and then returning to fullscreen mode didn't adjust the resolution of the guest properly In the new version (0.6.0) of virt-viewer, there is no longer a difference between --full-screen and --full-screen=auto-conf. The bug that was causing the misbehavior has been fixed, and the resolution is now adjusted properly when leaving and re-entering fullscreen mode.
Clone Of: 1096717
Environment:
Last Closed: 2015-03-05 13:39:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0295 0 normal SHIPPED_LIVE virt-viewer bug fix and enhancement update 2015-03-05 17:33:00 UTC

Description tingting zheng 2014-05-12 10:38:34 UTC 
As the bug can also be reproduced on rhel7,so cloned it to rhel7.


+++ This bug was initially created as a clone of Bug #1096717 +++

Description
The resolution of guest shows incorrect after switch to full-screen again with option --full-screen=auto-conf

Version:
virt-viewer-0.5.6-10.el6.x86_64
spice-gtk-0.20-11.el6_5.1.x86_64
spice-server-0.12.4-8.el6.x86_64
spice-gtk-python-0.20-11.el6_5.1.x86_64
spice-vdagent-0.14.0-3.el6_5.x86_64
spice-client-0.8.2-15.el6.x86_64
spice-glib-0.20-11.el6_5.1.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare a spice rhel guest with qxl+spicevmc
# virsh dumpxml $vm
...
    <channel type='spicevmc'>
      <target type='virtio' name='com.redhat.spice.0'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
...
    <graphics type='spice' port='5900' autoport='yes' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
    </graphics>
...
    <video>
      <model type='qxl' ram='65536' vram='65536' heads='1'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
...

2. Connect the guest with remote-viewer --full-screen=auto-conf
# remote-viewer spice://127.0.0.1:5900 --full-screen=auto-conf

3. After the guest is launched in full-screen mode,quit full-screen mode,then Click "View"->"Full-screen",the resolution shows incorrect.

Actual results：
As steps show.

Expected results:
Step 3,resolution of full-screen shows correct.

Additional info:
The issue can not be reproduced when launch remote-viewer --full-screen without option auto-conf.
The issue can be also reproduces on rhel7.
Comment 2 Marc-Andre Lureau 2014-07-03 18:05:10 UTC 
original bug got fixed by rebase, assuming same here.
Comment 4 tingting zheng 2014-07-21 08:45:11 UTC 
Tested pass with:
virt-viewer-0.6.0-1.el7.x86_64

Steps:
1. Prepare a spice rhel guest with qxl+spicevmc
# virsh dumpxml $vm
...
    <channel type='spicevmc'>
      <target type='virtio' name='com.redhat.spice.0'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
...
    <graphics type='spice' port='5900' autoport='yes' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
    </graphics>
...
    <video>
      <model type='qxl' ram='65536' vram='65536' heads='1'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
...

2. Connect the guest with remote-viewer --full-screen,since there is no auto-conf in remote-viewer manual,I use --full-screen option.
# remote-viewer spice://127.0.0.1:5900 --full-screen

3. After the guest is launched in full-screen mode,quit full-screen mode,then Click "View"->"Full-screen",the resolution shows correct.

Refer to the above comments,move the bug to VERIFIED.
Comment 6 errata-xmlrpc 2015-03-05 13:39:01 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.

https://rhn.redhat.com/errata/RHBA-2015-0295.html
Note You need to log in before you can comment on or make changes to this bug.