cups-browsed finds the printers and removes them during discovery

After using cups-browsed with the patches for CVE-2024-47076 and CVE-2024-47176 applied, a user opened bug #108350 [1] in Debian. More logfiles are attaches to the bugs. Do you have any idea what went wrong?

Thorsten

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083050

after latest upgrade to 1.28.17-3+deb12u1 printing fails, cups-browsed finds the printers and removes them during discovery.

in the cups-browsed_log logfile there are entries like this one:
Mon Sep 30 15:58:37 2024 get-printer-attributes IPP call failed on printer ARCHIV (ipp://ARCHIV%20%40%20ps04._ipp._tcp.local/cups).
Mon Sep 30 15:58:37 2024 Printer ipp://ARCHIV%20%40%20ps04._ipp._tcp.local/cups (ps04.local, 192.168.60.34): Local queue ARCHIV, Remote CUPS Printer, Slave of None (To be created/updated)
Mon Sep 30 15:58:37 2024 DNS-SD IDs: Service name: "ARCHIV @ ps04", Service type: "_ipp._tcp", Domain: "local"
...
Mon Sep 30 15:59:03 2024 get-printer-attributes IPP call failed on printer ARCHIV (ipps://ARCHIV%20%40%20ps04._ipps._tcp.local/cups).
Mon Sep 30 15:59:03 2024 Printer ARCHIV (Host: ps04.local, Port: 631, URI: ipps://ARCHIV%20%40%20ps04._ipps._tcp.local/cups) disappeared and no slave available (or it is a slave of another printer), removing entry.
Mon Sep 30 15:59:03 2024 === Remote printer overview ===
Mon Sep 30 15:59:03 2024 Printer ipps://ARCHIV%20%40%20ps04._ipps._tcp.local/cups (ps04.local, 192.168.60.34): Local queue ARCHIV, Remote CUPS Printer, Slave of None (Disappeared)
Mon Sep 30 15:59:03 2024 ===============================
Mon Sep 30 15:59:03 2024 checking queues in 0s
Mon Sep 30 15:59:03 2024 Processing printer list ...
Mon Sep 30 15:59:03 2024 === Remote printer overview ===
Mon Sep 30 15:59:03 2024 Printer ipps://ARCHIV%20%40%20ps04._ipps._tcp.local/cups (ps04.local, 192.168.60.34): Local queue ARCHIV, Remote CUPS Printer, Slave of None (Disappeared)
Mon Sep 30 15:59:03 2024 ===============================
Mon Sep 30 15:59:03 2024 Removing entry ARCHIV (ipps://ARCHIV%20%40%20ps04._ipps._tcp.local/cups) and its CUPS queue.
Mon Sep 30 15:59:03 2024 Recording printer options for ARCHIV to /var/cache/cups/cups-browsed-options-ARCHIV
Mon Sep 30 15:59:03 2024 Unable to get PPD file for ARCHIV: Nicht gefunden
Mon Sep 30 15:59:03 2024 Recording option settings from the IPP attributes for ARCHIV:
Mon Sep 30 15:59:03 2024 Requested IPP attributes (get-printer-attributes) for printer with URI ipp://localhost/printers/ARCHIV

and afterwards the printer is remove from "lpc status" list.

if we downgrade to the old version without the latest secruity fixes everything works great.

the logfile looks like that:
Mon Sep 30 15:56:33 2024 Print queue ARCHIV is for remote CUPS queue(s) and we get notifications from CUPS, using implicit class device URI implicitclass://ARCHIV/
Mon Sep 30 15:56:33 2024 PPD generation successful: Apple Raster PPD generated.
Mon Sep 30 15:56:33 2024 Created temporary PPD file: /tmp/1918a567086ab5
Mon Sep 30 15:56:33 2024 Using PPD /tmp/1918a567086ab5 for queue ARCHIV.
Mon Sep 30 15:56:33 2024 Editing PPD file /tmp/1918a567086ab5 for printer ARCHIV, setting the option defaults of the previous cups-browsed session and doing client-side filtering of the job, saving the resulting PPD in /tmp/1918a5670872a1.
Mon Sep 30 15:56:33 2024 Non-raw queue ARCHIV with PPD file: /tmp/1918a5670872a1
Mon Sep 30 15:56:33 2024 Unsetting printer-is-shared bit.
Mon Sep 30 15:56:33 2024 Failed reading file /var/cache/cups/cups-browsed-remote-default-printer

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

System Information:

• OS: [e.g. Ubuntu]
• Version [e.g. 22.04]

Additional context
Add any other context about the problem here.

Start by comparing the upgraded and downgraded cups-browsed behavior and reviewing the cups-browsed_log entries around get-printer-attributes failures and printer removal. Check discovery and queue state through lpc status, then confirm that the printer remains available after discovery completes.