0

I got a new printer as the old one (16 years old!) did not want to print anything anymore. Bizarre since it printed just fine and all of a sudden, just blank pages.

Anyway, the new printer is on the network. All I had to do is plug it in, enter its MAC address in my DHCP server to force a given IP (I like doing so for security since that way I can easily block traffic from the printer if I want to). It prints and scans like a charm.

However, once in a while my Linux Ubuntu 18.04 tells me: "Hey man! I found a printer!" and it adds the printer to the list again and again. It's not a constant message, it happens once or twice a day. But it's still weird since I already have it in my list and that entry works as expected when printing... (for scanning I use the HTTP interface, so no special entry here.)

I'm thinking this may be a bug, but maybe someone else ran in this problem and knows how to circumvent the issue as of now. Anyone?

Example of what I see in the preferences:

enter image description here

Update: if that helps, I have these two entries from /var/log/cups/error_log:

W [29/Mar/2020:21:30:52 -0700] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_Pro_M478f_9f_117A48_@HPF8B46A117A48.local-Gray..\' already exists
W [29/Mar/2020:21:30:52 -0700] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_Pro_M478f_9f_117A48_@HPF8B46A117A48.local-DeviceN..\' already exists
Alexis Wilke
  • 2,707

1 Answers1

1

Open a terminal and go to:

/etc/cups/cups-browsed.conf

Then make the following change in the file:

BrowseRemoteProtocols none

save and then restart CUPS:

service cups restart
graham
  • 10,436
  • I would imagine that the detection with the explicit "Add Printer" button would still work even if that option is set to none? I read the docs but can't comprehend what really happens there... – Alexis Wilke Mar 30 '20 at 17:17
  • 1
    Yes, t should still work using Add Printer. – graham Mar 30 '20 at 18:59
  • Okay, I wanted to check after a reboot, just in case the restart wasn't enough. Note that since 16.04, you are expected to use systemctl restart cups. Anyway... it didn't work. I still see the second instance of the printer appearing. – Alexis Wilke Apr 07 '20 at 03:57
  • Note that I also tried with BrowseLocalProtocols none and it did not help either. – Alexis Wilke Apr 07 '20 at 04:07