Bug#1062554: Acknowledgement (cups-browsed is not detecting any network printers)

2024-02-03 Thread Jonathan Kamens
close 1062554 thanks *sigh* I can't believe it. Rebooted my wifi router, and the problem went away. Apparently the wifi router was preventing the responses from getting back to the laptop. Sorry to bother you.

Bug#1062554: Acknowledgement (cups-browsed is not detecting any network printers)

2024-02-03 Thread Jonathan Kamens
One more data point: on the laptop that is not seeing mDNS query response broadcasts, if I disable wifi and plug into ethernet it works just fine. If I then unplug from ethernet and reenable wifi, it stops working again.

Bug#1062554: Acknowledgement (cups-browsed is not detecting any network printers)

2024-02-03 Thread Jonathan Kamens
I've debugged this further and I think it's probably a kernel network driver issuer but I don't know how to categorize that appropriately in the bug-tracking system so some help in that regard would be appreciated. `avahi-browse --all --terminate --ignore-local` returns no results on the

Bug#1062554: Acknowledgement (cups-browsed is not detecting any network printers)

2024-02-02 Thread Jonathan Kamens
*sigh* Ignore everything I said about my second laptop. The cups-browsed problem I originally reported persists, but I believe everything else was a PEBKAC issue. Sorry.

Bug#1062554: Acknowledgement (cups-browsed is not detecting any network printers)

2024-02-01 Thread Jonathan Kamens
It turns out things aren't working right on my second laptop either. It is correctly detecting network printers and making them visible to the OS as driverless printers, but I can't print to them. When I try, the print job gets paused and lpstat -t prints "No suitable destination host found by

Bug#1062554: Acknowledgement (cups-browsed is not detecting any network printers)

2024-02-01 Thread Jonathan Kamens
I also can't print to a printer I add explicitly to the system rather than relying on auto-discovered printers. Basically printing through CUPS appears to be completely borked, at least for me, across two diffferent laptops running Debian testing.