pseudonomous has reported this problem upstream as

https://www.cups.org/str.php?L4444

and the problem got fixed. The fix will be available in the next
upstream release, version 1.7.4.

** Changed in: cups (Ubuntu)
       Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1334449

Title:
  typo in debugging output from backend/dnssd

Status in “cups” package in Ubuntu:
  Triaged

Bug description:
  If for debugging purposes one reads the output from running:

  /usr/lib/cups/backend/dnssd

  at the command line, one will see statements like:

  DEBUG: Found "Sales._ipp._tcpzeroconf.org"...
  DEBUG: Querying "Sales._ipp._tcp.zeroconf.org"...
  DEBUG: sent=0, count=1
  DEBUG: Found "Stuart's Home AirPrint Printer._ipp._tcpzeroconf.org"...
  DEBUG: Found "3rd. Floor Copy Room._ipp._tcpzeroconf.org"...
  DEBUG: Found "Engineering._ipp._tcpzeroconf.org"...
  DEBUG: Found "Marketing._ipp._tcpzeroconf.org"...

  The domain component is not separated from the 'protocol component' of
  the dns record.

  I have been unable to get cups to work with non-local (I mean services
  that are not served up by mdns in the domain .local) dns-sd ipp
  printers.  (using unicast dns, I have gotten this to work with cups on
  OS X 10.6).  I kept getting a DNS error:

  ERROR: DNS failure: NXDOMAIN

  At first I believed this was because the dns name was being
  constructed incorrectly, but after reading the source, I believe the
  problem is unrelated.

  At any rate, it's  a stupid bug and ERROR: DNS failure: NXDOMAIN
  ERROR: DNS failure: NXDOMAIN
  it should be fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1334449/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to