Hi Julien,

thank you for reporting this issue! Would you mind trying the newest updates from updates-testing for cups-filters and cups if it helps? If not, there can be error in ghostscript itself, according:

(In reply to Julien HENRY from comment #0)
> juin 11 22:14:03 pcsalon cupsd[15405]: Killing pdf-to-ps
> juin 11 22:14:03 pcsalon cupsd[15405]: Cleaning up...
> juin 11 22:14:03 pcsalon cupsd[15405]: Possible error on renderer command
> line or PostScript error. Check options.Process is dying with \"Encountered
> error Broken pipe during fwrite\">
> juin 11 22:14:03 pcsalon cupsd[15405]: renderer exited with status 1
> juin 11 22:14:03 pcsalon cupsd[15405]: /bin/bash: setpagedevice: Permission
> non accordée
> juin 11 22:14:03 pcsalon cupsd[15405]: /bin/bash: avertissement :«
> here-document » à la ligne 0 délimité par la fin du fichier (au lieu de «
> /Duplex »)
> juin 11 22:14:03 pcsalon cupsd[15405]: <job data>
> juin 11 22:14:03 pcsalon cupsd[15405]: JCL: \033%-12345X@PJL
> juin 11 22:14:03 pcsalon cupsd[15405]: Starting process \"renderer\"
> (generation 2)
> juin 11 22:14:03 pcsalon cupsd[15405]: Starting process \"kid4\" (generation
> 2)
> juin 11 22:14:03 pcsalon cupsd[15405]: Starting process \"kid3\" (generation
> 1)
> juin 11 22:14:03 pcsalon cupsd[15405]: Starting renderer with command: \"gs
> -sstdout=%stderr  -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs
> -sIjsServer=hpijs<</Duplex false/T>

Hi Zdenek,

I can't find any update for cups and cups-filters in updates-testing. I see there is an update of hplip. Is it was you are talking about?

Oh, my bad - they are still in pending state before going to testing repository - you can find them in bodhi itself for now.

This is https://bodhi.fedoraproject.org/updates/FEDORA-2018-5e48964321 right? Then they should appear soon in the update-testing repo. As soon as it is available I'll let you know.

When you open the bodhi website and go to the build tab, there is link to koji build, where are rpms which you can install too.

I installed cups 2.2.6-15.fc28 and cups-filters 20.0-9.fc28, restarted cups.service, reverted to the hpijs driver, but I still have the same error.

And hp-setup still installs your printer with hpijs driver?

Yep:

# hp-setup -i 192.168.0.100

HP Linux Imaging and Printing System (ver. 3.18.4)
Printer/Fax Setup Utility ver. 9.0

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

(Note: Defaults for each question are maked with a '*'. Press <enter> to accept the default.)


Setting up device: hp:/net/Photosmart_Premium_C309g-m?ip=192.168.0.100



---------------------
| PRINT QUEUE SETUP |
---------------------


Please enter a name for this print queue (m=use model name:'Photosmart_Premium_C309g-m'*, q=quit) ?
Using queue name: Photosmart_Premium_C309g-m
Locating PPD file... Please wait.

Found PPD file: drv:///hp/hpijs.drv/hp-photosmart_premium_c309g-m-hpijs.ppd

Thank you for the info! I'm sorry to bother you - can you try the hplip update too? Because hplip needs cups running for finding the proper ppd - the newest update makes sure the cups is running.

Still the same:

# hp-setup -i 192.168.0.100

HP Linux Imaging and Printing System (ver. 3.18.6)
Printer/Fax Setup Utility ver. 9.0

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

(Note: Defaults for each question are maked with a '*'. Press <enter> to accept the default.)


Setting up device: hp:/net/Photosmart_Premium_C309g-m?ip=192.168.0.100



---------------------
| PRINT QUEUE SETUP |
---------------------


Please enter a name for this print queue (m=use model name:'Photosmart_Premium_C309g-m'*, q=quit) ?
Using queue name: Photosmart_Premium_C309g-m
Locating PPD file... Please wait.

Found PPD file: drv:///hp/hpijs.drv/hp-photosmart_premium_c309g-m-hpijs.ppd
Description: 

Note: The model number may vary slightly from the actual model number on the device.


> Because hplip needs cups running for finding the proper ppd

I don't know if this is expected, but I get many KO from hp-check:

# hp-check -t

 <Package-name>        <Package-Desc>      <Required/Optional> <Min-Version> <Installed-Version> <Status>   <Comment>

-------------------------
| External Dependencies |
-------------------------

 error: cups          CUPS - Common Unix Printing System                           REQUIRED        1.1             -               INCOMPAT   'CUPS may not be installed or not running'
 gs                   GhostScript - PostScript and PDF language interpreter and previewer REQUIRED        7.05            9.23            OK         -
 error: xsane         xsane - Graphical scanner frontend for SANE                  OPTIONAL        0.9             -               MISSING    'xsane needs to be installed'
 scanimage            scanimage - Shell scanning program                           OPTIONAL        1.0             1.0.27          OK         -
 error: dbus          DBus - Message bus system                                    REQUIRED        -               1.12.8          MISSING    'DBUS may not be installed or not running'
 policykit            PolicyKit - Administrative policy framework                  OPTIONAL        -               0.114           OK         -
 network              network -wget                                                OPTIONAL        -               1.19.5          OK         -
 error: avahi-utils   avahi-utils                                                  OPTIONAL        -               -               MISSING    'avahi-utils needs to be installed'

And would you mind setting your system locale to US (I'm sorry, I don't understand French in log...) and attaching cupsd log again with English locale? And can you send output of command 'rpm -qV ghostscript' if any?

Created attachment 1450932 [details]
System logs (US) when trying to print a test page

ghostscript is not installed

My bad, rpm -qV ghostscript returns nothing, but ghostscript *is* installed

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.

Still valid with a clean Fedora 31.
I installed clean KDE desktop + hplip-gui. When I setup my printer, the hpijs driver is selected, and I'm unable to print.
Manually switching to hpcups fix the issue.

I was able to reproduce with file device print queue and ppd from hplip.

There are two issues:

1. IMO hpcups driver should be preferred instead of old hpijs driver

2. foomatic-rip filter ends with error - probably due following ghostscript command:

gs -sstdout=%stderr  -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs -sIjsServer=hpijs<</Duplex false/Tumble false>>setpagedevice -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792 -sDeviceManufacturer=\"HEWLETT-PACKARD\" -sDeviceModel=\"deskjet 5600\" -r300 -sIjsParams=Quality:Quality=0,Quality:ColorMode=2,Quality:MediaType=0,Quality:PenSet=2,PS:MediaPosition=7 -dIjsUseOutputFD -sOutputFile=%stdout -_

Ad 1. I'll try to fake the argument of function which looks for PPDs to fake that my printer is HP Photosmart c309g

Ad 2. I'll get the file which goes to foomatic-rip and simulate the filtering process.

Ad 1.

Ok, faking the device seems to work for debug purposes.

The device falls through the first searching algorithm because of the following issue:

driver string name: drv:///hp/hpijs.drv/hp-photosmart_premium_c309g-m-hpijs.ppd is matched to regexp pattern and gives string 'photosmart_premium_c309g' which is used to compare with stripped model name 'photosmart_premium_c309g-m', which comes from the device.

So it falls through because the regexp pattern doesn't match to '-m'.

The second searching algorithm is able to find the right drivers, but still does not expect '-m' and thinks it is a PDL name... then it searches for pdl priority of 'm' and thinks it is a new PDL, so it returns the first match, which is hpijs driver...

I rewrote the searching algorithm to sanitize strings with '-' in the end - it now checks if it is known PDL (ps, pdf etc.) or filter type (hpcups, hpijs) and if it is neither of them, it thinks it is a part of device name.

I'll rename the summary and if I find more info about 2), I'll find a bug for it.

Commit for fixing search engine https://src.fedoraproject.org/rpms/hplip/c/458a657499eca3aa9a2944ccd832f3e76b0f9ea0?branch=master .

So printing with hpijs choke because of following:

hplip hpijs ppd defines following foomatic-rip command:

gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs -sIjsServer=hpijs%A%B%C -dIjsUseOutputFD%Z -sOutputFile=- -

The important part are variables %A%B%C , which are substituted in foomatic-rip.

Especially expectation of what will be substituted for %A is different from POV of PPD and foomatic-rip:

- PPD expects foomatic-rip will put -dDuplex=false from PPD, which doesn't matter where you put it in gs cmd line
- but foomatic-rip substitutes it with raw postscript commands - <</Duplex false/Tumble false>>setpagedevice - which needs to be in -c "" and at the end of gs cmd line

Working gs command from upstream (how it should look like):
gs -sstdout=%stderr  -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs -sIjsServer=hpijs -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792 -ssDeviceManufacturer="HEWLETT-PACKARD" -sDeviceModel="deskjet 5600" -r300 -sIjsParams=Quality:Quality=0,Quality:ColorMode=2,Quality:MediaType=0,Quality:PenSet=2,PS:MediaPosition=7  -dIjsUseOutputFD -sOutputFile=%stdout -c"<< /Duplex false/Tumble false>> setpagedevice" -_


But neither foomatic-rip or foomaticripcommand in PPD tells it should be in '-c""; - like -c"<</Duplex false/Tumble false>>setpagedevice", or moves it to the end of gs cmd line.

It can be solved by making foomatic-rip more robust, sanitize the foomaticripcommand lines from PPD and change to the correct form to make it work with gs, but IMO it is not priority since hpijs is deprecated.

FEDORA-2020-c77d623d5f has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c77d623d5f

FEDORA-2020-bcc8cef31e has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-bcc8cef31e

FEDORA-2020-bcc8cef31e has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-bcc8cef31e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-bcc8cef31e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2020-c77d623d5f has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c77d623d5f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c77d623d5f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2020-3ec2da7668 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3ec2da7668

FEDORA-2020-407a05acd2 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-407a05acd2

FEDORA-2020-407a05acd2 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-407a05acd2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-407a05acd2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2020-3ec2da7668 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-3ec2da7668`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3ec2da7668

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2020-63fd65420b has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-63fd65420b

FEDORA-2020-3013e53d34 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3013e53d34

FEDORA-2020-3013e53d34 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2020-63fd65420b has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.