HP PSC 1315 - simple scan closes after scanning third time

[Gusrubin]

Binary package hint: simple-scan

I have a "HP PSC 1315 all - in - one" and it works normally to second time that I do scanning, the third time the application closes. If I run open again it works two more time and happens the same.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: simple-scan 2.32.0.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Sun Jun 5 13:17:02 2011
DriverPackageVersions:
 libsane 1.0.22-2ubuntu1
 libsane-extras N/A
 hplip 3.11.1-2ubuntu2
 hpoj N/A
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
Lsusb:
 Bus 002 Device 005: ID 03f0:3f11 Hewlett-Packard PSC-1315/PSC-1317
 Bus 002 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
 Bus 002 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System name
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=490cc94b-0250-4cc9-8ba7-5f51bd1a41b1 ro quiet splash vt.handoff=7
SimpleScanLog:

SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/06/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS A8N-SLI ACPI BIOS Revision 1604
dmi.board.name: A8N-SLI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIACPIBIOSRevision1604:bd06/06/2006:svnSystemmanufacturer:pnSystemname:pvr1.XX:rvnASUSTeKComputerINC.:rnA8N-SLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System name
dmi.product.version: 1.XX
dmi.sys.vendor: System manufacturer

[Gusrubin (gusrubin)]

** (simple-scan:4004): WARNING **: scanner.vala:1098: Unable to start device: Device busy
*** glibc detected *** simple-scan: double free or corruption (!prev): 0x0000000001bd6000 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x78a96)[0x7f7905e7fa96]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7f7905e83d7c]
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0(+0x5ac7)[0x7f790727eac7]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_unref+0x150)[0x7f7906d7b9f0]
/usr/lib/libgtk-3.so.0(+0x135ff4)[0x7f7907b8bff4]
/usr/lib/libgtk-3.so.0(+0x1366a3)[0x7f7907b8c6a3]
/usr/lib/libgtk-3.so.0(+0x152e58)[0x7f7907ba8e58]
/usr/lib/libgtk-3.so.0(+0x27e9f0)[0x7f7907cd49f0]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xaa)[0x7f7906d78ffa]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x20e5f)[0x7f7906d8ae5f]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x623)[0x7f7906d94483]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82)[0x7f7906d94852]
/usr/lib/libgtk-3.so.0(+0x29012a)[0x7f7907ce612a]
/usr/lib/libgtk-3.so.0(gtk_container_propagate_draw+0x21e)[0x7f7907b24ace]
/usr/lib/libgtk-3.so.0(+0x8bd34)[0x7f7907ae1d34]
/usr/lib/libgtk-3.so.0(+0xcd4cc)[0x7f7907b234cc]
/usr/lib/libgtk-3.so.0(+0x152e58)[0x7f7907ba8e58]
/usr/lib/libgtk-3.so.0(+0x27e9f0)[0x7f7907cd49f0]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xaa)[0x7f7906d78ffa]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x20e5f)[0x7f7906d8ae5f]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x623)[0x7f7906d94483]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82)[0x7f7906d94852]
/usr/lib/libgtk-3.so.0(+0x29012a)[0x7f7907ce612a]
/usr/lib/libgtk-3.so.0(gtk_container_propagate_draw+0x21e)[0x7f7907b24ace]
/usr/lib/libgtk-3.so.0(+0xcd4cc)[0x7f7907b234cc]
/usr/lib/libgtk-3.so.0(+0x95b0f)[0x7f7907aebb0f]
/usr/lib/libgtk-3.so.0(+0x152e58)[0x7f7907ba8e58]
/usr/lib/libgtk-3.so.0(+0x27e9f0)[0x7f7907cd49f0]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xaa)[0x7f7906d78ffa]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x20e5f)[0x7f7906d8ae5f]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x623)[0x7f7906d94483]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x82)[0x7f7906d94852]
/usr/lib/libgtk-3.so.0(+0x29012a)[0x7f7907ce612a]
/usr/lib/libgtk-3.so.0(gtk_container_propagate_draw+0x21e)[0x7f7907b24ace]
/usr/lib/libgtk-3.so.0(+0x8bd34)[0x7f7907ae1d34]
/usr/lib/libgtk-3.so.0(+0xcd4cc)[0x7f7907b234cc]
/usr/lib/libgtk-3.so.0(+0x152e58)[0x7f7907ba8e58]
/usr/lib/libgtk-3.so.0(+0x27e9f0)[0x7f7907cd49f0]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xaa)[0x7f7906d78ffa]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x20e5f)...

[Michael Nagel (nailor)]

Does it happen EVERY time?
Does it ALWAYS happen with the third page?
Do you scan one page, wait until it finished and scan the next page after that or is there a chance you send new commands to the scanner when it is still working?
What happens if you use xsane?

[Gusrubin (gusrubin)]

Does it happen EVERY time?
- Yes. (with the third page).

Does it ALWAYS happen with the third page?
- Yes.

Do you scan one page, wait until it finished and scan the next page after that or is there a chance you send new commands to the scanner when it is still working?
What happens if you use xsane?
- I scan one page, wait until it finished and scan the next page, in a same job. There is no new commands during scanning process (at least not user commands).
I never used xsane, i dont know if this happens.

Do you want I do another kind of test?

Thanks.

[Michael Nagel (nailor)]

Yes, please try xsane, that is another program using the same backend as simple-scan. If that works, it is a workaround for you and proof for us that the problem is within simple-scan. If it does not work, it is probably a problem in the backend (hplip/libsane) and we should search there.

[Gusrubin (gusrubin)]

Hi Michael, I did the test with xsane, the fail doesn't occur.
But I was wrong when I answered to you that there was no new commands sending to the scanner when it is still working, the correct answer is Yes. I'm scanning pictures, I need to scan only the length of pic, then I click the stop button when the process reaches the lenght that I want and I click scan button again for a new pic.
I realized that no matter whether or not I save the job before start a new scan, the application crashes at third time I try to start scan.

I saved the log, here is:

--------

gustavo@pcgus:~$ simple-scan

(simple-scan:4277): Gtk-WARNING **: Unknown property: GtkDialog.has-separator

(simple-scan:4277): Gtk-WARNING **: Unknown property: GtkDialog.has-separator

** (simple-scan:4277): WARNING **: scanner.vala:1098: Unable to start device: Device busy
*** glibc detected *** simple-scan: free(): invalid pointer: 0x0000000001eb99d0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x78a96)[0x7ff49048ca96]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7ff490490d7c]
/usr/lib/sane/libsane-hpaio.so.1(sane_hpaio_close+0xa4)[0x7ff47c1a8354]
/usr/lib/libsane.so.1(sane_dll_close+0x24)[0x7ff490e7d824]
simple-scan[0x421549]
simple-scan[0x4215ba]
simple-scan[0x4221d9]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x6a2b6)[0x7ff4910eb2b6]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7efc)[0x7ff4907baefc]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff4904f589d]
======= Memory map: ========
00400000-0043c000 r-xp 00000000 08:01 2509785 /usr/bin/simple-scan
0063b000-0063c000 r--p 0003b000 08:01 2509785 /usr/bin/simple-scan
0063c000-0063d000 rw-p 0003c000 08:01 2509785 /usr/bin/simple-scan
01b04000-0216e000 rw-p 00000000 00:00 0 [heap]
7ff470000000-7ff470021000 rw-p 00000000 00:00 0
7ff470021000-7ff474000000 ---p 00000000 00:00 0
7ff47580d000-7ff475822000 r-xp 00000000 08:01 921496 /lib/x86_64-linux-gnu/libgcc_s.so.1
7ff475822000-7ff475a21000 ---p 00015000 08:01 921496 /lib/x86_64-linux-gnu/libgcc_s.so.1
7ff475a2...

[Launchpad Janitor (janitor)]

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