Job is "Completed" in queue - did not print

dustin drange at touchpaydirect.com
Mon Aug 27 12:00:24 PDT 2012


bump...

Also, I have started looking into editing the raster driver. Any pointers for getting my printer to not automatically say a job is completed would be appreciated.


> It dosent seems to be linked... here is the output:
>
> ldd /usr/lib/cups/backend/usb
>
> 	linux-gate.so.1 =>  (0xb7718000)
> 	libusb-0.1.so.4 => /usr/local/lib/libusb-0.1.so.4 (0xb76f4000)
> 	libcups.so.2 => /usr/lib/libcups.so.2 (0xb76aa000)
> 	libc.so.6 => /lib/libc.so.6 (0xb754c000)
> 	libusb-1.0.so.0 => /usr/local/lib/libusb-1.0.so.0 (0xb7540000)
> 	librt.so.1 => /lib/librt.so.1 (0xb7537000)
> 	libpthread.so.0 => /lib/libpthread.so.0 (0xb751d000)
> 	libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0xb74ee000)
> 	libgnutls.so.26 => /usr/lib/libgnutls.so.26 (0xb7452000)
> 	libgcrypt.so.11 => /lib/libgcrypt.so.11 (0xb73de000)
> 	libavahi-common.so.3 => /usr/lib/libavahi-common.so.3 (0xb73d2000)
> 	libavahi-client.so.3 => /usr/lib/libavahi-client.so.3 (0xb73c2000)
> 	libz.so.1 => /lib/libz.so.1 (0xb73ad000)
> 	/lib/ld-linux.so.2 (0xb7719000)
> 	libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0xb72fd000)
> 	libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0xb72d9000)
> 	libcom_err.so.2 => /lib/libcom_err.so.2 (0xb72d5000)
> 	libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0xb72cd000)
> 	libdl.so.2 => /lib/libdl.so.2 (0xb72c9000)
> 	libkeyutils.so.1 => /lib/libkeyutils.so.1 (0xb72c5000)
> 	libresolv.so.2 => /lib/libresolv.so.2 (0xb72b0000)
> 	libtasn1.so.3 => /usr/lib/libtasn1.so.3 (0xb729f000)
> 	libgpg-error.so.0 => /lib/libgpg-error.so.0 (0xb729a000)
> 	libdbus-1.so.3 => /lib/libdbus-1.so.3 (0xb725e000)
>
>
> > Weird, we should be getting an error - I'd expect a timeout on the bulk out transfer - when sending the print data.
> >
> > Is the USB backend in /usr/lib/cups/backend linked against libusb? You can run "ldd /usr/lib/cups/backend/usb" to find out...
> >
> >
> >
> > On Aug 22, 2012, at 1:55 PM, dustin <drange at touchpaydirect.com> wrote:
> >
> > > Michael,
> > >
> > > Thanks for the reply. I might have mislead you when I said remote. The printer is connected via USB to a linux ubuntu box. The linux ubuntu box is the only thing communicating with the printer. The only remote part of it, is that the computer and the printer are not located near. I have to access the computer via ssh or VNC. So with that in mind, that is why I said I cant physically determine if it printed or not. This is why I was wanting the queue to keep any jobs that were not completed.
> > >
> > > I recreate the situation locally and I intentionally cause a out of paper event, but i still see the job in the queue get marked as successful.
> > >
> > > I think it is URI, here is the device "Connection:" inside cups: usb://Swecoin%20AB/TTP%202030
> > >
> > >
> > >> Dustin,
> > >>
> > >> How is the queue configured (device URI) on your CUPS system? Direct USB connections are normally pretty robust for this sort of thing, but you mention the printer is remote so I don't know how you are bridging the gap...
> > >>
> > >>
> > >> On Aug 21, 2012, at 5:44 PM, dustin <drange at touchpaydirect.com> wrote:
> > >>
> > >>> Ok, my question is a bit of a work around for somthing I dont think will be easy to do.
> > >>>
> > >>> If I could just have my jobs not automatically cleared from my queue, unless they are truely printed that would be great. I submit a job and a split second later it is set to completed, even thought it did not print.
> > >>>
> > >>> The base of my problem is that I do not have much error reporting on this driver for my zebra swecoin ttp 2030 kiosk thermal USB printer. The only reporting I have is it being idle - ready to print, or paused - dissconnected / turned off.
> > >>>
> > >>> I am using cups 1.4.4, ttp20x0.ppd, rastertozebrakiosk.c
> > >>>
> > >>> My main goal here is to be able to detect if the printer has been printing properly. I was hoping I could look at the number of jobs in the queue and judging by that I could determine if it is printing. I will have the printer in a remote location so I cant physically notice it printing.
> > >>>
> > >>> It would be even better if I could detect out-of-paper, paper-jam, and any other errors that someone might know about.
> > >>>
> > >>> Thanks for any help!
> > >>> _______________________________________________
> > >>> cups mailing list
> > >>> cups at easysw.com
> > >>> http://lists.easysw.com/mailman/listinfo/cups
> > >>
> > >> _________________________________________________________
> > >> Michael Sweet, Senior Printing System Engineer, PWG Chair
> > >>
> > >
> > > _______________________________________________
> > > cups mailing list
> > > cups at easysw.com
> > > http://lists.easysw.com/mailman/listinfo/cups
> >
> > _________________________________________________________
> > Michael Sweet, Senior Printing System Engineer, PWG Chair
> >
>





More information about the cups mailing list