Red Hat Bugzilla – Bug 500480
HP LaserJet P1005 isn't plug'n'play; configuration requires expert guidance
Last modified: 2009-11-09 08:19:39 EST
Description of problem:
I have a use case / user story which obviously should work, and that it doesn't is in my opinion a bug: When attaching a HP LaserJet P1005 USB printer then the plug'n'play system should work and just make the printer work.
My experience was that a printer was created, but it didn't work and print jobs just disappeared without any usable hints in /var/log.
It turns out that the essential part that was missing was that I had to run hp-setup and let it download the driver and configure the printer. So I guess that my request is that hp-setup should be run automatically.
I file this issue on cups because I know that cups is a very central component of Fedora printing. The problem might however have to be solved somewhere else.
Version-Release number of selected component (if applicable):
The essential part is in fact a proprietary plugin for HPLIP.
There is no entirely free driver for the P1005. HPLIP requires a proprietary plugin, and foo2xqx seems like it might contain patented algorithms.
With Fedora, which has deep roots in free software, automatically downloading proprietary parts is not something we want to do.
Ok, thanks for the facts. I thought HPLIP downloaded firmware. But hplip _is_ in Fedora, and thus I expect it to be fully supported and integrated and plug'n'play.
A clear indication (message or log) that "this printer is not supported" or "no driver found" would be an OK (but sad) resolution. But obviusly it would be better if users were helped to make it work.
FWIW foo2xqx from Some Other Repo did not work for me. But if that is the way to go then I assume that could be solved.
I don't see foo2xqx on http://fedoraproject.org/wiki/ForbiddenItems or anywhere else in bz - has Legal looked at it and made a final verdict?
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
*** Bug 497091 has been marked as a duplicate of this bug. ***
This is resolved by the fix for bug #531330 in conjunction with the fix for bug #531872.
*** This bug has been marked as a duplicate of bug 531330 ***