Bug 8183 - Unable to setup the scanner on a HP Photosmart 5524
Summary: Unable to setup the scanner on a HP Photosmart 5524
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-22 20:02 CET by Pierre Jarillon
Modified: 2013-07-22 22:48 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Pierre Jarillon 2012-11-22 20:02:27 CET
With MCC, the HP Photosmart printer is enabled correctly.
Hpaio, xsane and xsane-gimp are installed.

During the installation of the printer, the recommended type is HP-Photosmart-5510d because the HP 5524 is not listed.
Hp-setup find no scanner and the scanner cannot be used.

As it is not possible to wait Mageia3, an update of the HP software is needed for Mageia2.
Comment 1 Pierre Jarillon 2012-11-22 20:10:18 CET
# scanimage -L
found USB scanner (vendor=0x03f0 [HP], product=0xb111 [Photosmart 5520 series]) at libusb:001:007
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.
Comment 2 Dan Fandrich 2013-07-22 22:48:01 CEST
The HP 5524 isn't listed as a supported scanner 
http://www.sane-project.org/sane-mfgs.html#Z-HEWLETT-PACKARD  Most of the Photosmart series are listed there explicity as "Unsupported". Unfortunately, if a device isn't supported by the upstream project, there's nothing we can do in the distribution to overcome that. I suggest looking at the Reporting Unsupported Scanners and Adding more information section of http://www.sane-project.org/contrib.html and contacting the SANE project with the information you have on the scanner. If an existing driver can't be modified, and you have lots of patience, you may be able to find a sympathetic developer and help him to write a new driver!

Status: NEW => RESOLVED
CC: (none) => dan
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.