Bug 1172126
Summary: | always fullscreen for SPICE-xpi | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | mingw-virt-viewer | Assignee: | Jonathon Jongsma <jjongsma> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.5.0 | CC: | benl, bsanford, cfergeau, codong, cww, dblechte, djasa, dyuan, ecohen, fidencio, gklein, iheim, jjongsma, lsurette, michal.skrivanek, mkalinin, mkrcmari, mzhan, ofrenkel, pnovotny, rbalakri, Rhev-m-bugs, sherold, tjamrisk, tpelka, tspeetje, tzheng, uril, vehrlich, virt-bugs, virt-viewer-maint, yeylon |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | 3.5.1 | ||
Hardware: | Unspecified | ||
OS: | Windows | ||
Whiteboard: | virt | ||
Fixed In Version: | mingw-virt-viewer-0.6.0-2.el6.2 rhevm-spice-client-*-3.5-3 | Doc Type: | Bug Fix |
Doc Text: |
Copied from bug 1155764:
Cause: CONTROLLER_AUTO_DISPLAY_RES flag is always set when using the RHEVM portal. When CONTROLLER_AUTO_DISPLAY_RES is set the client is opened in full screen mode.
Consequence: Client is always opened in the full screen mode.
Fix: Ignore CONTROLLER_AUTO_DISPLAY_RES flag.
Result: Client is opened in full screen mode only when is set to full screen (CONTROLLER_SET_FULL_SCREEN flag is set)
|
Story Points: | --- |
Clone Of: | 1155764 | Environment: | |
Last Closed: | 2015-03-18 12:12:34 UTC | Type: | --- |
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: | 1155764 | ||
Bug Blocks: | 1193058 |
Comment 2
Bill Sanford
2015-02-26 13:40:07 UTC
I tested with the following config: Client: RHEL-7.1-20150115.0 Host: RHEL 6.6x64 GA Guest: Win7x64 In comment #2, it should be Verified with virt-viewer-0.6.0-12.el7 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/RHSA-2015-0698.html |