Bug 888 - HP all-in-one network scanner is not detected
Summary: HP all-in-one network scanner is not detected
Status: RESOLVED DUPLICATE of bug 792
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-19 07:20 CEST by Stefano Negro
Modified: 2011-05-25 22:44 CEST (History)
2 users (show)

See Also:
Source RPM: system-config-printer
CVE:
Status comment:


Attachments

Description Stefano Negro 2011-04-19 07:20:32 CEST
Description of problem:
unable to connect wifi all-in-one HP Photosmart C4580.
Hplip is configuring and using correctly the wifi device.

Version-Release number of selected component (if applicable):
Drakscanner on Beta 1, cauldron

How reproducible:
Open Drakscanner and try to auto-detect for new printer

Steps to Reproduce:
1.Open Drakscanner
2.Push "search for new scanner"
3.No scanner Detected
Comment 1 Yann Ciret 2011-04-19 07:36:04 CEST
Hello,

I think it is a duplicate of my bug 792
(https://bugs.mageia.org/show_bug.cgi?id=792)

Try to install lib64sane-hpaio1 with urpmi and after add a new printer with HPLIP

CC: (none) => mageia

Comment 2 Stefano Negro 2011-05-25 18:52:43 CEST
Done with RC.
Loaded lib64sane-hpaio1, then added printer and also scanner it's available and functioning.
This is a workaround. For Normal user it's quite impossible to know. 
It'll be better to load during installation this HP lib, it's very common.
Angelo Naselli 2011-05-25 21:53:23 CEST

CC: (none) => anaselli
Summary: Drakconnect => HP all-in-one network scanner is not detected

Comment 3 Ahmad Samir 2011-05-25 22:44:46 CEST
This is a duplicate of 792, which is already fixed, hplip now pulls libsane-hpaio1 as a requires.

*** This bug has been marked as a duplicate of bug 792 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Source RPM: (none) => system-config-printer


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