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.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1973091
Title:
Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink
Status in linux package in Ubuntu:
Incomplete
Bug description:
The following packages are installed:
1. libusb-1.0-0/jammy,now 2:1.0.25-1ubuntu1 amd64
2. libinklevel5/jammy,now 0.9.3-3 amd64
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_64-linux-gnu/libc.so.6
#1 0x00007ffff7d52879 in libusb_get_device_list () from
/lib/x86_64-linux-gnu/libusb-1.0.so.0
#2 0x00007ffff7f96c90 in find_printer () from
/lib/x86_64-linux-gnu/libinklevel.so.5
#3 0x00007ffff7f963e5 in get_device_id () from
/lib/x86_64-linux-gnu/libinklevel.so.5
#4 0x00007ffff7f90d55 in get_ink_level () from
/lib/x86_64-linux-gnu/libinklevel.so.5
#5 0x000055555555554e in ?? ()
#6 0x00007ffff7d8ed90 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7 0x00007ffff7d8ee40 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#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 (0x00007ffe6e47b000)
libinklevel.so.5 => /lib/x86_64-linux-gnu/libinklevel.so.5
(0x00007f479dd44000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f479db1c000)
libusb-1.0.so.0 =>
/home/markus/privat/programmieren/c/printer/libusb-dist/libusb-1.0.26/libusb/.libs/libusb-1.0.so.0
(0x00007f479dafc000)
/lib64/ld-linux-x86-64.so.2 (0x00007f479dd79000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f479dad2000)
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973091/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
