RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Trying to redirect two similar devices would lead the second usbredirect to crash.

How reproducible: 100%

lsusb (redacted)
Bus 002 Device 006: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50
Bus 002 Device 005: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50

1) By using vendor:product

usbredirect --to localhost:5550 --device 0951:1666 # first
usbredirect --to localhost:5550 --device 0951:1666 # second fails

2) By using bus-device

usbredirect --to localhost:5550 --device 02-06 # first
usbredirect --to localhost:5550 --device 02-05 # second fails

Actual results:

second usbredirect crashes

Expected results:

usbredirect not to crash and USB device to show in the guest

Additional info:

Upstream bug report: https://gitlab.freedesktop.org/spice/usbredir/-/issues/29

Posted a working fix: https://gitlab.freedesktop.org/spice/usbredir/-/merge_requests/67

> usbredirect --to localhost:5550 --device 0951:1666 # second fails

> usbredirect --to localhost:5550 --device 02-05 # second fails

Bad copy-paste here. The second usbredirect uses a different port. Using the same port would always fail.

Reproduced and verified with usbredir-0.12.0-3.el8
Redirection of two identical devices by using vendor:product and bus-device works now.

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 (usbredir bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2023:2884