Your message dated Sun, 26 Oct 2025 13:56:29 +0100
with message-id <[email protected]>
and subject line Re: Bug#1119064: fwupd: fails to start with undefinded symbol
has caused the Debian Bug report #1119064,
regarding fwupd: fails to start with undefinded symbol
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 [email protected]
immediately.)
--
1119064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119064
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fwupd
Version: 2.0.16-3
Severity: serious
X-Debbugs-Cc: [email protected]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
after the -3 update fixing the segfault fwupd still fails to start for
me:
$ doas /usr/libexec/fwupd/fwupd
usr/libexec/fwupd/fwupd: symbol lookup error:
/usr/lib/x86_64-linux-gnu/fwupd-2.0.16/libfwupdplugin.so: undefined
symbol: libusb_wrap_sys_device
best,
werdahias
- -- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.16.9+deb14-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled
Versions of packages fwupd depends on:
ii libarchive13t64 3.7.4-4+b1
ii libblkid1 2.41.2-4
ii libc6 2.41-12
ii libcbor0.10 0.10.2-2
ii libcurl3t64-gnutls 8.17.0~rc2-1
ii libdrm-amdgpu1 2.4.127-1
ii libdrm2 2.4.127-1
ii libflashrom1 1.6.0-2
ii libfwupd3 2.0.16-3
ii libglib2.0-0t64 2.86.1-1
ii libgnutls30t64 3.8.10-2
ii libjcat1 0.2.3-2
ii libjson-glib-1.0-0 1.10.8+ds-1
ii liblzma5 5.8.1-2
ii libmbim-glib4 1.32.0-1
ii libmbim-proxy 1.32.0-1
ii libmm-glib0 1.24.2-1
ii libmnl0 1.0.5-3
ii libpolkit-gobject-1-0 126-2
ii libprotobuf-c1 1.5.1-1
ii libqmi-glib5 1.36.0-1
ii libqmi-proxy 1.36.0-1
ii libreadline8t64 8.3-3
ii libsqlite3-0 3.46.1-8
ii libsystemd0 258.1-1
ii libtss2-esys-3.0.2-0t64 4.1.3-1.2
ii libusb-1.0-0 2:1.0.29-2
ii libxmlb2 0.3.24-2
ii shared-mime-info 2.4-5+b3
ii systemd-standalone-sysusers [systemd-sysusers] 258.1-1
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
Versions of packages fwupd recommends:
ii bolt 0.9.10-1
ii dbus [default-dbus-system-bus] 1.16.2-2
ii fwupd-amd64-signed [fwupd-signed] 1:1.8+1
ii jq 1.8.1-4
ii python3 3.13.7-1
ii udisks2 2.10.91-1
Versions of packages fwupd suggests:
pn gir1.2-fwupd-2.0 <none>
- -- Configuration Files:
/etc/fwupd/fwupd.conf [Errno 13] Keine Berechtigung: '/etc/fwupd/fwupd.conf'
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iIsEARYKADMWIQQUWTv/Sl6/b+DpcW7svtu2B7myvgUCaP4NSRUcd2VyZGFoaWFz
QGRlYmlhbi5vcmcACgkQ7L7btge5sr4ZNwD/W5IoGhDb5UEwaSB/U7FdO9WAROvK
618O+Oz1uNFVJIsBAK09XQkkwydGjwQga8zXlmLZolN3F84V99zTbOyLZNEO
=yknU
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Sun, 26 Oct 2025 13:22, Chris Hofstaedtler <[email protected]> wrote:
Hi,
not the maintainer, just chiming in...
On Sun, Oct 26, 2025 at 01:00:15PM +0100, Matthias Geiger wrote:
after the -3 update fixing the segfault fwupd still fails to start for
me:
$ doas /usr/libexec/fwupd/fwupd
usr/libexec/fwupd/fwupd: symbol lookup error:
/usr/lib/x86_64-linux-gnu/fwupd-2.0.16/libfwupdplugin.so: undefined
symbol: libusb_wrap_sys_device
libusb_wrap_sys_device should be provided by libusb-1.0.so.0 (from
libusb-1.0-0).
Can you check what your systems dynamic linker uses to resolve
libfwupdplugin.so's libs, for example using:
ldd /usr/lib/*linux-gnu/fwupd-2.0.*/libfwupdplugin.so
For reference, on my arm64 hardware this gives:
libusb-1.0.so.0 => /lib/aarch64-linux-gnu/libusb-1.0.so.0
(0x0000ffffad830000)
Hi,
sorry for the noise, turned out this was caused by third-party software
doing funny stuff with ldconfig :/
Fixed now.
best,
werdahias
--- End Message ---
