Bug 906560
Summary: | spice client crashes at first Shift-Ctrl-V in Microsoft Outlook | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Yonit Halperin <yhalperi> |
Component: | mingw-virt-viewer | Assignee: | Marc-Andre Lureau <marcandre.lureau> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.2.0 | CC: | acathrow, alevy, alexl, audgiri, bsanford, byount, cfergeau, dblechte, dyasny, hdegoede, jackoramone, jbiddle, jforbes, jlmagee, kraxel, lagarcia, malittle, marcandre.lureau, pvine |
Target Milestone: | --- | ||
Target Release: | 3.2.0 | ||
Hardware: | All | ||
OS: | Windows | ||
Whiteboard: | |||
Fixed In Version: | mingw-virt-viewer-0.5.3-23.el6ev | Doc Type: | Bug Fix |
Doc Text: |
Previously, pressing Shift-Ctrl-V in Microsoft Outlook caused the SPICE client to crash. Now, palettes of un-rendered bitmaps are appropriately cached, so that Outlook no longer causes the SPICE client to crash.
|
Story Points: | --- |
Clone Of: | 906558 | Environment: | |
Last Closed: | 2013-06-10 20:02:16 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: | 826036, 906558, 984745 | ||
Bug Blocks: |
Description
Yonit Halperin
2013-01-31 22:05:07 UTC
let's move to POST, since the patch exists I just tested this with RHEV-M 3.2 (sf10.1) and a Windows 7 guest. I pressed "Shift-Ctrl-V" and I got a "Move Items" dialog box and virt-viewer crashed (Closed the virt-viewer window). I tried to re-launch the virt-viewer from the User Portal, and the virt-viewer crashed shortly after I opened the Windows 7x64 VM for the second time. in mingw-spice-gtk 0.14-5 This is verified fixed in mingw-virt-viewer-0.5.3-23.el6ev. 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/RHEA-2013-0889.html |