I have a brother printer at home connected via dnssd. If I take my laptop to work and then come home, then try to print it sits in the queue. Hover over the printer icon (kde) I see "unable to locate printer".
Rebooting gets the printer working. Restarting cups does not. Any ideas?
Thanks, Neal
On Tue, 5 Nov 2024 at 22:50, Neal Becker ndbecker2@gmail.com wrote:
I have a brother printer at home connected via dnssd. If I take my laptop to work and then come home, then try to print it sits in the queue. Hover over the printer icon (kde) I see "unable to locate printer".
Rebooting gets the printer working. Restarting cups does not. Any ideas?
Just a hunch, but did you disable/mask cups-browsed in response to the recent CUPS CVE?
Other than that, how are you discovering the printer when you relocate? IP, DNS name? Can you resolve it, ping it, telnet/nmap to the appropriate ports?
On Tue, 2024-11-05 at 17:49 -0500, Neal Becker wrote:
I have a brother printer at home connected via dnssd. If I take my laptop to work and then come home, then try to print it sits in the queue. Hover over the printer icon (kde) I see "unable to locate printer".
Rebooting gets the printer working. Restarting cups does not. Any ideas?
That very occasionally happens to me, though my machine is a desktop that sits beside the printer. The following seems to work most of the time:
$ sudo avahi-browse -a -t
That will list visible devices on the local network, and seems to be sufficient to wake up the printer. There may be a shorter way to do it but I can't be bothered investigating.
Failing that, power-cycling the printer should do the trick.
poc
On Tue, 2024-11-05 at 17:49 -0500, Neal Becker wrote:
I have a brother printer at home connected via dnssd. If I take my laptop to work and then come home, then try to print it sits in the queue. Hover over the printer icon (kde) I see "unable to locate printer".
Rebooting gets the printer working. Restarting cups does not.
Wondering, are you rebooting between work and home, or suspending?
There may be printer discovery issues if only suspending. Perhaps some of the services should be restarted, but aren't.
I've found that, from time to time, I have to restart cups-browsed and cups, when something has changed on the LAN. Printing just about always works as expected on my old CentOS box, but Fedora requires a sadistic amount of horse-whipping to print to the same printer, whether I'm printing directly to the printer (it's a networked Hewlett Packard P3015 laserjet), or via the CentOS server.
To make matters worse, Fedora (40) keeps on defaulting to stopping the printer on errors, rather than simply aborting the job, and that is a seriously annoying setting.
Several older releases of Fedora ago, I didn't have this problem.
Inconsistent settings is something I hate about this "discover the printer automatically, all the time" methodology instead of setting your printer up manually, once.
On Tue, Nov 5, 2024 at 11:21 PM Tim via users users@lists.fedoraproject.org wrote:
On Tue, 2024-11-05 at 17:49 -0500, Neal Becker wrote:
I have a brother printer at home connected via dnssd. If I take my laptop to work and then come home, then try to print it sits in the queue. Hover over the printer icon (kde) I see "unable to locate printer".
Rebooting gets the printer working. Restarting cups does not.
Wondering, are you rebooting between work and home, or suspending?
There may be printer discovery issues if only suspending. Perhaps some of the services should be restarted, but aren't.
I've found that, from time to time, I have to restart cups-browsed and cups, when something has changed on the LAN. Printing just about always works as expected on my old CentOS box, but Fedora requires a sadistic amount of horse-whipping to print to the same printer, whether I'm printing directly to the printer (it's a networked Hewlett Packard P3015 laserjet), or via the CentOS server.
To make matters worse, Fedora (40) keeps on defaulting to stopping the printer on errors, rather than simply aborting the job, and that is a seriously annoying setting.
Several older releases of Fedora ago, I didn't have this problem.
Inconsistent settings is something I hate about this "discover the printer automatically, all the time" methodology instead of setting your printer up manually, once.
Yes, I'm suspending and then waking when I get home.
On Wed, 2024-11-06 at 10:52 -0500, Neal Becker wrote:
Yes, I'm suspending and then waking when I get home.
Perhaps you might want to look into having the wakeup routines automatically restart cups and cups-browsed. Restarting them won't cause any harm, and would automate things for you.
Or perhaps, having them restarted after your network connects.
Some things trying to fire up before the network is ready has been a cause of failed services in the past. They (the ones that fail) don't retry, later, after their initial failure because no network was ready.
-
Neal Becker -
Patrick O'Callaghan -
Tim -
Will McDonald