Date: Fri, 6 Jun 2014 02:15:22 -0700 (PDT) From: Beeblebrox <zaphod@berentweb.com> To: freebsd-ports@freebsd.org Subject: Re: print/cups-base web interface broken & unable to print Message-ID: <1402046122363-5918422.post@n5.nabble.com> In-Reply-To: <CABG_4jkUHUM3HqDADZo9503esOw7sh73J1-%2B-SMB%2BBMZaJnAzg@mail.gmail.com> References: <1401958638341-5918098.post@n5.nabble.com> <1401987639244-5918202.post@n5.nabble.com> <20140606085156.15b32a6c@tmu.ulm.sysgo.com> <CABG_4jkUHUM3HqDADZo9503esOw7sh73J1-%2B-SMB%2BBMZaJnAzg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
@Robert I ran poudriere for the installed cups* ports and did an upgrade. The missing commandtops file was restored when upgrade installed cups-image (not cups-filter), so that problem is resolved. Printing still fails though. I have a Virtual-PDF printer defined in cups with Generic PPD. To simplify, I decided to test with this printer and again got "Filter Failed" message. Link to log with "level debug" for this job: https://docs.google.com/document/d/1YDWcTll0IFu-JUfhGCX1m2IT7gPxwqw0qoEa9_7X2J0/edit?usp=sharing Virtual-PDF PPD: DeviceURI cups-pdf:/ *FormatVersion: "4.3" *FileVersion: "1.1" *LanguageVersion: English *LanguageEncoding: ISOLatin1 *PCFileName: "CUPS-PDF.PPD" *Manufacturer: "Generic" *Product: "(CUPS v1.1)" *ModelName: "Generic CUPS-PDF Printer" *1284DeviceID: "MFG:Generic;MDL:CUPS-PDF Printer;DES:Generic CUPS-PDF Printer;CLS:PRINTER;$ *% cupsFilter: "application/vnd.cups-postscript 0 pstitleiconv" *PSVersion: "(2017.000) 0" *LanguageLevel: "2" *ColorDevice: True *DefaultColorSpace: RGB *FileSystem: False *Throughput: "8" *LandscapeOrientation: Plus90 *TTRasterizer: Type42 Separately, I have noticed a potentially incompatible option setting as below: print/cups-base (MDNSRESPONDER or AVAHI) print/cups-filters (AVAHI) I don't want to use Zeroconf at all, so I prefer to turn these options off. While print/cups-filters gets built with UNSET AVAHI, print/cups-base does not and requires that at least ONE of the Zeroconf options have been enabled. I have no idea how compatible the resulting binaries will be when Avahi is used in port but MDNS in another. Thanks & Regards. ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/print-cups-base-web-interface-broken-unable-to-print-tp5918098p5918422.html Sent from the freebsd-ports mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1402046122363-5918422.post>