simple-scan crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
simple-scan (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Open app, wait to find scanner: HP 8740, app closes, and does not find HP 8740 scanner.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: simple-scan 3.31.90-0ubuntu2
ProcVersionSign
Uname: Linux 4.19.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 10 18:04:03 2019
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2019-02-10 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190210)
MachineType: HP HP Pavilion Notebook
ProcCmdline: simple-scan
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x55696844c844: mov 0x18(%rbp),%rcx
PC (0x55696844c844) ok
source "0x18(%rbp)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SimpleScanLog:
SourcePackage: simple-scan
StacktraceTop:
?? ()
?? ()
?? ()
g_closure_invoke () from /lib/x86_
?? () from /lib/x86_
Title: simple-scan crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 06/22/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.48
dmi.board.
dmi.board.name: 8217
dmi.board.vendor: HP
dmi.board.version: 83.72
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.
dmi.modalias: dmi:bvnInsyde:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Notebook
dmi.product.sku: Z7Y92UA#ABA
dmi.product.
dmi.sys.vendor: HP
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 #1814581, 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.