36

I've just upgraded to Ubuntu 17.04, using the GNOME desktop. Suddenly, I've started seeing 'printer added' notifications as OSD popups - approximately every 2 minutes! It's really distracting.

Anyone have any idea how I can either stop them at source, or at the very least filter them out from the OSD notifications?

33

The problem that you're identifying appears identical to my case, which is, that upon OS restart, the system goes through an auto-discovery/auto-install process, and then politely notifies the user via a notification window (the OSD, or on-screen display). Yet then--periodically--this process seems to repeat itself for some as yet unknown reason.

Seems to me that somewhere in the new 17.04 driverless printer driver discovery logic, something is broken. The best I can tell is that the colord daemon is failing on a missing ICC file for the printer in question, which causes CUPS to want to "reinstall" the printer driver, and hence the repeating "printer installed" OSD message. Perhaps as a clue, when installing a "non-driverless" printer driver, the corresponding ICC is installed correctly.

In my own case, I've solved the problem by preventing CUPS from initiating this auto-everything process entirely. In this way, I install my printer(s) once, and never see a "printer added" OSD messages again.

The solution:

  • Edit /etc/cups/cups-browsed.conf, changing the BrowseRemoteProtocols CUPS dnssd line to BrowseRemoteProtocols none

  • Restart CUPS from Terminal service cups restart

Note that this assumes your printer(s) are on a LAN and not directly connected to your machine. If your printer is local (physically attached), you may want to edit BrowseProtocols instead (untested).

A restart of the CUPS service or machine reboot should resolve the "printer added" issue. Note that you'll need to manually add your printer(s), as the auto-discovery feature has now been disabled.

CUPS Reference: https://www.systutorials.com/docs/linux/man/5-cups-browsed.conf/

Rich

  • that sounds pretty plausible. My printer is indeed on the network. I'm not in the office today, but I'll try your suggestion next time I am. Thanks! – Ian Dickinson Jun 2 '17 at 12:47
  • So that does definitely stop the OSD notifications, thanks @richbl. I do wonder if we should be reporting the root problem to a bug list somewhere, but I'm not actually sure where that somewhere should be! – Ian Dickinson Jun 9 '17 at 9:03
  • 21
    For me the configuration file was /etc/cups/cups-browsed.conf – gitaarik Jul 28 '17 at 15:49
  • 3
    I do not care if the underlying process repeats. I just want to avoid seeing the OSD messages. Can those be disabled? – Thorbjørn Ravn Andersen Nov 2 '17 at 10:25
  • 1
    Does not work in 17.10. I still get the notifications, and printer gets added, as a duplicate to a previously installed printer. – Chad Wright Nov 6 '17 at 17:29
16

So I thought I had found a solution (via FedoraForums actually):

# Finding the schemas of interest:
$ gsettings list-schemas | grep -i notif

# Listing the values to target:
$ gsettings list-keys org.gnome.settings-daemon.plugins.print-notifications

# Changing the value:
$ gsettings set org.gnome.settings-daemon.plugins.print-notifications active false

Source http://www.fedoraforum.org/forum/showthread.php?t=297053

Unfortunately, despite a brief pause, I'm still getting OSD notifications.

  • I can confirm that this seems to work in 16.04 LTS. Thanks – chris LB Jul 5 '17 at 11:26
  • 2
    works like a charm on 17.10 – R13e Jan 11 '18 at 8:05
  • 1
    Seems to do the trick on Debian 9. Probably a Gnome issue. – kabanus Apr 12 '18 at 7:08
  • 5
    I like this answer because it demonstrates how to find the setting that needs to be changed, rather than just giving the fix. Plus you change the notification setting rather than turning off printer auto-detection altogether. – metasequoia Aug 15 '18 at 12:51
  • It doesn't help my Ubuntu 18.04 either. – Samuel Li Feb 26 at 22:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.