Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Whatever I do to use scanner (scanimage -L shows "device `plustek:libusb:002:007' is a Canon CanoScan LiDE25 flatbed scanner") I end with some kind of crash.
Version-Release number of selected component:
sane-backends-1.0.24-9.el7
Additional info:
reporter: libreport-2.1.11
backtrace_rating: 4
cmdline: scanimage -d plustek
crash_function: sane_dll_cancel
executable: /usr/bin/scanimage
kernel: 3.10.0-123.9.3.el7.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 sane_dll_cancel at /lib64/libsane.so.1
#2 poll at /lib64/libc.so.6
#3 handle_events at /lib64/libusb-1.0.so.0
#4 libusb_handle_events_timeout_completed at /lib64/libusb-1.0.so.0
#5 libusb_handle_events_completed at /lib64/libusb-1.0.so.0
#6 do_sync_bulk_transfer at /lib64/libusb-1.0.so.0
#7 libusb_bulk_transfer at /lib64/libusb-1.0.so.0
#8 sanei_usb_read_bulk at /lib64/libsane.so.1
#9 sanei_lm983x_read at /lib64/libsane.so.1
#10 usb_IsScannerReady at /usr/lib64/sane/libsane-plustek.so.1
Interesting thing about this crash (which I can still happily reproduce) is that gimp-xsane interface is able to acquire preview of the image, but when doing the real scan, then the crash happens.
Sorry for the delay. Unfortunately, even the second attempt at a backtrace is missing vital information like on which instruction/line it crashed -- you may need to have the sane-backends-debuginfo package installed when it crashes so the abrt tool can get at this info.
Do you have a Fedora machine with sane-backends-1.0.25, and if yes, can you connect the scanner there and reproduce the crash?
(In reply to Nils Philippsen from comment #18)
> Sorry for the delay. Unfortunately, even the second attempt at a backtrace
> is missing vital information like on which instruction/line it crashed --
> you may need to have the sane-backends-debuginfo package installed when it
> crashes so the abrt tool can get at this info.
>
> Do you have a Fedora machine with sane-backends-1.0.25, and if yes, can you
> connect the scanner there and reproduce the crash?
Unfortunately, the scanner went west completely and I have thrown it away. You can close this bug as INSUFFICIENT_DATA if you wish.