Bug 1155764
Summary: | always fullscreen for SPICE-xpi | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Peter Manzella <pmanzell> | |
Component: | mingw-virt-viewer | Assignee: | Jonathon Jongsma <jjongsma> | |
Status: | CLOSED ERRATA | QA Contact: | SPICE QE bug list <spice-qe-bugs> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 3.5.0 | CC: | benl, cfergeau, cww, dblechte, djasa, dyuan, fidencio, gklein, iheim, jjongsma, lsurette, meverett, michal.skrivanek, mkalinin, mkrcmari, mzhan, pnovotny, rbalakri, Rhev-m-bugs, sherold, tjamrisk, tpelka, tspeetje, tzheng, uril, vehrlich, virt-bugs, virt-viewer-maint, yeylon, ykaul | |
Target Milestone: | ovirt-3.6.0-rc | Keywords: | ZStream | |
Target Release: | 3.6.0 | |||
Hardware: | Unspecified | |||
OS: | Windows | |||
Whiteboard: | ||||
Fixed In Version: | mingw-virt-viewer-2.0-2.el7ev | Doc Type: | Bug Fix | |
Doc Text: |
Previously, the Red Hat Enterprise Virtualization Manager always opened the virt-viewer client in full screen mode, even if the client was not configured to open in full screen. This occurred because the CONTROLLER_AUTO_DISPLAY_RES flag was automatically set. This has been fixed and the Red Hat Enterprise Virtualization Manager now ignores CONTROLLER_AUTO_DISPLAY_RES flag, and the client now opens in full screen mode only when the CONTROLLER_SET_FULL_SCREEN flag is set.
|
Story Points: | --- | |
Clone Of: | 1149352 | |||
: | 1172126 (view as bug list) | Environment: | ||
Last Closed: | 2016-03-09 20:09:32 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Spice | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1149352, 1181289 | |||
Bug Blocks: | 1144449, 1172126 |
Comment 2
Jonathon Jongsma
2014-10-23 14:54:57 UTC
Should be addressed by the rebase 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/RHEA-2016-0377.html |