Your message dated Sun, 6 Feb 2011 22:34:37 +0100
with message-id <[email protected]>
and subject line Done: cupsys just hangs
has caused the Debian Bug report #298249,
regarding rastertoprint hangs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
298249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298249
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gs-esp
Version: 8.15.3.dfsg
Hi there,
I have had this problem for a long time and already filed two bugs in the past.
One against cupsys: #298249 and one against gs-esp: #274553.
I will tell the story once more. Maybe someone new will look into it. I also
worked on the workaround.
When I print something from PDF or OpenOffice (larger documents seem to do the
trick but other than that I have not really found a pattern, it comes up
seemingly at random) the printer stops working midway through the job with a
couple pages already printed. When I check the webinterface of Cupsys it says
that the document the printer is working on is at xx%. The led of my HP
Laserjet 4 tells me that it is in "receiving" status and waiting for more data.
But nothing happens.
Workaround: I cancel the job and do /etc/init.d/cupsys stop . Then I reset the
printers memory. After that I bring up Top in the console and search for jobs
owned by lp. Two jobs will come up: Rastertoprint and some other job that I
don't remember the name of right now. I kill both using signal 9 (killall lp
would probabely do the same). Then I restart Cupsys.
Just restarting cupsys won't work without killing those two jobs. Switching off
and switching on the printer instead of resetting it leads to a page of
jibberish. If you don't cancel the job Cupsys will start the job from the
beginning as soon as the printer is back.
When I filed the bug against Cupsys back in Sarge they said gs-esp is at fault.
I am actually really surprised that this bug (or some very similar problem)
made it from Sarge all the way to Etch. Maybe this is a Laserjet 4 problem,
though I doubt it. I used straight Cupsys with different drivers and I also
used the hp daemons and drivers and the problem always stays the same.
Thx,
Malte
--
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger
--- End Message ---
--- Begin Message ---
Package: gs-esp
Version: Close
You do not answer the previous three attempt to get moreinformation about this
bug. Close now
--- End Message ---
