simple-scan crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
simple-scan (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Occurred while scanning a page, after I had cancelled and restarted the scan.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: simple-scan 3.1.91-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Tue Sep 20 12:58:57 2011
DriverPackageVe
libsane 1.0.22-2ubuntu1
libsane-extras N/A
hplip 3.11.7-0ubuntu5
hpoj N/A
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
ProcCmdline: simple-scan
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x415a4a: movl $0x1,0x18(%rax)
PC (0x00415a4a) ok
source "$0x1" ok
destination "0x18(%rax)" (0xaaaaaaaaaaaa
SegvReason: writing unknown VMA
Signal: 11
SimpleScanLog:
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 oneiric on 2011-09-12 (7 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
dmi.bios.date: 04/04/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.05
dmi.board.name: 30CC
dmi.board.vendor: Quanta
dmi.board.version: 79.10
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dv6500 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Thank you for taking the time to report this crash and helping to make Ubuntu 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.