In gnome-fallback, both indicator-printers-service and gsd-printer are running as part of the session.
larsu in IRC suggested the following workaround: > (11:36:40 μμ) larsu: alkisg, yep, gsd-printer shouldn't be running > (11:43:19 μμ) larsu: cool, set > org.gnome.settings-daemon.plugins.print-notifications.active to false I did that, and after reboot [*] I got a different printer icon and no messages about the "Error: connecting-to-device" (and no notification about the job being completed either). So the problem that remains is to set that setting to false by default in the gnome-fallback session. [*] the reboot was necessary because when I tried powering on my printer right after the setting change, I got an apport window about a gnome-settings-daemon crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/842768 Title: Cups notifies "printer ' xxx ' may be not connected " although printer is OK and printing is OK too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/842768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
