simple-scan crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
simple-scan (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Scanner failed to power up for some reason (it's blacklisted from USB power saving since that was what made it fail at some time before). The SIGSEGV occured afterwards.
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: simple-scan 3.30.0-1
ProcVersionSign
Uname: Linux 4.18.0-7-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Sep 16 19:04:18 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2011-10-14 (2529 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
MachineType: LENOVO 4238A15
ProcCmdline: simple-scan
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f121a443d1a: mov 0x10(%rax),%edx
PC (0x7f121a443d1a) ok
source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%edx" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: simple-scan
StacktraceTop:
() at /usr/lib/
sane_avision_
sane_dll_
()
()
Title: simple-scan crashed with SIGSEGV
UpgradeStatus: Upgraded to cosmic on 2018-07-30 (48 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare
dmi.bios.date: 06/04/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 83ET82WW (1.52 )
dmi.board.
dmi.board.name: 4238A15
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad T420
dmi.product.name: 4238A15
dmi.product.
dmi.sys.vendor: LENOVO
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1717645, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.