Hide Forgot
Description of problem: As the API which the dnssd CUPS backend in CUPS 1.4 uses is uncommon or even not available under Linux, I have taken the Avahi support patch from the cups-1.4-0.rc1.16.fc12.src.rpm package so that I could build the backend under Ubuntu. The backend builds and it runs without crashing, but make, model, and device ID fields do not get filled, so printers found by the dnssd backend do not get automatically set up by system-config-printer. Version-Release number of selected component (if applicable): cups 1.4-0.rc1.16.fc12 How reproducible: Have a network-connected printer available and run /usr/lib/cups/backend/dnssd on the command line. Wait until the ntries for your network printer(s) show up and press Ctrl + C then. Example output: ------------------------------------------------------------------------------ network dnssd://A3%20Photo%20Inkjet%20%40%20till-desktop._ipp._tcp.local/ "unknown" "A3 Photo Inkjet @ till-desktop" "" "" network dnssd://Double-sided%20Color%20Laser%20%40%20till-desktop._ipp._tcp.local/ "unknown" "Double-sided Color Laser @ till-desktop" "" "" network dnssd://Fast%20Color%20Multi-Function%20Printer%20%40%20till-desktop._ipp._tcp.local/ "unknown" "Fast Color Multi-Function Printer @ till-desktop" "" "" network dnssd://Fast%20Monochrome%20Laser%20Printer%20%40%20till-desktop._ipp._tcp.local/ "unknown" "Fast Monochrome Laser Printer @ till-desktop" "" "" network dnssd://HP%20LaserJet%203390%20(934614)._pdl-datastream._tcp.local/ "unknown" "HP LaserJet 3390 (934614)" "" "" network dnssd://HP%20LaserJet%20P3005%20%5B2611E3%5D._pdl-datastream._tcp.local/ "unknown" "HP LaserJet P3005 [2611E3]" "" "" network dnssd://Inkjet%20with%20CD%20tray%20%40%20till-desktop._ipp._tcp.local/ "unknown" "Inkjet with CD tray @ till-desktop" "" "" network dnssd://Monochrome%20laser%20multi-function%20(fax)%20%40%20till-desktop._ipp._tcp.local/ "unknown" "Monochrome laser multi-function (fax) @ till-desktop" "" "" network dnssd://Monochrome%20laser%20multi-function%20%40%20till-desktop._ipp._tcp.local/ "unknown" "Monochrome laser multi-function @ till-desktop" "" "" network dnssd://Photo%20Inkjet%20Printer%20A4,%206%20inks%20%40%20till-desktop._ipp._tcp.local/ "unknown" "Photo Inkjet Printer A4, 6 inks @ till-desktop" "" "" network dnssd://Photosmart%20C8100%20series%20%5B06F23C%5D._pdl-datastream._tcp.local/ "unknown" "Photosmart C8100 series [06F23C]" "" "" network dnssd://Photosmart%20Pro%20B9100%20series%20%5BCC9932%5D._pdl-datastream._tcp.local/ "unknown" "Photosmart Pro B9100 series [CC9932]" "" "" network dnssd://Single-sided%20color%20laser%20%40%20till-desktop._ipp._tcp.local/ "unknown" "Single-sided color laser @ till-desktop" "" "" network dnssd://hp%20designjet%20130nr%20(C7791D)%20%5BE739F1%5D._pdl-datastream._tcp.local/ "unknown" "hp designjet 130nr (C7791D) [E739F1]" "" "" ------------------------------------------------------------------------------ Note that the 2nd field (make/model) is always filled with "unknown" and the fifth field (device ID) is always empty. These should ne filled with manufacturer/model and with the device ID. See the results of other backends (usb, hp, ...) as example. Note that Avahi is capable to retrieve this data. My discovery-only dnssd backend http://www.openprinting.org/download/printing/dnssd polls make/model info without problems.
Thanks for the report. The backend was reporting devices before avahi resolution had completed. Note that it keys off the 'product' field if available, which may only contain a model name without the manufacturer name present. There is also no preference order for which keys to use. These are both upstream issues.