Bug 1932653

Summary:	splix: use a new splix fork
Product:	[Fedora] Fedora	Reporter:	Bruno Wolff III <bruno>
Component:	splix	Assignee:	Zdenek Dohnal <zdohnal>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	bruno, twaugh, zdohnal
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-03-01 07:31:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bruno Wolff III 2021-02-24 20:34:43 UTC

Description of problem:

There appears to be a fork of splix at http://gitlab.com/ScumCoder/splix that has useful driver updates and ppd files. I was able to get my Samsung M2020W working using that repo as a basis for splix (after commenting out some patches) and when setting up the printer using the m2020.ppd ppd file. It might be worth pulling some patches out of that repo. Maybe adding some of the ppds to the foomatic-db once there is driver support.

Comment 1 Zdenek Dohnal 2021-02-25 05:41:32 UTC

Hi Bruno,

thank you for reporting the issue!

I checked your printer manual[1] (hopefully its the same type), and it should support AirPrint - did you try driverless printing[2] with your printer?

If you did, what was the reason you switched back to a driver?

In case you haven't tried the driverless printing yet, please check the manual[3] and try it. The manual is for network device, because IIRC letter 'W' in model name should mean 'wireless', so I send you that - in case it is a USB device, there is a manual for setting driverless USB device too.

To the issue itself:
Printer drivers are deprecated since 2010, substituted by Airprint, Mopria, IPP everywhere standards - most devices newer than 2010 supports at least AirPrint, so if you have a device bought in 2010 and later, you don't need any drivers if you set it up for driverless printing.
So I will not add more new drivers, if AirPrint works correctly or can be fixed for that device. The classic drivers will stay there to support older non-driverless devices until they will be encapsulated in printer applications[4].

=========================================================================================
To sum it up:
Would you mind trying the driverless printing with your device?

Thank you in advance!




[1] http://h10032.www1.hp.com/ctg/Manual/c05790048.pdf
[2] https://fedoraproject.org/wiki/How_to_debug_printing_problems#Driverless_printing_.28wireless.2Fethernet.29
[3] https://fedoraproject.org/wiki/How_to_debug_printing_problems#How_to_setup_CUPS_temporary_queues_with_network_printer
[4] https://fedoraproject.org/wiki/How_to_debug_printing_problems#Printer_applications

Comment 2 Bruno Wolff III 2021-02-25 10:45:10 UTC

I'll try it out. I was using a USB connection, not the wireless mode. The reason I went looking for driver support is that when I used the printer settings in the XFCE desktop it didn't seem to recognize the printer type. I should be able to try driverless printing today.

Comment 3 Bruno Wolff III 2021-02-25 11:41:58 UTC

It looks like I needed ipp-usb, which I didn't have installed. I'll try to see if that makes a difference once I have the printer connected again.

Comment 4 Bruno Wolff III 2021-02-25 12:20:40 UTC

The IPP everywhere driver does work. (I successfully printed a test page.) It isn't suggested by the driver search when installing the printer. I have to select the generic drivers and then select IPP everywhere manually.
Thanks for your help.

Comment 5 Zdenek Dohnal 2021-03-01 07:31:50 UTC

(In reply to Bruno Wolff III from comment #4)
> It isn't suggested by the driver search when installing the printer.

The main pros of IPP Everywhere is that you don't need to install the printer at all - see https://fedoraproject.org/wiki/How_to_debug_printing_problems#Temporary_print_queues 

They will just appear during the print dialog and will be removed after successful printing - so you spare some CPU memory otherwise needed for maintaining the permanent queue and you don't need to install the queue manually.

Temporarily (it is planned to provide a different solution) - a permanent queue would be needed if you want to share your print queue further down the network or if you want a different defaults then the device has set. If you don't want to use any of those, a temporary queue suffices for you.