Whenever I print to a printer shared on my network (via CUPS's automatic
discovery protocol), I get a notification message telling me that the
printer is not connected -- after the job is successfully sent to the
print server.

$ lpstat -t
scheduler is running
no system default destination
device for delly: ipp://10.0.0.1:631/printers/delly
device for officejet_4200: ipp://10.0.0.1:631/printers/officejet_4200
delly accepting requests since Wed 10 Nov 2010 10:00:55 GMT
officejet_4200 accepting requests since Wed 10 Nov 2010 10:00:56 GMT
printer delly is idle.  enabled since Wed 10 Nov 2010 10:00:55 GMT
	Ready to print.
printer officejet_4200 is idle.  enabled since Wed 10 Nov 2010 10:00:56 GMT

There are some useful comments on this launchpad report for ubuntu:

https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/842768

Their bug is assigned to gnome-settings-daemon instead, but the cause
is the same.

Basically, the message comes from the fact that cups is reporting
"connecting-to-device".  It doesn't mean that the device is not
connected, which is what the notification conveys.  IMO, this message
should never be displayed because it shouldn't take long to connect to
the device (probably much less than a second).  Also, it will connect in
the same way every time, so even if it did take a while to connect, the
user would get used to that.

I've modified jobviewer.py to suppress this message, but I don't know
much about python so I'm not sure how to get the .py file into the .pyc
file so it'll take effect for testing.  I'll probably have to build a
local package to test it.

I've tested the attached patch (it goes in debian/patches, and you have
to edit series to include it), and it works like a charm.

The only thing I've noticed now is that the printer icon sticks around
after your printing is finished, until you open it and hit Refresh.
I'm not sure if that's normal... but either way it's much less
intrusive than the notification was.

I don't imagine this patch will make it into an update for squeeze, but
I've attached it in case anyone else finds it useful.

Greeting to you once again



I am writing for the second time as I did not receive any reply from you to
my previous message.



Kindly reply so we can discuss the subject as soon as possible.



Sincerely,



Andy Landman