Quoting Paul Gevers (2018-08-29 19:58:37) > Control: tags -1 - moreinfo > > On Wed, 29 Aug 2018 09:41:37 +0200 Jonas Smedegaard <jonas@jones.dk> wrote: > > It would be most helpful if someone could dig out from that convoluted > > ci-in-cups test the actual ghostscript command causing cups to hang. > > Looking here: > https://sources.debian.org/src/cups/2.2.8-5/debian/tests/cups/ > > it runs: > /usr/share/cups/test-drivers > > As the log ends with: > * Driver drv:///sample.drv/dymo.ppd > - Create test printer: done. > - Print test job with /usr/share/cups/data/topsecret.pdf: > > I guess it successfully runs this command > /usr/sbin/lpadmin -p $DUMMY_PRINTER_NAME -E -m $driver -v > file:///dev/null > and fails with this command: > rid=$(/usr/bin/lp -d $DUMMY_PRINTER_NAME $file | sed -e > 's/^.*request id is \(.*\) (.*)$/\1/g') > > where > DUMMY_PRINTER_NAME=test-printer0 > driver=drv:///sample.drv/dymo.ppd > file=/usr/share/cups/data/topsecret.pdf > > Is that enough for you to continue? Thanks - that is indeed helpful, but provides only the _cups_ commands. Inside those are some Ghostscript command (and some data) which I would need to check if/what fails with Ghostscript. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Attachment:
signature.asc
Description: signature