Intentionally cancelling job at printer causes repeated reprint attempts from client
まだ誰も着手していません。
評価
調査の方向性
まず backend/implicitclass.c から始め、libcupsfilters/filter.c を通るキャンセル状態の流れと、CUPS scheduler/job.c での処理を追跡します。browsing で検出されたリモートの IPP/IPPS キューと、プリンター側でのキャンセルを使って問題を再現し、direct IPPS と implicitclass のログを比較します。意図的なキャンセルが再試行可能な失敗ではなくキャンセルとして伝播し、再印刷の繰り返しが防止されれば完了です。
索引モデルが issue の本文から書いたものです。
説明
I've noticed a behavior that may have been going on for awhile, but only recently was brought to my attention. When a user prints from a client with a "browsed" remote cups queue, and that user then intentionally cancels the print job at the printer, the client computer will begin retrying that print job repeatedly. Also, for reasons I have yet to determine, each retry also appends the job to the existing job (doubling the number of copies on every retry attempt).
I've observed that this only occurs on clients with printers browsed from a remote cups server, where that server is then connected to the printer via ipp/ipps. If the same client is connected directly with the printer ( ipps:// ), this does not occur. My guess is that this occurs where implicitclass is used.
I've tested this with a few combination of debian-based linux systems I have on hand, and a few models of HP enterprise network printers, and one model of small-office Canon network printer. I set up a debian Trixie system as the "server" (offering to the shared queues to be browsed by clients) and an ubuntu 26.04 system as the "server". As clients, I tried a few different versions of debian-based client (ubuntu 24/26, Mint, debian). All seemed to exhibit this behavior.
To see this behavior:
- Set up a Linux cups "server". Set settings in cupsd.conf that allow clients to browse the shared printers
Listen 0.0.0.0:631andAllow allin the<Location />directive block - Create a printer in this cups instance, connected with ipp/ipps, using the IPP everywhere driver. Share the printer
- Set up a client with cups-browsed, configured to browse the cups queue from the server. For example, in cups-browsed.conf, a
BrowsePolldirective pointing to the IP address of the server - Print a document from the client to this shared printer, such that you have to time manually cancel it while it is in progress.
End of client job log for a job printing from the client directly to the printer (ipps):
D [25/Aug/2026:19:02:24 -0500] [Job 314] job-password-encryption-supported 1setOf keyword none,sha2-256
D [25/Aug/2026:19:02:24 -0500] [Job 314] printer-state-message textWithoutLanguage
D [25/Aug/2026:19:02:24 -0500] [Job 314] ---- end-of-attributes-tag ----
D [25/Aug/2026:19:02:24 -0500] [Job 314] ATTR: auth-info-required=none
E [25/Aug/2026:19:02:24 -0500] [Job 314] Print job canceled at printer.
D [25/Aug/2026:19:02:24 -0500] [Job 314] Set job-printer-state-message to "Print job canceled at printer.", current level=ERROR
D [25/Aug/2026:19:02:24 -0500] [Job 314] PID 1067977 (/usr/lib/cups/backend/ipps) stopped with status 5.
W [25/Aug/2026:19:02:24 -0500] [Job 314] Backend ipps returned status 5 (cancel job)
D [25/Aug/2026:19:02:24 -0500] [Job 314] time-at-completed=1787702544
I [25/Aug/2026:19:02:24 -0500] [Job 314] Job canceled at printer.
D [25/Aug/2026:19:02:25 -0500] [Job 314] Unloading...
End of a client job log for a job printing to a browsed remote queue:
D [25/Aug/2026:18:57:25 -0500] [Job 313] cfFilterExternal (ipp): multiple-document-handling-supported 1setOf keyword separate-documents-uncollated-copies,separate-documents-collated-copies
D [25/Aug/2026:18:57:25 -0500] [Job 313] cfFilterExternal (ipp): operations-supported 1setOf enum Print-Job,Validate-Job,Create-Job,Send-Document,Cancel-Job,Get-Job-Attributes,Get-Jobs,Get-Printer-Attributes,Hold-Job,Release-Job,Pause-Printer,Resume-Printer,Purge-Jobs,Set-Printer-Attributes,Set-Job-Attributes,Get-Printer-Supported-Values,Create-Printer-Subscriptions,Create-Job-Subscriptions,Get-Subscription-Attributes,Get-Subscriptions,Renew-Subscription,Cancel-Subscription,Get-Notifications,Enable-Printer,Disable-Printer,Hold-New-Jobs,Release-Held-New-Jobs,Cancel-Jobs,Cancel-My-Jobs,Close-Job,CUPS-Get-Default,CUPS-Get-Printers,CUPS-Add-Modify-Printer,CUPS-Delete-Printer,CUPS-Get-Classes,CUPS-Add-Modify-Class,CUPS-Delete-Class,CUPS-Accept-Jobs,CUPS-Reject-Jobs,CUPS-Set-Default,CUPS-Get-Devices,CUPS-Get-PPDs,CUPS-Move-Job,CUPS-Authenticate-Job,CUPS-Get-PPD,CUPS-Get-Document,Restart-Job
D [25/Aug/2026:18:57:25 -0500] [Job 313] cfFilterExternal (ipp): ---- end-of-attributes-tag ----
D [25/Aug/2026:18:57:25 -0500] [Job 313] ATTR: auth-info-required=none
E [25/Aug/2026:18:57:25 -0500] [Job 313] cfFilterExternal (ipp): Print job canceled at printer.
E [25/Aug/2026:18:57:25 -0500] [Job 313] cfFilterExternal (ipp): Backend (PID 1067687) stopped with status 5
D [25/Aug/2026:18:57:25 -0500] [Job 313] Set job-printer-state-message to "cfFilterExternal (ipp): Backend (PID 1067687) stopped with status 5", current level=ERROR
D [25/Aug/2026:18:57:25 -0500] [Job 313] cfFilterExternal (ipp): Logging (PID 1067688) exited with no errors.
D [25/Aug/2026:18:57:25 -0500] [Job 313] cfFilterChain: Backend completed with status 1.
E [25/Aug/2026:18:57:25 -0500] [Job 313] cfFilterChain: Backend (PID 1067686) stopped with status 1
D [25/Aug/2026:18:57:25 -0500] [Job 313] Closed the pipes for back and side channels
E [25/Aug/2026:18:57:25 -0500] [Job 313] Job processing failed.
D [25/Aug/2026:18:57:25 -0500] [Job 313] PID 1067683 (/usr/lib/cups/backend/implicitclass) stopped with status 1.
W [25/Aug/2026:18:57:25 -0500] [Job 313] Backend implicitclass returned status 1 (failed)
I [25/Aug/2026:18:57:25 -0500] [Job 313] Job held for 300 seconds since it could not be sent.
Some brief glancing at the code seems to point to the different error codes returned from the ipp backend and the implicitclass backend. In main cups source (https://github.com/OpenPrinting/cups/blob/e119e5c84d88679fae61b63f789b584af89d8ba8/scheduler/job.c#L3247), the ipp backend returns error values which are handled there. Note that error 5 as seen in the logs is "CUPS_BACKEND_CANCEL", which leads the the job being actually cancelled.
However, when implicit class returns from a job canceled at the printer at this point, it will return "1" instead of "5" which leads to it being retried (presuming that the error policy is retry-job or retry-current-job). At (https://github.com/OpenPrinting/cups-browsed/blob/04b26c8b34407b6ba4631d755d56643d71d057ab/backend/implicitclass.c#L386) implicitclass calls cfFilterChain which eventually calls the ipp backend as a filter, which, when it receives the "error" of being canceled at the printer, is then handled by filter.c in the libcupsfilters repository at (https://github.com/OpenPrinting/libcupsfilters/blob/b95e5a4703d5ccf5129ffe49b6646bd7fbce91cf/cupsfilters/filter.c#L1544 ) which turns this ipp backend return into "status = 1" at ( https://github.com/OpenPrinting/libcupsfilters/blob/b95e5a4703d5ccf5129ffe49b6646bd7fbce91cf/cupsfilters/filter.c#L1568 ), which then implicit class turns into a return of "1" back to the cups job scheduler ( https://github.com/OpenPrinting/cups-browsed/blob/04b26c8b34407b6ba4631d755d56643d71d057ab/backend/implicitclass.c#L403 ).
IN general, a workaround to this is to set the error policy to "Abort job" instead of retrying. However, should this be fixed? Without enough knowledge of the connected pieces of cups, I'm not sure where the best place to fix this would be.
- 主要言語
- C
- スター
- 51
- フォーク
- 21
- 平均マージ
- 22時間 49分
- マージ済み PR(30日)
- 6
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
OpenPrinting/cups-browsed のほかの issue
-
難易度 3/5 1〜2日 初心者へのやさしさ 67/100
OpenPrinting/cups-browsed#82 · コメント 1 件 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
OpenPrinting/cups-browsed#77 · コメント 1 件 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 42/100
OpenPrinting/cups-browsed#76 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 38/100
OpenPrinting/cups-browsed#71 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
OpenPrinting/cups-browsed#74 · コメント 3 件 ·
OpenPrinting/cups-browsed の issue をすべて見る
似ている issue
-
`sha256()` returns a wrong hash when libsql-ffi is built with gcc 11 or later対応中かも @colinhacks が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
tursodatabase/libsql#2333 ·
メンテナーはふだん 11 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
OpenPrinting/cups#1826 ·
メンテナーはふだん 1 日以内に返信
-
Backport to 3.0 advertises a suffix that does not exist対応中かも このイシューにリンクされたプルリクエストがオープン中、またはマージ済みです。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
389ds/389-ds-base#8152 ·
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
RetroAchievements/rcheevos#580 · コメント 1 件 ·
メンテナーはふだん 5 日以内に返信