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

オープン
#502 コメント 4 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 3 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python
領域
desktop

調査の方向性

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._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.

主要言語
Python
スター
209
フォーク
111
平均マージ
2日 13時間
マージ済み PR(30日)
8

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

OpenPrinting/system-config-printer のほかの issue

OpenPrinting/system-config-printer の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。