simple-scan crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
simple-scan (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
after Kernel update 3.2.0.17
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: simple-scan 3.2.1-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Feb 19 22:02:54 2012
DriverPackageVe
libsane 1.0.22-7ubuntu1
libsane-extras N/A
hplip 3.12.2-1
hpoj N/A
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120126)
MachineType: HP Pavilion 061 EX259AA-ABA s7520n
ProcCmdline: simple-scan
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x415a8a: movl $0x1,0x18(%rax)
PC (0x00415a8a) ok
source "$0x1" ok
destination "0x18(%rax)" (0xaaaaaaaaaaaa
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: simple-scan
StacktraceTop:
?? ()
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_
Title: simple-scan crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2012-02-11 (8 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 03/14/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.04
dmi.board.name: Opal
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.02
dmi.chassis.type: 3
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: EX259AA-ABA s7520n
dmi.product.
dmi.sys.vendor: HP Pavilion 061
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 #843361, 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.