simple-scan crashed with SIGABRT in __libc_message()

Bug #900289 reported by Christopher Kyle Horton
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
HPLIP
New
Undecided
Unassigned
hplip (Ubuntu)
New
Medium
Unassigned

Bug Description

Simple Scan crashed while trying to reproduce bug 532812. Steps followed:

1. Start Simple Scan. Check that it is set to scan in Photo mode.
2. Start a scan, then shortly after it begins filling in the image hit the cancel button.
3. Switch the scanning mode to Text.
4. Press the Scan button again, and again cancel the scan partway through.
5. Press the button for setting up a new document. Select "Discard all changes" in the dialog that pops up.
6. Press the Scan button again. Simple Scan will now crash and close.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: simple-scan 3.2.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-2.6-generic 3.2.0-rc3
Uname: Linux 3.2.0-2-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Dec 5 08:33:00 2011
DriverPackageVersions:
 libsane 1.0.22-2ubuntu2
 libsane-extras N/A
 hplip 3.11.10-1ubuntu1
 hpoj N/A
ExecutablePath: /usr/bin/simple-scan
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
MachineType: Gigabyte Technology Co., Ltd. M61PME-S2P
ProcCmdline: simple-scan
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-generic root=UUID=2d55fd3e-d932-47b9-abd6-a1fde1ec0453 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 cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 11/03/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: M61PME-S2P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd11/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnM61PME-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM61PME-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: M61PME-S2P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f584d82f098 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=3, str=0x7f584d82c0af "free(): invalid pointer", ptr=<optimized out>) at malloc.c:6283
 __GI___libc_free (mem=<optimized out>) at malloc.c:3738
 hpaioPmlDeallocateObjects (hpaio=<optimized out>) at scan/sane/hpaio.c:604
 sane_hpaio_close (handle=0x16b0520) at scan/sane/hpaio.c:2347

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in simple-scan (Ubuntu):
importance: Undecided → Medium
summary: - simple-scan crashed with SIGABRT in raise()
+ simple-scan crashed with SIGABRT in __libc_message()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in simple-scan (Ubuntu):
status: New → Confirmed
visibility: private → public
Revision history for this message
Michael Nagel (nailor) wrote :

==============================================================
Hi there,

thank you for filing this bug and showing your interest in Simple Scan!

This seems to be a Hardware Issue, i.e. Simple Scan does not support your scanner perfectly -- or possibly not at all.

Unfortunately such problems happen more often then they should, and while it might indeed be a problem with Simple Scan, in our experience, most of the time it is not.
This is why we prepared a check-list at [1] that will let you find out whether or not it really is a problem with Simple Scan and what your options are in either case.

Please read that list and tell us how you decided to proceed. I will set this bug to "Incomplete", so a friendly robot will expire this bug in 60 days if you do not respond. However, we would really prefer to hear back from you!

Best Regards
Michael

[1] https://help.ubuntu.com/community/SimpleScanHardwareIssues
==============================================================

Changed in simple-scan (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for simple-scan (Ubuntu) because there has been no activity for 60 days.]

Changed in simple-scan (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Robert Ancell (robert-ancell) wrote :

This seems to be related to bug 930914 which is the top detected problem for Ubuntu 12.04 users with simple-scan (see https://errors.ubuntu.com/?release=Ubuntu%2012.04&package=simple-scan&period=month)

affects: simple-scan (Ubuntu) → hplip (Ubuntu)
Changed in hplip (Ubuntu):
status: Expired → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.