Hide Forgot
I wanted to test printer configuration OOTB with Fedora 20. So I booted up a VM that's bridged to my local network with the F20 Final TC5 Desktop live x86_64 image, ran the control center, and opened the printer applet. It auto-detected the printer (an HP M1212nf connected to the network) and offered to set it up - awesome. I set it up, and tried to print a test page. It failed, as I kinda expected, and GNOME even showed a pop-up that told me it needed a proprietary plugin and I should run hp-plugin. So far, so fairly awesome. But after multiple attempts to install the plugin, attempts to print to the printer still fail with: hpcups[3592]: print/hpcups/HPCupsFilter.cpp 457: m_Job initialization failed with error = 48 which, according to teh googles, is the typical error you see when the plugin's not installed. I ran hp-plugin multiple times - in graphical and non-graphical mode. I even directly downloaded and launched http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-3.13.11-plugin.run . hp-diagnose_plugin reports: 'Device Plugin is already installed' When I ran hp-plugin in debug mode, I did see this message right before "Plug-in installation successful": hp-plugin[3608]: debug: Device URI dnssd://HP%20LaserJet%20Professional%20M1212nf%20MFP._pdl-datastream._tcp.local/ is invalid/unknown hp-plugin[3608]: debug: Exception: 4 (Unknown/invalid device-uri field) lpstat -t reports: [root@localhost liveuser]# lpstat -t scheduler is running no system default destination device for HP-LaserJet-Professional-M1212nf-MFP: dnssd://HP%20LaserJet%20Professional%20M1212nf%20MFP._pdl-datastream._tcp.local/ HP-LaserJet-Professional-M1212nf-MFP accepting requests since Fri 06 Dec 2013 05:07:27 PM EST printer HP-LaserJet-Professional-M1212nf-MFP is idle. enabled since Fri 06 Dec 2013 05:07:27 PM EST Rendering completed HP-LaserJet-Professional-M1212nf-MFP-6 liveuser 1024 Fri 06 Dec 2013 05:07:24 PM EST
If you use system-config-printer to change the device URI to the HPLIP one (starting with hp:/), does hp-plugin then work correctly?
FWIW the D-Bus GroupPhysicalDevices method call that system-config-printer provides returns device URIs in preference order, most preferred first.
Still valid with a fully up-to-date F20. And yes, using s-c-p to replace the dnssd:// URI with this one copied from the host system: hp:/net/HP_LaserJet_Professional_M1212nf_MFP?ip=192.168.1.11 brings the printer to life and spits out the test page.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.