simple-scan crashed with SIGSEGV in make_cache_block()

Bug #1760086 reported by Franck
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sane-backends (Ubuntu)

Bug Description

Segfaults when trying to scan a document in Photo mode. Text mode works.

Scanner is a all-in-one Brother J4625DW.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: simple-scan 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Mar 30 13:58:18 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/simple-scan
MachineType: LENOVO 2353CTO
ProcCmdline: simple-scan
 PATH=(custom, user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
 Segfault happened at: 0x7ffb702a214c <make_cache_block+811>: movzbl 0x3ec(%rax),%eax
 PC (0x7ffb702a214c) ok
 source "0x3ec(%rax)" (0x000003ec) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: simple-scan
 make_cache_block () from /usr/lib/x86_64-linux-gnu/sane/
 read_scanned_data () from /usr/lib/x86_64-linux-gnu/sane/
 PageScan () from /usr/lib/x86_64-linux-gnu/sane/
 sane_brother4_read () from /usr/lib/x86_64-linux-gnu/sane/
 ?? ()
Title: simple-scan crashed with SIGSEGV in make_cache_block()
UpgradeStatus: Upgraded to bionic on 2018-01-22 (67 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo 09/27/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ETA9WW (2.69 )
dmi.board.asset.tag: Not Available 2353CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: ThinkPad T430s 2353CTO
dmi.product.version: ThinkPad T430s
dmi.sys.vendor: LENOVO

Revision history for this message
Franck (alci) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

 #0 0x00007ffb702a214c in ?? ()
 #1 0x000000ff00000000 in ?? ()
 #2 0x00007ffb60202960 in ?? ()
 #3 0x00000000000000ff in ?? ()
 #4 0x0000000000000000 in ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Franck (alci) wrote :

Happens in Simple-scan, but probably has to do with sane-backends

affects: simple-scan (Ubuntu) → sane-backends (Ubuntu)
information type: Private → Public
Revision history for this message
Forrest Voight (forrestv) wrote :

(Reposted here because some people aren't subscribed to #1769126. Sorry if you get a duplicate notification.)

I looked into this issue at length and posted a write-up here:

The gist of it is that setting up a Brother printer with an invalid model name (e.g. "MFCL5900DW" instead of "MFC-L5900DW") can cause crashes in some cases (namely simple-scan in photo mode).


* (optional) Check "/opt/brother/scanner/brscan4/brsanenetdevice4.cfg" to see if the configured device has an invalid model name (by cross-referencing with the output of "brsaneconfig4 -q")
* Delete /opt/brother/scanner/brscan4/brsanenetdevice4.cfg
* Re-add the scanner with a command similar to "brsaneconfig4 -a name=MFC-L5900DW model=MFC-L5900DW nodename=BRN3C2AF4738657"

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.