Bug 1328916
| Summary: | [RFE] Spice: drop support for usbclerk on Windows client machines in RHEV-M 4.0 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Uri Lublin <uril> |
| Component: | rhevm-spice-client | Assignee: | Uri Lublin <uril> |
| Status: | CLOSED ERRATA | QA Contact: | SPICE QE bug list <spice-qe-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | bgraveno, cfergeau, dblechte, djasa, gklein, lsurette, rbalakri, sherold, srevivo, trichard, ylavi |
| Target Milestone: | ovirt-4.0.0-beta | Keywords: | FutureFeature |
| Target Release: | 4.0.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rhevm-spice-client-4.0-1 | Doc Type: | Deprecated Functionality |
| Doc Text: |
The usbclerk service has been dropped from this release. The usbdk driver is now supported instead, and it supports more devices than WinUSB, which was installed by usbclerk. The usbdk driver is installed via the MSI installer.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-23 20:49:43 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: | |||
|
Description
Uri Lublin
2016-04-20 14:46:09 UTC
oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target. Will 4.0 UsbDk installer also replace usbclerk installations (and possibly old redirector installations), to ease the transition? (In reply to David Jaša from comment #4) > Will 4.0 UsbDk installer also replace usbclerk installations (and possibly > old redirector installations), to ease the transition? No, users would need to remove it manually. If both usbclerk and usbdk are installed, usbdk is to be used for spice usbredir by remote-viewer. 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-1681.html |