Gnome print dialog box poll for printer info every time it's opened

[Franck]

When a printer is defined as a remote printer, using DNS-SD or not, each time you enter a gnome print dialog box, the dialog says : 'Getting printer information...'
This phase sometimes takes several tens of seconds, making the printing process cumbersome...

Applications that don't use gnome print dialog (say openoffice for example) don't suffer from this latency.

This behaviour appeared with Karmic Koala and is still here in Lucid alpha.

=== Workaround ===
echo "ServerName 127.0.0.1" >> /etc/cups/client.conf

[Till Kamppeter (till-kamppeter)]

The printing dialog in the GTK applications is provided by GTK and not by system-config-printer. Moving ...

[Sebastien Bacher (seb128)]

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

[Sebastien Bacher (seb128)]

Thank you for sending the bug to GNOME

[Ayan George (ayan)]

I can reproduce the issue and I'm actively debugging it.

[Alex_L33 (alex-l33)]

I have a local printer connected directly by USB (Epson sylus CX6600) and the process still takes about ten seconds or more, so it can't be a problem only with network-connected device.

 A timeout option somewhere would be nice as most of the time i am quite happy for it to just print with my default settings and not tell me any information anyway.

Additionally, attempting to close the gnome-print dialogue should abort the "fetching printer information" task rather than causing the program from which one was attempting to print to hang while you wait.

[Rodrigo Virote Kassick (kassick)]

I can confirm the bug in Lucid. Disabling the dnssd parameter in
BrowseLocalProtocols in cups.conf and cups.conf.default resolved for me, but I
assume that will kill printer discovery.

[Jakob Unterwurzacher (jakobunt)]

Disabling dnssd didn't help here on 10.04. But this solved it for me (thanks Dominik from bug 475845):
echo "ServerName 127.0.0.1" >> /etc/cups/client.conf
(Note that this file probably does not exist beforehand. Also, you need to restart your applications for it to take effect)