Bug 1159380 - s-c-p is unable to find appropriate hpijs-driver (HP LJ 400 Color M451dn)
Summary: s-c-p is unable to find appropriate hpijs-driver (HP LJ 400 Color M451dn)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: hplip
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: IEEE1284DeviceIDs
TreeView+ depends on / blocked
 
Reported: 2014-10-31 18:01 UTC by MaxiPunkt
Modified: 2015-01-06 06:17 UTC (History)
2 users (show)

Fixed In Version: hplip-3.14.10-3.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-06 06:14:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description MaxiPunkt 2014-10-31 18:01:57 UTC
Description of problem:

Do have an HP LaserJet 400 Color M451dn, connected o USB-port:
# lsusb | grep Hewlett
Bus 002 Device 006: ID 03f0:0f2a Hewlett-Packard

The printer is supported by hplip > 3.12.2

When turning printer on, s-c-p in systray states correct printer-name and starts searching for appropriate driver (hpijs).
Finally it fails, reporting that no driver could be found, which is installed on my system for sure:
/usr/share/ppd/HP/hp-lj_300_400_color_m351_m451-ps.ppd.gz

Starting s-c-p from console & trying to setup printer manually shows several error-messages:
$ system-config-printer
ERROR:dbus.proxies:Introspect error on :1.203:/org/freedesktop/PackageKit: dbus.exceptions.IntrospectionParserException: Error parsing introspect data: <class 'xml.parsers.expat.ExpatError'>: unbound prefix: line 5, column 4
No ID match for device hp:/usb/HP_LaserJet_400_color_M451dn?serial=CNFF346024:
MFG:Hewlett-Packard;MDL:HP LaserJet 400 color M451dn;DES:HP LaserJet 400 color M451dn;

What's going wrong, here?


Version-Release number of selected component (if applicable):
$ rpm -qa | grep system-config-printer
system-config-printer-libs-1.4.6-1.fc20.noarch
system-config-printer-udev-1.4.6-1.fc20.x86_64
system-config-printer-1.4.6-1.fc20.x86_64

$ rpm -qa | grep hplip
hplip-common-3.14.6-5.fc20.x86_64
hplip-gui-3.14.6-5.fc20.x86_64
hplip-3.14.6-5.fc20.x86_64
hplip-libs-3.14.6-5.fc20.x86_64

$ rpm -qa | grep hpijs
hpijs-3.14.6-5.fc20.x86_64

How reproducible:
Always

Steps to Reproduce:
see above

Actual results:
Unable to find printer-driver.

Expected results:
plug'n'play printer-setup.

Comment 1 Tim Waugh 2014-11-03 11:47:01 UTC
The PPD is missing the attribute required to link it to that particular IEEE 1284 Device ID.

Comment 2 MaxiPunkt 2014-11-03 18:36:20 UTC
Oh, wow - thank you for your fast response.

So is this a bug which must be reported & fixed upstream?
Or is Fedora's hplip-version being patched by someone to get it working?

Would you need further details to do it?

Comment 3 Tim Waugh 2014-11-04 11:49:51 UTC
Ideally it would be fixed upstream, yes:
  https://bugs.launchpad.net/hplip/+bug/802999

In the mean time, we'll fix it in Fedora by applying a patch.

Comment 4 MaxiPunkt 2014-11-04 19:24:05 UTC
Great!

Is there a chance to get this fix into official FC20-updates as well?

Comment 5 Tim Waugh 2014-11-05 09:04:19 UTC
It will be included in the next update when there are sufficient fixes to warrant one, yes.

Comment 6 MaxiPunkt 2014-11-06 22:07:46 UTC
Cool, thanks a lot for your efforts!

Comment 7 MaxiPunkt 2014-11-25 19:05:38 UTC
Today there was an update of hplip (FC20):

$ rpm -qa | grep hplip
hplip-common-3.14.10-1.fc20.x86_64
hplip-libs-3.14.10-1.fc20.x86_64
hplip-3.14.10-1.fc20.x86_64
hplip-gui-3.14.10-1.fc20.x86_64

But s-c-p is still unable to setup my printer automatically - was your fix not included?

Comment 8 Fedora Update System 2014-11-26 07:56:49 UTC
hplip-3.14.10-3.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/hplip-3.14.10-3.fc21

Comment 9 Fedora Update System 2014-11-26 07:57:13 UTC
hplip-3.14.10-3.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/hplip-3.14.10-3.fc20

Comment 10 Fedora Update System 2014-11-27 08:35:51 UTC
Package hplip-3.14.10-3.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing hplip-3.14.10-3.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-15818/hplip-3.14.10-3.fc20
then log in and leave karma (feedback).

Comment 11 MaxiPunkt 2014-12-01 18:26:31 UTC
Sorry, but this does NOT fix the issue:

$ rpm -qa | grep hplip
hplip-common-3.14.10-3.fc20.x86_64
hplip-3.14.10-3.fc20.x86_64
hplip-libs-3.14.10-3.fc20.x86_64
hplip-gui-3.14.10-3.fc20.x86_64

s-c-p still is unable to setup the appropriate driver for my printer automatically, I'm forced to pick it manually.

Starting s-c-p from console & trying to setup printer manually does not show error-messages "No ID match for device" anymore - but still there is one error-message left, as already reported in initial bug-report:

$ system-config-printer
ERROR:dbus.proxies:Introspect error on :1.90:/org/freedesktop/PackageKit: dbus.exceptions.IntrospectionParserException: Error parsing introspect data: <class 'xml.parsers.expat.ExpatError'>: unbound prefix: line 5, column 4


Might this error be related to this bug?

Comment 12 MaxiPunkt 2014-12-01 19:02:58 UTC
Err - now tested with USB-connected printer % conclude the following:
* RJ45-connected printer: s-c-p fails!
* USB-connected printer : s-c-p is successful

Any idea how to fix printer-setup via RJ45-connection?

Comment 13 Tim Waugh 2014-12-03 13:47:24 UTC
(In reply to MaxiPunkt from comment #11)
> $ system-config-printer
> ERROR:dbus.proxies:Introspect error on :1.90:/org/freedesktop/PackageKit:
> dbus.exceptions.IntrospectionParserException: Error parsing introspect data:
> <class 'xml.parsers.expat.ExpatError'>: unbound prefix: line 5, column 4
> 
> 
> Might this error be related to this bug?

No. That's an apper bug, unrelated to this.

(In reply to MaxiPunkt from comment #12)
> Err - now tested with USB-connected printer % conclude the following:
> * RJ45-connected printer: s-c-p fails!
> * USB-connected printer : s-c-p is successful
> 
> Any idea how to fix printer-setup via RJ45-connection?

You mean the printer is connected to the network?

Comment 14 MaxiPunkt 2014-12-03 17:43:29 UTC
(In reply to Tim Waugh from comment #13)
> (In reply to MaxiPunkt from comment #12)
> > Err - now tested with USB-connected printer % conclude the following:
> > * RJ45-connected printer: s-c-p fails!
> > * USB-connected printer : s-c-p is successful
> > 
> > Any idea how to fix printer-setup via RJ45-connection?
> 
> You mean the printer is connected to the network?

Yes, printer can be connected via USB or network (RJ45), and I've now tested both with latest hplip-version (testing):

USB-connection    : s-c-p is successful (thanks to your patch, before it failed)
network-connection: s-c-p still fails

So the reported problem is partially solved.

Comment 15 Tim Waugh 2014-12-08 14:57:23 UTC
If it is working at all, this bug is fixed.

If you are having a problem configuring it using a network connection, that sounds like a different bug. Please open a new one, and make sure to include the relevant information:
https://fedoraproject.org/wiki/How_to_debug_printing_problems#Filing_a_bug_report

Thanks.

Comment 16 MaxiPunkt 2014-12-08 20:14:36 UTC
O.k. then - this bug initially described a problem with USB-connected printer, which was fixed with your patch of hplip, adding printer-ID to ppd-file.

Now I've filled a new bug #1171874 describing the remaining problem with network-connected printer, only.

Comment 17 Fedora Update System 2015-01-06 06:14:00 UTC
hplip-3.14.10-3.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 18 Fedora Update System 2015-01-06 06:17:19 UTC
hplip-3.14.10-3.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.


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