gnome-settings daemon notifies as error an info message

More info in case it was needed:

Versions and repository:

gnome-settings-daemon:
Installed version: 3.4.2-0ubuntu0.6.2
Repo used: http://es.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages

gnome-fallback:
Installed version: 3.2.1-0ubuntu8
Repo Used: http://es.archive.ubuntu.com/ubuntu/ precise/universe i386 Packages

Printer used: This has been testd with several printers: Canon ir5035 and Xerox Phaser 6180MFP-D. Tests on the latests one were done using Xerox Phaser 6180MFP-D Foomatic/Postscript, being the printer connected through the LAN.

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.

Hello Sebastien:

Not sure if this has already been done. This bug report was open as suggested by Canonical support staff, and was supposedly assigned to some dev.

Perhaps Alex (the guy from Canonical) could tell us if this has already been done.

@Javier: the bug has not been assigned to a dev so far. I set the priority to "low" because it doesn't impact our default desktop (Unity), we don't use the gnome-settings-daemon print plugin there and that code is not really supported ... you get it because you run a fallback session.

You might want to turn off the gnome-settings-daemon print plugin as a workaround

Till, do you have an issue what could make that error be displayed? gnome-settings-daemon seems to relay the errors/informations from system-config-printer, do you know how to get a debug log for those?

Hi @Sebastien:

Turning off notifications is not a useful workaround, as a user would still expect a notification that the printing has been ok, and this would provoke the same behaviour this issue is provoking, the users ending a documento to print several times.

Unfortunately I'm unsure on how we could get a debug file from system-config-printer, I guess it gets some pieces of info from CUPS, would perhaps CUPS logs give you some information?

@Javier: Till, who is assigned to this bug now, can probably help you to get debug informations for that issue. I'm not sure if system-config-printer has a debug log by itself but I suspect cups logs have some informations. If that's not enough we can still do a debug build of gnome-control-center to get extra details...

Thanks @Sebastien.

@Till I'll be just waiting for any info I might provide in order for you to ease digging into this

The system-config-printer part which is most probably used here is /usr/share/system-config-printer/scp-dbus-service.py. Usually it is started with the rights of the client user via D-Bus (D-Bus session service AFAIK). Try running

/usr/share/system-config-printer/scp-dbus-service.py --debug

in a terminal window and after that the GNOME settings app and watch the output in the terminal.

Hello Till:
running /usr/share/system-config-printer/scp-dbus-service.py --debug did not provide any information when running or printing gnome-settings.

Nevertheless perhaps this other log might be helpful for you. I have taken it from runnig

/usr/share/system-config-printer/system-config-printer.py --debug

I'm uploading outpout as printer.log just in case this was useful

BR

Till, could you have a look to the g-s-d printing plugin and see to what system-config-printer event it could be react to that would lead to the error in the screenshot?

How can I call the g-s-d printing plugin from the command line?

you can't really (new versions have standalone test binary though), you need to stop gnome-settings-daemon and run it with debug option if needed

Seb, so I have to switch to a gnome-fallback session so that I can start the plugin out of the System Settings and restart the gnome-settings-daemon in debug mode before starting the plugin?

Tim, how do I get debug logging of /usr/share/system-config-printer/scp-dbus-service.py when gnome-settings-daemon and/or GNOME's printer setup tool interacts with scp-dbus-service.py?

Just as in comment #10, but you have to make sure it isn't already running first. (Waiting for 30 seconds should be sufficient as it will time out.)

I'm not sure scp-dbus-service is really involved here though.

Hello:

This bug is actually the same that the one for fedora in here https://bugzilla.redhat.com/show_bug.cgi?id=883401 (which I think @Tim knows as he has done some interactions)

Nevertheless, several tries do not actually fix it:

https://launchpad.net/~bencer/+archive/desktop-bugfixes -> this ppa version of gnome-settings daemon implements the blacklist method that was implemented in fedora bug, but as a difference to fedora patch, it for some reason is not notifying when the printer is not reachable for some reason. So, it solves the "ERROR: connecting to printer" but it is not a valid solution as the user is not being notified of actual issues with the printer .

I have as well tried converting rpm from fedora to deb with alien, and installing it, but in such case I do not get any notification at all (not even that the document is sent to the printer)

Perhaps the issue then relies in any other package but I'm not sure in which if them it might be

@Javier: what patch is used in fedora? those fixes should be upstream/in the current version upstream and in Ubuntu

Hello @Sebastien:

I think you wanted this , might be?
https://bugzilla.gnome.org/attachment.cgi?id=230765&action=diff

@Javier: the patch you are point at doesn't filter "connecting-to-device", which is the error you have in your screenshot (which is weird because that doesn't seem an error)

Hello Sebastien:

I think that error is included between one of these conditions (note that the comment points to the Fedora report I mentioned you before):

            /* These reasons should not be shown to users (rhbz#883401) */

            g_str_equal (reason, "other") ||

            g_str_equal (reason, "com.apple.print.recoverable") ||

            g_str_has_prefix (reason, "cups-remote-")) {

BR

@Javier, sorry I don't understand what you mean? The "connecting-to-device" string doesn't match "other" nor "com.apple.print.recoverable" nor start with "cups-remote-"...?

Hello Sabastian, I think that these errors are not the error shown to the user, but some error that cups daemon (or any other related daemon - perhaps through dbus) sends to gnome-settings daemon . I do not know what is the content of the "data" argument in

                                if (!known_reason && !reason_is_blacklisted (data)) {

Perhaps Tim could helps us to clarify this, provided he was the one that opened and confirmed the resolution of this fedora fix

Hello Sebastian:

Is there any advance on this. Could I perform some test that might you help on this?

@Javier: sorry, I don't really know how that code interacts with cups exactly, it could be useful if somebody able to reproduce the issue could add debug statement in the code to see what case is triggered exactly...

Hello Sebastien:

I'm able to reproduce this whenever I want, so if you could tell me detailed instructions on how to add such debug, I would be glad to do it

Hello Sebastien:

Perhaps it could be worthy have a look to https://bugzilla.gnome.org/show_bug.cgi?id=683577

Nevertheless, I have tried building gsd with these changes in code and in Ubuntu it blocks valid notifications (like that the printer is not online)

In Ubuntu 14.10 (Utopic), there are two packages that can be involved in gnome printer norifications: gnome-settings-daemon and unity-settings-daemon. The latter package seems to be a fork of the former, for Unity use I suppose.

These two packages come with a printer notification plugin. The one of gnome-settings-daemon is /usr/lib/gnome-settings-daemon/gsd-printer and the other is /usr/lib/unity-settings-daemon/usd-printer.

I found that if the gnome-flashback session (a.ka. "Gnome Classic") is used, the printer notification plugin involved is usd-printer, from the unity-settings-daemon package. I guess that gsd-printer is used in a Gnome Shell session (I don't use it so I can test my guessing).

So, to remove the connecting-to-printer false error message, I think the safest approach is to patch both packages, just by adding the lines:

 if (g_str_has_prefix (reason, "connecting-to-device"))
         return TRUE;

to the reason_is_blacklisted() static function in gsd-print-notifications-manager.c.

A patch is attached for the gnome-settings-daemon package and I'll also fill a bug report with a patch for the unity-settings-daemon package.

The attachment "suppress-printer-connecting-to-device-notifification.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]