Bug 11644

Summary:	xsane gets stuck at scanning for devices
Product:	Mageia	Reporter:	Chris Denice <eatdirt>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	Normal	CC:	nic, wim
Version:	Cauldron
Target Milestone:	Mageia 5
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	xsane-0.998-5.mga4.src.rpm	CVE:
Status comment:

Description Chris Denice 2013-11-11 16:52:16 CET

Description of problem:

When I start xsane, I get the windows:
"scanning for device..."

and nothing else happens. My system is well configured for scanning and used to work with xsane. The scanner is a HP photosmart C5180:


scanimage -L
device `hpaio:/net/Photosmart_C5100_series?ip=192.168.0.14' is a Hewlett-Packard Photosmart_C5100_series all-in-one

and I can scan documents using:
hp-scan


Cheers,
chris.

Reproducible: 

Steps to Reproduce:

Comment 1 Manuel Hiebel 2013-12-22 13:13:21 CET

iirc some hp allinone printer are not compatible with the sane protocol

Comment 2 Chris Denice 2014-01-12 13:20:14 CET

Hi there,
it worked perfectely fine with mga3, so I don't think they drop support for those machines.

I tried "simple-scan" which works fine too. Moreover, in drakconf, when I click on configure scanner, the scanner is also found.

We should try to fix it before mga4. Let me know what I can test.

Cheers,
chris.

Target Milestone: --- => Mageia 4

Comment 3 Chris Denice 2014-10-19 23:24:05 CEST

Could we get this bug fixed for mga5; it still there...

Target Milestone: Mageia 4 => Mageia 5

Comment 4 Chris Denice 2014-10-19 23:26:28 CEST

*** Bug 13496 has been marked as a duplicate of this bug. ***

CC: (none) => wim

Comment 5 Nic Baxter 2015-03-30 02:00:36 CEST

Hi Chris
I have a HP2610 that I have been using for years. I don't scan very often but when I do I use xsane. I have just used it now and it just works. Possibly fixed? Does it work for you?

CC: (none) => nic

Comment 6 Chris Denice 2015-03-31 00:40:29 CEST

Hi sorry for the silence,
just to say that this has been fixed. The issue was certainly the driver in used. Using std network protocal, the scanner is never found (it is on the network). But now, using drakconf -> hardware -> printer, I have a new option which is using hp:// (hplip drivers I suspect) and using them works fine.

Thanks to whoever fixed this!

cheers.

Status: NEW => RESOLVED
Resolution: (none) => FIXED