Red Hat Bugzilla – Bug 1144043
after plug/redirection of usb device, virt-viewer freezes for several seconds before the device gets redirected
Last modified: 2016-03-09 15:09:11 EST
Description of problem: after plug/redirection of usb device, virt-viewer freezes for several seconds before the device gets redirected Version-Release number of selected component (if applicable): spice-usbdk-win v0.02-1 client systems: xp, 7 32b, 7 64b How reproducible: frequent Steps to Reproduce: 1. connect to some guest with usbdk-enabled client 2. plug in a device (to trigger auto-redirection), check a device in "USB device selection" Actual results: before the device is successfully redirected, virt-viewer/spice-gtk freezes for several seconds Expected results: 1. the time to redirect the device should be comparable to winusb/usbclerk - a fraction of second 2. the device redirection should be asynchronous Additional info:
In winusb back-end the redirection process is asynchronous one, so the GUI is doesn't wait for a finishing of the process. In UsbDk, the process is synchronous and therefore the GUI freezes until end of redirecting. The problem should be solved in GUI.
Fix pending rebase of current spice-gtk patches to master.
This is discussed in http://lists.freedesktop.org/archives/spice-devel/2015-May/020037.html and http://lists.freedesktop.org/archives/spice-devel/2015-June/020042.html
Seems fixed in current builds
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
Fixed by patch series: UsbDk backend for spice-gtk: http://lists.freedesktop.org/archives/spice-devel/2015-October/022851.html Making start/stop redirection asynchronous: http://lists.freedesktop.org/archives/spice-devel/2015-October/022873.html
What is the status of this bug?
If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format: Cause: Consequence: Fix: Result:
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