Bug 919089
| Summary: | Setting wrong resolution when switching to fullscreen | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jiri Pallich <jpallich> |
| Component: | spice-vdagent | Assignee: | Hans de Goede <hdegoede> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.4 | CC: | abienven, acathrow, alevy, bsarathy, cfergeau, dallan, dblechte, dyasny, gkong, hdegoede, jwest, marcandre.lureau, mbarta, mkrcmari, mzhan, pm-eus, rwu, tjamrisk, tlavigne, tzheng |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | spice-vdagent-0.12.0-4.el6_4.1 | Doc Type: | Bug Fix |
| Doc Text: |
While adjusting the guest monitor configuration, the SPICE agent failed to set the resolution when it switched to full-screen mode, because the guests video memory was exhausted. This left the guest monitor configuration in an inconsistent state. This update fixes the issue by reverting the guest monitor configuration to the previous state, when the agent fails to adjust the guest monitor configuration.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-18 14:09:54 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: | 881020 | ||
| Bug Blocks: | |||
|
Description
Jiri Pallich
2013-03-07 15:12:11 UTC
This is fixed in spice-vdagent-0.12.0-4.el6_4.1 moving to MODIFIED. Note to qe, for details of the fix, and the new behavior please see bug 881020 comment 35. 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-2013-0654.html |