[CUPS print setup] USB connected DYMO LabelWriter450 ppd not accepted by ADD PRINTER settings |
||||
Issue descriptionTesting team has this Thermal Label Printer DYMO LabelWriter 450 Turbo - same as this one - https://www.amazon.com/dp/B0027JIIKQ/ PPD files downloaded with the archive at http://download.dymo.com/dymo/Software/Download%20Drivers/Linux/Download/dymo-cups-drivers-1.4.0.tar.gz I find the printer in the "Add a nearby printer" list - https://screenshot.googleplex.com/xLkZQRNdQUi and after selection and click on ADD, the "Select a printer manufacturer and model" screen prompts for either M/m or PPD file. No matter which one of the 450 model ppd files I choose I get "Profived PPD is invalid - https://screenshot.googleplex.com/5OMMzAGEBwO Attaching one of the ppd files. This is one of the popular thermal printers, we happen to have at teams desks. What is wrong with the file, so the printer does not get added?
,
Nov 8 2017
That PPD references raster2dymolw which is a filter that we don't have. We'd need to add that filter as a component to get Dymo printers to work. This is working as intended. However, if we want to prioritize this manufacturer, we should file a bug for it. *cupsFilter: "application/vnd.cups-raster 0 raster2dymolw"
,
Nov 8 2017
i wonder why it could surface this printer in 'Add a nearby printer' even we do not have ppd file served... is this particular printer a usb or networked?
,
Nov 8 2017
It is USB connected.
,
Nov 8 2017
hi Justin, what's your opinion on this? should we block user provided ppd for printers surfaced in 'Add a nearby printer'?
,
Nov 8 2017
No, I don't think we should block user provided ppds for auto-detected printers. What I *do* think we need to do is provide more specific feedback to the user when a custom ppd is unusable; we should be providing more details than just "add failed" messages. I might even go so far as to say we should preflight-check ppds for some common things that will cause addition to fail, rather than trying to figure out a reason for a failure after the add fails.
,
Nov 9 2017
FYI - Created crbug.com/782984 to track better error messages around this use case. |
||||
►
Sign in to add a comment |
||||
Comment 1 Deleted