Comment 35 for bug 1069671

Revision history for this message
Daniel Richard G. (skunk) wrote :

The IPP-version patch does not appear to (fully) fix the problem.

I'm testing a build of 1.6.1-2 on Quantal. It works if I specify the server hostname (with version directive) on the command line, but not if I specify same via the CUPS_SERVER environment variable or /etc/cups/client.conf:

    $ lpq -h cups-server.example.com/version=1.1
    WARNING: gnome-keyring:: couldn't connect to: /run/user/dgomez/keyring-VYcpvh/pkcs11: No such file or directory
    defprint is ready
    no entries

    $ CUPS_SERVER=cups-server.example.com/version=1.1 lpq
    WARNING: gnome-keyring:: couldn't connect to: /run/user/dgomez/keyring-VYcpvh/pkcs11: No such file or directory
    lpq: Unable to connect to server.

    $ cat /etc/cups/client.conf
    ServerName cups-server.example.com/version=1.1
    Encryption Required
    $ lpq
    WARNING: gnome-keyring:: couldn't connect to: /run/user/dgomez/keyring-VYcpvh/pkcs11: No such file or directory
    lpq: Unable to connect to server.

I traced through the code a bit, and found that in the latter two cases, CUPS is actually doing a DNS lookup on "cups-server.example.com/version=1.1". It never calls cupsSetServer().