Your message dated Sat, 24 Oct 2020 14:47:28 +0100
with message-id <20201024134728.ga156...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#972703: gnome-boxes does not start, undefined symbol
libusb_set_option
has caused the Debian Bug report #972703,
regarding gnome-boxes does not start, undefined symbol libusb_set_option
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
972703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-boxes
Version: 3.30.3-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
gnome-boxes does not start. Trying from command line, issues this error:
$ gnome-boxes
gnome-boxes: symbol lookup error:
/usr/lib/x86_64-linux-gnu/libusbredirhost.so.1: undefined symbol:
libusb_set_option
Similar issue when starting qemu:
$ qemu-system-x86_64
qemu-system-x86_64: symbol lookup error: qemu-system-x86_64: undefined
symbol: libusb_set_option
There is also issue #960330 for virt-viewer with the same error.
Thank you
-- System Information:
Debian Release: 10.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-12-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-boxes depends on:
ii dconf-gsettings-backend [gset 0.30.1-2
ii libarchive13 3.3.3-4+deb10u1
ii libc6 2.28-10
ii libcairo2 1.16.0-4
ii libfreerdp2-2 2.0.0~git20190204.1.2693389a+dfsg1-1+deb10u2
ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii libglib2.0-0 2.58.3-2+deb10u2
ii libgovirt2 0.3.4-3.1
ii libgtk-3-0 3.24.5-1
ii libgtk-vnc-2.0-0 0.9.0-1.1
ii libgudev-1.0-0 232-2
ii libosinfo-1.0-0 1.2.0-1
ii libosinfo-bin 1.2.0-1
ii libpango-1.0-0 1.42.4-8~deb10u1
ii librest-0.7-0 0.8.1-1
ii libsecret-1-0 0.18.7-1
ii libsoup2.4-1 2.64.2-2
ii libspice-client-glib-2.0-8 0.35-2
ii libspice-client-gtk-3.0-5 0.35-2
ii libtracker-sparql-2.0-0 2.1.8-2
ii libusb-1.0-0 2:1.0.22-2
ii libvirt-daemon 5.0.0-4+deb10u1
ii libvirt-glib-1.0-0 1.0.0-1
ii libwebkit2gtk-4.0-37 2.28.4-1~deb10u1
ii libxml2 2.9.4+dfsg1-7+b3
ii mtools 4.0.23-1
ii tracker 2.1.8-2
Versions of packages gnome-boxes recommends:
ii qemu-system-x86 1:3.1+dfsg-8+deb10u8
gnome-boxes suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 24 Oct 2020 at 13:32:41 +0100, Carnë Draug wrote:
> This is embarassing but I found now what was the issue. There is one
> package that I installed some months ago that was not from Debian
> repos and for some reason it installs /lib/libusb.
It's good to know that this doesn't seem to be a more general dpkg issue!
I'd recommend using a container or chroot when installing third-party
software, particularly if it isn't in .deb format, to avoid it causing
bugs like this.
> The package in question is xiAPI, from ximea, a company for microscope
> cameras
Please report to them that this broke unrelated software. If their
software needs to bundle libraries like libusb, it should install them
to a location outside the system's normal search path, and use RPATH,
RUNPATH or a wrapper script to make them visible to their software (only) -
the same techniques typically used in Linux ports of games.
smcv
--- End Message ---
