Bug 1635865 - /usr/bin/qemu-system-x86_64: undefined symbol: libusb_set_option
Summary: /usr/bin/qemu-system-x86_64: undefined symbol: libusb_set_option
Keywords:
Status: CLOSED DUPLICATE of bug 1625641
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-03 19:28 UTC by Alex G.
Modified: 2018-10-03 19:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-03 19:57:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alex G. 2018-10-03 19:28:35 UTC
Description of problem:

It appears there is a dependency issue with libusbx:
On a fresh install, qemu-kvm fails to start

Version-Release number of selected component (if applicable):

qemu-kvm-2.11.2-4.fc28.x86_64
libusbx-1.0.21-6.fc28.x86_64 


How reproducible:
I don't understand the grammar of this field.


Steps to Reproduce:
1. $ qemu-kvm

Actual results:
# qemu-kvm 
/usr/bin/qemu-system-x86_64: symbol lookup error: /usr/bin/qemu-system-x86_64: undefined symbol: libusb_set_option


Expected results:
qemu-kvm starts up.


Additional info:
User must manually upgrade to libusbx-1.0.22-1.fc28.x86_64.
With libusbx-1.0.21-6.fc28.x86_64, the problem persists.

Comment 1 Richard W.M. Jones 2018-10-03 19:57:20 UTC
This happens all the time when using a qemu version which
is later than the corresponding libusbx version.  I believe
the only good fix is for libusbx to start using symbol
versioning (which would probably have to happen upstream).

In the mean time, yes, the workaround is to upgrade to the
newest libusbx.

*** This bug has been marked as a duplicate of bug 1625641 ***


Note You need to log in before you can comment on or make changes to this bug.