Simple Scan no longer detects the scanner after aborting a scan

Bug #852999 reported by Alex Francisco Bustos Pinzon
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Simple Scan
Confirmed
Undecided
Unassigned
simple-scan (Ubuntu)
Triaged
Low
Unassigned
Nominated for Trusty by Alberto Salvia Novella
Nominated for Xenial by Alberto Salvia Novella
Nominated for Yakkety by Alberto Salvia Novella

Bug Description

I have an AIO Epson Stylus Office tx300f mutifunctional printer who has scanning function.

I was scanning a text. The Simple Scan software was working correctly so, when I ordered to stop the scan, effectively the scanner stopped. But the reader-bar of the scanner didn't move to idle position.

When I tried to do a new scan, Simple Scan stopped. Then it began loading the preview for an undefined time, until it appears a message telling that no scanner is available:

(https://launchpadlibrarian.net/284606065/Screenshot.png)

WORKAROUND: Use xsane.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: simple-scan 2.32.0.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Sat Sep 17 23:35:38 2011
DriverPackageVersions:
 libsane 1.0.22-2ubuntu1
 libsane-extras N/A
 hplip 3.11.1-2ubuntu2
 hpoj N/A
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 003: ID 04b8:0848 Seiko Epson Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard Presario F500 (GB124LA#ABM)
ProcEnviron:
 LANGUAGE=es:en
 LANG=es_CO.UTF-8
 LC_MESSAGES=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=b95299d5-8005-439f-af0d-2b98286a58ed ro quiet splash vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/24/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.20
dmi.board.name: 30D3
dmi.board.vendor: Quanta
dmi.board.version: 65.3A
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.20:bd03/24/2010:svnHewlett-Packard:pnPresarioF500(GB124LA#ABM):pvrRev1:rvnQuanta:rn30D3:rvr65.3A:cvnQuanta:ct10:cvrN/A:
dmi.product.name: Presario F500 (GB124LA#ABM)
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Alex Francisco Bustos Pinzon (alexra-5) wrote :
Michael Nagel (nailor)
tags: added: scanner-crash
Michael Nagel (nailor)
summary: - epson scanner crashes when trying to take a new scan, after a voluntary
- cancelled scan
+ Epson Stylus Office tx300f crashes after aborting one scan and starting
+ another
Revision history for this message
Michael Nagel (nailor) wrote : Re: Epson Stylus Office tx300f crashes after aborting one scan and starting another

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: New → 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
Alberto Salvia Novella (es20490446e) wrote :

I tested this on two different old HP scanners and this happens on both. I I abort an scanning, the application can no longer detect the scanner. Depending on the model Simple Scan can hang or not.

It doesn't happen in a modern HP multifunction.

tags: added: trusty vivid
Changed in simple-scan (Ubuntu):
status: Expired → Confirmed
summary: - Epson Stylus Office tx300f crashes after aborting one scan and starting
- another
+ Simple Scan crashes after aborting one scan and starting another
Changed in simple-scan (Ubuntu):
importance: Undecided → Medium
Changed in simple-scan:
status: New → Confirmed
Changed in simple-scan (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
penalvch (penalvch) wrote : Re: Simple Scan crashes after aborting one scan and starting another

Alex Francisco Bustos Pinzon / Alberto Salvia Novella, to see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

no longer affects: simple-scan (Ubuntu)
affects: simple-scan → simple-scan (Ubuntu)
Changed in simple-scan (Ubuntu):
status: Confirmed → Incomplete
importance: Undecided → Low
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

I'll tell you before 2016-09-18.

Changed in simple-scan (Ubuntu):
status: Incomplete → In Progress
assignee: nobody → Alberto Salvia Novella (es20490446e)
Revision history for this message
penalvch (penalvch) wrote :

Alberto Salvia Novella, if you personally would be releasing a patch towards this soon, then In Progress and assigning this to you would make sense here as per https://wiki.ubuntu.com/Bugs/Status .

Changed in simple-scan (Ubuntu):
assignee: Alberto Salvia Novella (es20490446e) → nobody
status: In Progress → Incomplete
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

@ Christopher M. Penalver

It really doesn't matter, as the idea is simply to signal that the bug isn't ready to be worked on.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Tested with Hewlett-Packard ScanJet 4570c (ID 03f0:1305).

After the bug Simple Scan is no longer able to detect the Scanner, even by closing and reopening the application. On the other hand the bug doesn't happen in xsane, and the scanner is even detectable after Simple Scan is no longer able to detect the Scanner.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

The bug is triggered by gtk_event_controller_reset failing to reset the scanner.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

This is how it looks like.

tags: added: xenial
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

It also affects Ubuntu Daily.

tags: added: yakety
Changed in simple-scan (Ubuntu):
status: Incomplete → Triaged
importance: Low → Medium
importance: Medium → Low
tags: added: yakkety
removed: yakety
Changed in simple-scan:
status: New → Confirmed
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Alberto Salvia Novella, I'm not sure you have the same bug as the original reporter. This report is about how "Simple Scan crashes after aborting one scan and starting another".

Does your Simple Scan application crash performing the above?

Changed in simple-scan (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

@ Christopher M. Penalver

Yes, doing exactly the same as above and with exactly the same symptoms. Just that in my scanner model the bar moves to the idle position.

My latest comments were only to explain extra symptoms I see.

Changed in simple-scan (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
penalvch (penalvch) wrote :

Alberto Salvia Novella, I think the title of the this report is not reflective of the original problem. From what I see, Simple Scan doesn't actually crash, but has a standard communication issue with the scanner. Hence, Simple Scan doesn't crash, or there would be a file in /var/crash. I'll adjust the title to reflect what is actually being experienced.

Revision history for this message
penalvch (penalvch) wrote :

Original reporter provided screenshot.

summary: - Simple Scan crashes after aborting one scan and starting another
+ Simple Scan notes "Failed to scan" after aborting one scan and starting
+ another
description: updated
summary: - Simple Scan notes "Failed to scan" after aborting one scan and starting
- another
+ Simple Scan no longer detects the scanner after aborting a scan
description: updated
penalvch (penalvch)
description: updated
Revision history for this message
Marko Indaco (mint-marko) wrote :

Hi all, If can help I experience right now tha same issue. As said by Christopher M. Penalver (penalvch) in post #15 this don't seems a crash indeed some fuctions work anyway, but, in my case, I got only the classic red upper-popup that say there's a communication problem with the source.
Then, just to try, I open Xsane and also that was link-broken to the scanner, so I try to scan usign Master PDF Editor 4 but in this case the scanning process was working.
Hope can help.

Regards

Printer: Epson WF-2510
Linux Mint 18.2 (Cinnamon 64bit) - RAM: 4 Giga - MoBo: G31MX Series - CPU: Intel Core 2 Quad CPU Q9400 @ 2.66GHz - GPU: GeForce 9500 GT - Audio: NM10/ICH7

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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