simple-scan crashed with SIGSEGV in sane_xerox_mfp_control_option()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
simple-scan (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: simple-scan
beowulf@
Description: Ubuntu lucid (development branch)
Release: 10.04
beowulf@
simple-scan:
Installiert: 0.9.10-0ubuntu4
Kandidat: 0.9.10-0ubuntu4
Versions-Tabelle:
*** 0.9.10-0ubuntu4 0
500 http://
100 /var/lib/
Just tried to scan a page on my Samsung SCX-4200 MFP.
Simple-Scan crashed.
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: simple-scan 0.9.10-0ubuntu4
ProcVersionSign
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Mon Apr 12 08:04:00 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
MachineType: MICRO-STAR INTERNATIONAL CO., LTD U-100
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: simple-scan
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x593ca91 <sane_xerox_
PC (0x0593ca91) ok
source "(%ecx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SimpleScanLog:
SourcePackage: simple-scan
StacktraceTop:
sane_xerox_
sane_dll_
sane_control_
?? ()
?? ()
Title: simple-scan crashed with SIGSEGV in sane_xerox_
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/16/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.3
dmi.board.
dmi.board.name: U-100
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: Ver.001
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: U-100
dmi.product.
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
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 #551956, 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.