Comment 16 for bug 1989508

(In reply to Brian J. Murrell from comment #5)
> Indeed, I don't think anyone thinks you can fix the remote server issue.
> There are alternative solutions that you, RH, as the packager can apply
> though. Your proposed solution:
>
> > I'll create a bash script which will be run under 'hp-plugin' command and it will do the same thing.
>
> is one solution. Including the plugin from
> https://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/ in
> hplip (or an hp-plugin subpackage) is another.

Unfortunately the plugin has a license incompatible with open source licenses which can be in the official repos in Fedora, so I cannot ship it in a subpackage (that was the reason why hp-plugin script existed).

IIRC Rathann (one hplip user from community) somehow packaged the plugin, but I'm not sure whether he shares it via RPMFusion or uses it locally...

> And yet another is to host
> the http://hplip.sourceforge.net/plugin.conf on a RH controlled server and
> update the path during the package build.

When I look into the previous contents of plugin.conf - https://web.archive.org/web/20220420014143/http://hplip.sourceforge.net/plugin.conf - IMHO I cannot guess all the entries there to fully replace this file :(

>
> In any case, whichever solution you choose I am sure everyone will be
> grateful for your efforts!

Either way, it would be great if everyone who hit this issue found out whether they really need a plugin for their printing/scanning operations - the plugin is needed only if your device is quite old (about more than 10 years old in case of network printing, about more than 7 years old in case of USB printing, about more than 5-7 years old in terms of scanning) and does not support a driverless methods or if driverless solutions don't match your criteria or don't work due some bugs.

For example, I have HP LaserJet M1536dnf (purchased in 2011, made in 2010) at home, which is capable of driverless printing via network (wifi and ethernet), prints with classic driver via USB and plugin is needed only for scanning.

More info about this you can find here ( for printing https://docs.fedoraproject.org/en-US/quick-docs/cups-useful-tricks/#_how_to_find_out_whether_my_printer_is_capable_of_driverless_printing , for scanning https://docs.fedoraproject.org/en-US/quick-docs/cups-useful-tricks/#_how_to_find_out_my_multifunction_device_or_standalone_scanner_is_capable_of_driverless_scanning ) and in the following paragraphs. In case you encounter some problems/errors when setting the driverless scanning/printing up (if you find out the device should support it), it would be great if you filed a bugzilla to a respective component (in case you have problems with printing from a specific application - file a bug on it, in case the problem is generic - file a bug on CUPS).

Regarding the fix, I'll be back in the office next week, so I will be working on the official solution since next week. In the meantime, manual download of plugin from the link https://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/ and 'sh <plugin-file>' should work as a workaround.