Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libusb-1.0 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
* Impact
libusb as an incompatibility with previous versions which breaks ink and maybe some other softwares
* Test case
install ink and
$ ink -p usb
it shouldn't segfault
* Regression potential
libusb is used by fwupd, libfprint, cups, boxes, gvfs and others. Ensure those services are still working as expected (printing, listing new usb devices on the desktop, fingerprint login, firmware update, boxes VM usb hardware detection)
-------
The following packages are installed:
1. libusb-
2. libinklevel5/
3. ink/jammy,now 0.5.3-3 amd64
Command invoked is:
ink -p usb
Result is a segmentation fault. Backtrace in gdb:
gdb) bt
#0 0x00007ffff7dfcf74 in pthread_mutex_lock () from /lib/x86_
#1 0x00007ffff7d52879 in libusb_
#2 0x00007ffff7f96c90 in find_printer () from /lib/x86_
#3 0x00007ffff7f963e5 in get_device_id () from /lib/x86_
#4 0x00007ffff7f90d55 in get_ink_level () from /lib/x86_
#5 0x000055555555554e in ?? ()
#6 0x00007ffff7d8ed90 in ?? () from /lib/x86_
#7 0x00007ffff7d8ee40 in __libc_start_main () from /lib/x86_
#8 0x0000555555555795 in ?? ()
I have compiled libusb-1.0.26 into my $HOME and pointed LD_LIBRARY_PATH to it. Then I get the expected result:
ink -p usb
ink 0.5.3 (c) 2018 Markus Heinz
hp deskjet 5550
Black: 0%
Color: 0%
ldd /usr/bin/ink
linux-vdso.so.1 (0x00007ffe6e47
libinklevel.so.5 => /lib/x86_
libc.so.6 => /lib/x86_
libusb-1.0.so.0 => /home/markus/
/lib64/
libudev.so.1 => /lib/x86_
So I have the assumption that there is a regression in libusb-1.0.25 which has been fixed in libusb-1.0.26.
On Ubuntu 20.04 there was no problem with libusb and libinklevel / ink. It just appeared after the update to Ubuntu 22.04 which I did today.
affects: | linux (Ubuntu) → libusb-1.0 (Ubuntu) |
tags: | added: jammy |
description: | updated |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1973091
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.