Created attachment 1714946 [details] cupsd logs Created attachment 1714946 [details] cupsd logs Description of problem: I have an Epson printer on my wireless network previously configured using driverless printing. Recently I noticed that after removing the printer I was unable to add it again using driverless printing. CUPS definitely sees the printer but errors out when I try to add it. Installing escpr drivers suffices as a workaround, but it would be simpler if driverless printing were to work. Version-Release number of selected component (if applicable): cups-filters 1.28.1-1. How reproducible: always Steps to Reproduce: 1. Try to add wireless printer through gnome-control-center. 2. Observe that printer is discovered. 3. Select it and click "Add". Actual results: "Failed to add new printer." See also the attached cupsd log. Expected results: I should be able to configure the printer using driverless printing. Additional info: I'm running Silverblue on my laptop, and using OSTree I determined that this problem resulted from the system update 32.20200831.0 --> 32.20200901.0: container-selinux 2:2.143.0-1.fc32 -> 2:2.144.0-2.fc32 crun 0.14.1-3.fc32 -> 0.14.1-4.fc32 cups-filters 1.27.5-6.fc32 -> 1.28.1-1.fc32 cups-filters-libs 1.27.5-6.fc32 -> 1.28.1-1.fc32 exiv2 0.27.2-2.fc32 -> 0.27.3-3.fc32 exiv2-libs 0.27.2-2.fc32 -> 0.27.3-3.fc32 iptables 1.8.4-8.fc32 -> 1.8.4-9.fc32 iptables-libs 1.8.4-8.fc32 -> 1.8.4-9.fc32 iptables-nft 1.8.4-8.fc32 -> 1.8.4-9.fc32 python3-cups 2.0.1-1.fc32 -> 2.0.1-5.fc32 rsync 3.2.2-1.fc32 -> 3.2.3-1.fc32 toolbox 0.0.93-1.fc32 -> 0.0.95-1.fc32 vim-minimal 2:8.2.1522-2.fc32 -> 2:8.2.1551-1.fc32 I'm filing the bug here because cups-filters seems most likely to be responsible among these updated packages.
Hi Casey, thank you for reporting the issue! Would you mind trying the following command: $ driverless -d cat ipps://EPSON6B1C2F.local:631/ipp/print > out.ppd 2> log and please attach the both created file if they aren't empty. I tried the same command on my HP driverless printer and it worked, so it seems to be specific to your Epson model. The core seems to be that now driverless backend isn't able to communicate with your printer or the printer doesn't provide enough info, which is required by driverless now, but we hopefully will see after checking the logs.
Created attachment 1715043 [details] driverless -d cat ipps://EPSON6B1C2F.local:631/ipp/print > out.ppd 2> driverless-errors-0916..log out.ppd is empty
Created attachment 1715045 [details] driverless -d cat ipps://EPSON6B1C2F.local:631/ipp/print > driverless-0831.ppd 2> driverless-errors-0831.log Result of running the same command on the 20200831 system image.
Thanks, please see attachments.
Thank you for the files! DEBUG2: Request for IPP attributes (get-printer-attributes) for printer with URI ipps://EPSON6B1C2F.local:631/ipip/print failed: Not Found DEBUG2: get-printer-attributes IPP request failed: DEBUG2: - No response See the uri - ipps://EPSON6B1C2F.local:631/ipip/print ---- Are you sure you didn't do a typo when you issued the command: $ driverless -d cat ipps://EPSON6B1C2F.local:631/ipp/print > out.ppd 2> log ? If it is a typo, please retest again (and you can choose shorter file desc in bugzilla :) ).
My apologies, you are right -- I am attaching the new logs, which do seem to indicate that the ppd file is generated correctly.
Created attachment 1715059 [details] driverless -d cat ipps://EPSON6B1C2F.local:631/ipp/print > driverless-0916.ppd 2> driverless-debug-0916.log
Created attachment 1715060 [details] debug output
Ok, so now to find out what GTK (framework which gnome-control-center and gnome-settings-daemon uses for getting printers) does differently... I'll check GTK code.
Aha: $ driverless cat <uri> works, but the following doesn't: $ driverless <uri> So the issue is in 'driverless' afterall. And it is reproducible regardless of printer device.
It is connected only to uris based on dns-sd name - like ipp://HP%20LaserJet%20M1536dnf%20MFP%20%2842307C%29._ipp._tcp.local/ . hostname based names like ipps://EPSON6B1C2F.local:631/ipp/print works.
The fix is sent upstream https://github.com/OpenPrinting/cups-filters/pull/309
You can test the scratch build for now https://koji.fedoraproject.org/koji/taskinfo?taskID=51663181 .
FEDORA-2020-b0e5a09b24 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b0e5a09b24
FEDORA-2020-6d1438650a has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-6d1438650a
FEDORA-2020-f053cee377 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f053cee377
FEDORA-2020-b0e5a09b24 has been pushed to the Fedora 33 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-b0e5a09b24` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-b0e5a09b24 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Thanks, your patch works!
FEDORA-2020-f053cee377 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-f053cee377` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f053cee377 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-6d1438650a 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-6d1438650a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6d1438650a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-6d1438650a has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-b0e5a09b24 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-f053cee377 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.