I ran into this bug too on about a dozen different machines.  Every
printer connected via USB displayed the same behavior.  It would print
once, then jetpipe would crash.  Most parallel printers were fine,
although a couple would crash as well.

To debug, I ran jetpipe from a command line (outside of LTSP).  I went
to another machine and configured a CUPS printer and pointed it to the
ip address and port that jetpipe was running on.   After the first print
job went through, the socket tried to respawn before the old one died,
causing an error that crashed the script.

I added the "time.sleep(5)" statement, as Faraz recommended, and that
fixed it.  For anybody else out there who needs to patch jetpipe, you
also have to add the "import time" statement just under the other
"import" statements.  Otherwise, the time.sleep(5) statement won't work.
This is probably obvious to experienced python programmers.

I am wondering why the socket needs to close and re-open after there is
no more data received.  Is there any downside to just leaving the socket
up and listening all the time?

-- 
jetpipe crashes on print
https://bugs.launchpad.net/bugs/110609
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to