Add Printer wizard keeps using broken ipps:// DNS-SD URI, driverless PPD generation fails

Abierto
#502 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
desktop

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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._tcp and _ipps._tcp on 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.

Lenguaje dominante
Python
Estrellas
209
Forks
111
Merge medio
2 d 13 h
PR fusionados (30 d)
8

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenPrinting/system-config-printer

Todos los issues de OpenPrinting/system-config-printer

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.