Bug 1879147
| Summary: | driverless cannot generate ppd for dns-sd based uris | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Casey <casey.jao> |
| Component: | cups-filters | Assignee: | Zdenek Dohnal <zdohnal> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 32 | CC: | twaugh, zdohnal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cups-filters-1.28.2-2.fc32 cups-filters-1.28.2-2.fc33 cups-filters-1.28.2-2.fc31 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-21 00:00:57 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: | |||
| Attachments: | |||
|
Description
Casey
2020-09-15 14:20:58 UTC
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. |