Hide Forgot
Description of problem: Old IP USB Auto-Share does not work in initial full-screen of spice session - in full-screen mode right after connecting to a guest using spice remote viewer client through User Portal. Once an user goes to windowed mode and back to full-screen, Auto-share does work correctly. !This same bug was observed and fixed in spicec already please see bug #769020 so It may be the same issue => fix. Version-Release number of selected component (if applicable): virt-viewer-0.5.2-1.el6.x86_64 spice-gtk-0.11-1.el6.x86_64 spice-xpi-2.7-11.el6.x86_64 spice-protocol-0.10.1-1.el6.noarch spice-glib-0.11-1.el6.x86_64 spice-gtk-tools-0.11-1.el6.x86_64 How reproducible: always Steps to Reproduce: 1. Connect to a Windows guest with guest tools installed from a client with usb share service installed and usb kspice module loaded. Check USB Auto-share and Open in full-screen option before that in User portal. 2. Plug USB device into client Actual results: USB devices is not mounted into Windows Guest. Expected results: USB device should be mounted into Guest. Additional info:
Retested with virt-viewer-0.5.2-2.el6, The bug still occurs.
proposed patch sent to virt-viewer mailing list
Fixed upstream commit df1fbf1e8d0b4f56bda6dc4cf40379d5af30d128 Author: Marc-Andre Lureau <marcandre.lureau> Date: Wed Mar 21 22:47:06 2012 +0100 Notify focus state when the foreign menu title is set The current code only inform of focus state when the listener is ready. spice-gtk controller code lacks signal when a client connects, but a client will set the title when connected and send a notify signal. Use this event to notify of application focus state.
according to comment 11, the bug fixed on virt-viewer-0.5.2-3.el6 move to verified.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No documentation needed.
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-2012-0772.html