"Printer added" notification

[Gustav Ekner]

I've recently installed Ubuntu 17.10 (Gnome shell). After a while I saw an OSD notification with the message "printer added", and thought that must be because of the new driverless printers feature in the kernel. I have a brother printer in the network, and I tested it and it worked. The thing is that the message repeats itself, approximately every two minutes, and it's really distracting. I saw a question about this on AskUbuntu (https://askubuntu.com/questions/918462/ubuntu-17-04-printer-added-notifications-under-gnome), and a solution, but it seemed like no one had filed a bug report.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1725955/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Sebastien Bacher (seb128)]

Could you add your syslog to the bug? The notification comes from gnome-settings-daemon when detecting a new printer, the repetition is a bug for sure though

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Gustav Ekner (gustav-ekner)]

Nothing shows up about it in the syslog except this, which seems to show up each time the notification comes:

colord[1227]: failed to get session [pid 2331]: No data available

[Gustav Ekner (gustav-ekner)]

Now the bug is reported in GNOME's bug reporter: https://bugzilla.gnome.org/show_bug.cgi?id=789490

[Sebastien Bacher (seb128)]

thanks for reporting it upstream

[brad (dragonsawareness)]

Oct 31 23:56:14 brad-ubuntu org.debian.apt[837]: 23:56:14 AptDaemon [INFO]: Quitting due to inactivity
Oct 31 23:56:14 brad-ubuntu org.debian.apt[837]: 23:56:14 AptDaemon [INFO]: Quitting was requested
Nov 1 00:01:50 brad-ubuntu systemd[1]: Started Run anacron jobs.
Nov 1 00:01:50 brad-ubuntu anacron[16049]: Anacron 2.3 started on 2017-11-01
Nov 1 00:01:50 brad-ubuntu anacron[16049]: Will run job `cron.daily' in 5 min.
Nov 1 00:01:50 brad-ubuntu anacron[16049]: Jobs will be executed sequentially
Nov 1 00:03:20 brad-ubuntu systemd[1]: dev-disk-by\x2duuid-5254FA6A54FA5069.device: Job dev-disk-by\x2duuid-5254FA6A54FA5069.device/start timed out.
Nov 1 00:03:20 brad-ubuntu systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-5254FA6A54FA5069.device.
Nov 1 00:03:20 brad-ubuntu systemd[1]: Dependency failed for /Media.
Nov 1 00:03:20 brad-ubuntu systemd[1]: Media.mount: Job Media.mount/start failed with result 'dependency'.
Nov 1 00:03:20 brad-ubuntu systemd[1]: dev-disk-by\x2duuid-5254FA6A54FA5069.device: Job dev-disk-by\x2duuid-5254FA6A54FA5069.device/start failed with result 'timeout'.
Nov 1 00:06:50 brad-ubuntu anacron[16049]: Job `cron.daily' started
Nov 1 00:06:50 brad-ubuntu anacron[16397]: Updated timestamp for job `cron.daily' to 2017-11-01
Nov 1 00:06:50 brad-ubuntu cracklib: no dictionary update necessary.
Nov 1 00:06:51 brad-ubuntu systemd[1]: Stopping Make remote CUPS printers available locally...
Nov 1 00:06:51 brad-ubuntu systemd[1]: Stopped Make remote CUPS printers available locally.
Nov 1 00:06:51 brad-ubuntu systemd[1]: Stopping CUPS Scheduler...
Nov 1 00:06:51 brad-ubuntu systemd[1]: Stopped CUPS Scheduler.
Nov 1 00:06:51 brad-ubuntu gsd-color[1855]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_ENVY_4520_series
Nov 1 00:06:51 brad-ubuntu gsd-color[1320]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_ENVY_4520_series
Nov 1 00:06:51 brad-ubuntu systemd[1]: Closed CUPS Scheduler.
Nov 1 00:06:51 brad-ubuntu systemd[1]: Stopping CUPS Scheduler.
Nov 1 00:06:51 brad-ubuntu systemd[1]: Listening on CUPS Scheduler.
Nov 1 00:06:51 brad-ubuntu systemd[1]: Stopped CUPS Scheduler.
Nov 1 00:06:51 brad-ubuntu systemd[1]: Stopping CUPS Scheduler.
Nov 1 00:06:51 brad-ubuntu systemd[1]: Started CUPS Scheduler.
Nov 1 00:06:51 brad-ubuntu systemd[1]: Started CUPS Scheduler.
Nov 1 00:06:51 brad-ubuntu systemd[1]: Started Make remote CUPS printers available locally.
Nov 1 00:06:51 brad-ubuntu colord[932]: failed to get session [pid 16648]: No data available.

Nothing was in sys log. I had to look inside sys log 1.

My screen will wake up 3-4 times a day (while locked) randomly to look for my hp envy 4520. Its a wirelessly connected printer. I've already added it. If I remove it from printers it automatically re-adds itself with this script. Its very annoying.

[Stu (stu-axon)]

I've just started working somewhere with a lot of printers and am seeing this pop up often, under Ubuntu 17.10

[brad (dragonsawareness)]

This notification pops up each time the network is changed (connected, disconnected), printer turned off or on, and during a daily chron job.

[Sebastian Thürrschmidt (thuerrschmidt)]

Just a wild guess: Maybe avahi-daemon is involved somehow? For me at least these annoying messages seem to have stopped completely after throwing out the avahi-daemon service (for other reasons).

So you may try this:

systemctl disable avahi-daemon.socket avahi-daemon.service

If it helps, do this:

systemctl mask avahi-daemon.socket avahi-daemon.service
systemctl stop avahi-daemon.socket avahi-daemon.service

[Gustav Ekner (gustav-ekner)]

I'm running 18.04 right now and don't have the issue, so I guess it has been resolved. Are you running 17.10 @thuerrschmidt?

[Robin Sheat (eythian)]

It still occurs in 18.04.

[Jeff Lambert (jl-newtraxtech)]

Happens to me in 18.04 desktop

[Sebastien Bacher (seb128)]

Could those having the issue add their journalctl log?

[Carlos Laviola (claviola)]

This started happening to me after I upgraded from Ubuntu 19.04 to 19.10. Now I get a steady spam of pop-ups and the only thing in the logs that seems related are colord messages like the one from #6:

out 31 13:08:47 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 13:13:31 maragogi colord[1784]: failed to get session [pid 4408]: No data available
out 31 13:32:07 maragogi colord[1784]: failed to get session [pid 19534]: No data available
(...)
out 31 14:00:20 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:00:38 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:01:05 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:01:37 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:01:56 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:02:14 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:02:34 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:03:02 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:03:22 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:03:40 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:04:09 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:04:31 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:04:49 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:05:05 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:05:23 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:05:53 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:06:13 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:06:32 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:07:19 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:07:38 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:08:06 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:08:24 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:08:43 maragogi colord[1784]: failed to get session [pid 19534]: No data available
out 31 14:09:10 maragogi colord[1784]: failed to get session [pid 19534]: No data available

The referenced PIDs:

claviola 4408 0.0 0.1 991904 26724 ? Ssl out30 0:04 /usr/lib/gnome-settings-daemon/gsd-color
root 19534 0.0 0.0 105252 12528 ? Ss 00:00 0:03 /usr/sbin/cupsd -l

[Samey the Hedgie (superzander369)]

Happens for me on Ubuntu 20.04

[Sebastien Bacher (seb128)]

The issue should be fixed with https://launchpad.net/ubuntu/+source/gnome-settings-daemon/3.36.1-1ubuntu2

Changelog

  * debian/patches/git_cupsbrowsed_notification.patch:
    - Ignore 'Printer-added' notifications for queues created by
      cups-browsed (lp: #1878241)