Add Printer wizard keeps using broken ipps:// DNS-SD URI, driverless PPD generation fails
I maintainer di solito rispondono entro 3 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Python
- Stelle
- 209
- Fork
- 111
- Merge medio
- 2g 13h
- PR unite (30g)
- 8
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di OpenPrinting/system-config-printer
-
Job viewer shows "Printer error" for cups-waiting-for-job-completedForse già presa @RonitMehta08 l’ha presa 8 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
OpenPrinting/system-config-printer#494 ·
I maintainer di solito rispondono entro 3 giorni
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 44/100
OpenPrinting/system-config-printer#499 ·
I maintainer di solito rispondono entro 3 giorni
-
[Release Tracking] system-config-printer 1.5.19 milestoneForse già presa @alexpevzner l’ha presa 19 giorni fa. Aperta
OpenPrinting/system-config-printer#492 · 1 commento · 2 assegnatari ·
I maintainer di solito rispondono entro 3 giorni
-
ScannerAperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 25/100
OpenPrinting/system-config-printer#407 · 1 commento ·
I maintainer di solito rispondono entro 3 giorni
-
Doesn't run with PYTHONSAFEPATH enabledForse già presa @xovishnukosuri l’ha presa 253 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 58/100
OpenPrinting/system-config-printer#387 ·
I maintainer di solito rispondono entro 3 giorni
Tutte le issue di OpenPrinting/system-config-printer
Issue simili
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
pearu/agent-sandbox#451 ·
I maintainer di solito rispondono entro 1 giorno
-
run_gate loads a custom tasks file from outside the working directoryForse già presa @Ru0k3 l’ha presa oggi. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
MakazhanAlpamys/Soup#3189 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
review developer setup docAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
NYCPlanning/data-engineering#2996 ·
I maintainer di solito rispondono entro 1 giorno