Add Printer wizard keeps using broken ipps:// DNS-SD URI, driverless PPD generation fails
维护者通常 3 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by tracing how the Add Printer wizard selects and submits a DNS-SD device URI, then follow the driverless PPD generation call. The report names no source files or tests, so locate these paths in the repository and check how an explicitly entered ipp:// URI is handled. Done when that URI is preserved through submission and PPD generation, and a usable plain-IPP endpoint can be selected when IPPS fails.
由索引模型根据 Issue 内容生成。
描述
Problem
When adding a network printer that is discovered through DNS-SD and advertises both _ipp._tcp.local and _ipps._tcp.local, the Add Printer wizard ends up submitting the secure ipps:// URI to CUPS. On the device below, the IPPS endpoint rejects the TLS handshake with SSL alert 40 (handshake_failure). cups-filters' driverless PPD generation then fails and the wizard reports that the printer could not be added.
I also tried to force plain IPP by entering ipp://<printer-host>.local:631/ipp/print in the wizard, but the request that reached cupsd still contained the DNS-SD ipps:// URI, so the outcome did not change.
CUPS error log
E [20/Nov/2026:19:03:46] [CGI] Unable to create PPD file: Could not poll sufficient capability info from the printer (ipps://Canon%20TS7530%20series._ipps._tcp.local/, ipps://<printer-host>.local:631/ipp/print) via IPP!
E [20/Nov/2026:19:03:57] [CGI] Unable to create PPD file: Could not poll sufficient capability info from the printer (ipps://Canon%20TS7530%20series._ipps._tcp.local/, ipps://<printer-host>.local:631/ipp/print) via IPP!
E [20/Nov/2026:19:03:57] copy_model: empty PPD file
E [20/Nov/2026:19:03:57] [Client 48] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://localhost/printers/Canon-TS7530-series) from localhost.
Expected behavior
If the user explicitly supplies an ipp:// device URI, that URI should be used for CUPS-Add-Modify-Printer and for driverless PPD generation. More generally, when a device advertises both ipp and ipps and the IPPS endpoint is unusable, the GUI should fall back to the working plain-IPP endpoint instead of failing the whole wizard.
Verification
Plain IPP works correctly from the same machine:
ipptool -4 ipp://192.168.0.62:631/ipp/print /usr/share/cups/ipptool/get-printer-attributes.test->PASS, about 375 KB of attributes returned.driverless ipp://<printer-host>.local:631/ipp/print-> valid 21 KB PPD, exit status 0.driverless ipps://192.168.0.62:631/ipp/print-> exactly the same "Could not poll sufficient capability info ... via IPP!" error as the GUI.- OpenSSL:
openssl s_client -connect 192.168.0.62:631->SSL alert number 40 (handshake failure)for both TLS 1.2 and TLS 1.3; no peer certificate is sent.
Adding the queue from the command line with the pre-generated PPD works:
driverless ipp://<printer-host>.local:631/ipp/print > /tmp/canon.ppd
sudo lpadmin -p Canon_TS7530 -E -v ipp://<printer-host>.local:631/ipp/print -P /tmp/canon.ppd
sudo lpadmin -d Canon_TS7530
Environment
- Arch Linux (Omarchy), 2026-11-20
- system-config-printer 1.5.18-7
- CUPS 2.4.20-1, cups-filters 2.0.1-3, libcupsfilters 2.2.1.r32.gd49e9284-1
- Printer: Canon TS7530 series, firmware 1.030 (already the latest available), AirPrint 1.8 / Mopria 2.0, advertises both
_ipp._tcpand_ipps._tcpon port 631
Since the printer firmware is already current, this looks like an interoperability problem between the device's IPPS stack and recent OpenSSL/cups-filters. The GUI should not force the broken endpoint when a working plain-IPP endpoint is available.
- 主要语言
- Python
- 星标
- 209
- 派生
- 111
- 平均合并
- 2 天 13 小时
- 30 天内合并 PR
- 8
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
OpenPrinting/system-config-printer 的其他 Issue
-
Job viewer shows "Printer error" for cups-waiting-for-job-completed可能已有人在做 @RonitMehta08 于 8 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 86/100
OpenPrinting/system-config-printer#494 ·
维护者通常 3 天内回复
-
难度 4/5 3-5 天 新手友好度 44/100
OpenPrinting/system-config-printer#499 ·
维护者通常 3 天内回复
-
[Release Tracking] system-config-printer 1.5.19 milestone可能已有人在做 @alexpevzner 于 19 天前认领。 未关闭
OpenPrinting/system-config-printer#492 · 1 条评论 · 已指派 2 人 ·
维护者通常 3 天内回复
-
Scanner未关闭
难度 3/5 1-2 天 新手友好度 25/100
OpenPrinting/system-config-printer#407 · 1 条评论 ·
维护者通常 3 天内回复
-
Doesn't run with PYTHONSAFEPATH enabled可能已有人在做 @xovishnukosuri 于 253 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 58/100
OpenPrinting/system-config-printer#387 ·
维护者通常 3 天内回复
查看 OpenPrinting/system-config-printer 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 85/100
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
pearu/agent-sandbox#451 ·
维护者通常 1 天内回复
-
run_gate loads a custom tasks file from outside the working directory可能已有人在做 @Ru0k3 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 78/100
MakazhanAlpamys/Soup#3189 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
NYCPlanning/data-engineering#2996 ·
维护者通常 1 天内回复