Bug#883554: Option cups-browsed-test-printer missing from broken configurations
Hi,
I don't run Debian, but I ended up here while researching the same
problem running CUPS (2.2.7, cups-filters-1.20.3) on openSUSE: after
some time (possibly a day, but currently it seems related to user
activity rather than just time) several clients start rejecting to
print, after an initially perfect setup by referencing a remote server
using `BrowsePoll myserver.mydomain` in `cups-browsed.conf`.
Here is a `printer.conf` from a (still) working client:
```
<DefaultPrinter HP_LaserJet_4700_Color_myserver_mydomain>
UUID urn:uuid:b6a92a7c-2501-3057-50c5-ffe00cdb0d76
Info HP LaserJet 4700 Color
MakeModel Remote printer: HP Color LaserJet 4700 Postscript (recommended)
DeviceURI implicitclass:HP_LaserJet_4700_Color_myserver_mydomain
State Idle
StateTime 1549039467
ConfigTime 1549039467
Type 37086
Accepting Yes
Shared No
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer
Option cups-browsed true
Option cups-browsed-dest-printer "547 myserver.mydomain:631/hp4700"
</DefaultPrinter>
```
and here the one from a broken `printer.conf`:
```
<Printer HP_LaserJet_4700_Color_myserver_mydomain>
UUID urn:uuid:7e74bcd2-9bb9-33fc-4193-a39d7ab75eac
Info HP LaserJet 4700 Color
MakeModel Remote printer: HP Color LaserJet 4700 Postscript (recommended)
DeviceURI implicitclass:HP_LaserJet_4700_Color_myserver_mydomain
State Stopped
StateMessage No destination host name supplied by cups-browsed for
printer "HP_LaserJet_4700_Color_myserver_mydomain", is cups-browsed running?
StateTime 1549461902
ConfigTime 1549461866
Reason paused
Type 37086
Accepting Yes
Shared No
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer
Option cups-browsed true
</Printer>
```
For some reason the option `cups-browsed-dest-printer` gets lost.
If everyone reporting on this issue is also running KDE, #887495 might
be a duplicate of this bug here, plus we might have to open an issue at
KDE instead. On the other hand, reading the changelog for cups-filters
seems that cups-browsed is not ready for production and/or the problem
might already be solved in a more recent version of cups-filters.
Best regards,
Tiziano
Reply to: