simple-scan crashed with SIGABRT in raise()

[Pete Graner]

While scanning some documents, simple scan told me it could not connect to the scanner, after scanning two sheets. I clicked change scanner, and reselected my original scanner. Then I clicked scan all sheets from feeder to try and finish scanning the last remaining page. Then simple scan crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: simple-scan 3.2.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 1 12:24:29 2012
DriverPackageVersions:
 libsane 1.0.22-7ubuntu1
 libsane-extras N/A
 hplip 3.11.12-2
 hpoj N/A
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/simple-scan
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: simple-scan
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-12-generic root=UUID=96746e8e-9178-466f-b223-ddebb6a670b4 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: simple-scan
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 free () from /lib/x86_64-linux-gnu/libc.so.6
Title: simple-scan crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
dmi.bios.date: 07/15/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: LCPBG10J.86A.0548.2011.0715.2025
dmi.board.asset.tag: Base Board Asset Tag
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrLCPBG10J.86A.0548.2011.0715.2025:bd07/15/2011:svn:pn:pvr:rvn:rn:rvr:cvn:ct3:cvr:

[Apport retracing service (apport)]

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 #900289, 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.