Bug 1162593

Summary: [abrt] sane-backends: sane_dll_cancel(): scanimage killed by SIGSEGV
Product: Red Hat Enterprise Linux 7 Reporter: Matěj Cepl <mcepl>
Component: sane-backendsAssignee: Nils Philippsen <nphilipp>
Status: CLOSED INSUFFICIENT_DATA QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: mcepl, nphilipp
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:eeb816fa032eef1fbdd84f26ead994a599b2b8f7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-29 16:56:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: sosreport.tar.xz
none
better backtrace none

Description Matěj Cepl 2014-11-11 11:20:04 UTC
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

Comment 1 Matěj Cepl 2014-11-11 11:20:06 UTC
Created attachment 956237 [details]
File: backtrace

Comment 2 Matěj Cepl 2014-11-11 11:20:07 UTC
Created attachment 956238 [details]
File: cgroup

Comment 3 Matěj Cepl 2014-11-11 11:20:08 UTC
Created attachment 956239 [details]
File: core_backtrace

Comment 4 Matěj Cepl 2014-11-11 11:20:10 UTC
Created attachment 956240 [details]
File: dso_list

Comment 5 Matěj Cepl 2014-11-11 11:20:11 UTC
Created attachment 956241 [details]
File: environ

Comment 6 Matěj Cepl 2014-11-11 11:20:13 UTC
Created attachment 956242 [details]
File: exploitable

Comment 7 Matěj Cepl 2014-11-11 11:20:14 UTC
Created attachment 956243 [details]
File: limits

Comment 8 Matěj Cepl 2014-11-11 11:20:16 UTC
Created attachment 956244 [details]
File: maps

Comment 9 Matěj Cepl 2014-11-11 11:20:17 UTC
Created attachment 956245 [details]
File: open_fds

Comment 10 Matěj Cepl 2014-11-11 11:20:18 UTC
Created attachment 956246 [details]
File: proc_pid_status

Comment 11 Matěj Cepl 2014-11-11 11:20:20 UTC
Created attachment 956247 [details]
File: var_log_messages

Comment 12 Matěj Cepl 2014-11-11 11:21:02 UTC
Created attachment 956248 [details]
File: sosreport.tar.xz

Comment 14 Matěj Cepl 2014-11-12 12:46:59 UTC
Created attachment 956731 [details]
better backtrace

Better backtrace (hopefully)

Comment 15 Matěj Cepl 2014-12-18 22:03:00 UTC
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.

Comment 18 Nils Philippsen 2016-05-27 11:58:27 UTC
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?

Comment 19 Matěj Cepl 2016-06-20 16:57:11 UTC
(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.

Comment 20 Nils Philippsen 2016-07-29 16:56:33 UTC
Thanks for the update!