Comment 6 for bug 196429

On Sat, Mar 08, 2008 at 03:05:09PM -0000, Sebastien Bacher wrote:
> Could you describe easy steps to create the issue?

I assume you have some sort of non-network printer being served
by a cups server on machine 192.168.1.16 (any IP will do).

On a client machine

edit /etc/cups/client.conf so it reads

ServerName 192.168.1.16

Arrange for there to be no reverse DNS mapping for 192.168.1.16
on your client machine.

That would mean make sure it is not defined in /etc/hosts, and
that your DNS server has no reverse resolution for 192.168.1.16.
I would suggest getting rid of any forward resolution if you
want to be extra sure.

Make sure there are no caching DNS data tables laying about on
the client machine.

Basically you want this command

% host 192.168.1.16

to return

Host 16.1.186.192.in-addr.arpa not found: 3(NXDOMAIN)

on the client machine.

restart cupsys on the client machine.

Use the GTK print dialog from evince or the system menu
print configurator.

The GTK print dialog will show a greyed out print button.

The print configurator will report an error reaching cups.

However, cups is working fine. lpr and other non-GTK
dialog print code will all work.

> ** Changed in: gtk+2.0 (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
> Status: Confirmed => Incomplete
> --
> evince/evolution/gtk-print-dialog printing and system-config-printer fail when using client.conf with IP address for which there is no reverse look-up available
> https://bugs.launchpad.net/bugs/196429
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Source Package "gtk+2.0" in Ubuntu: Incomplete
> Status in Source Package "system-config-printer" in Ubuntu: Confirmed
>
> Bug description:
> I ran into the 'greyed out print button' in evince in gutsy 7.10.
>
> I was working with a network printer and it worked via
> lpr and in fact any tool that did not rely on the GTK
> print dialog.
>
> Evince and evolution were clearly broken. As was the system
> printer configurator via the menu. It kept dying after reporting
> an error connecting to cups.
>
> I could use xpdf instead of evince and print fine. I could
> also use the GTK dialog to print to a file and then send the
> file to the printer using any non-GTK tool.
>
> In /etc/cups/client.conf I had put
>
> ServerName 192.168.1.16
>
> In the end the problem was that I did not have an entry
> in /etc/hosts for 192.168.1.16.
>
> If I add an entry like
>
> 192.168.1.16 printer.mydomain.tld printer
>
> then everything works well including evince and evolution.
>
> Without that entry or a similar one in /etc/hosts, all the programs
> that use the GTK print dialog malfunction and the system print
> configurator dies.
>