print problem (a tough one)

The Natural Philosopher writes:
> reboot the system - this usually cleans out spooled files..

I wrote:
> lprm will do that.

philo writes:
> Nope

Yup. lprm will clean out spooled files.

> already tried that both as user and as root

Your problem is not spooled files. It is material buffered up in your
printer.
--
John Hasler
john.TakeThisOut@dhh.gt.org
Dancing Horse Hill
Elmwood, WI USA

"John Hasler" <john DeleteThis @dhh.gt.org> wrote in message
news:87tz0e3rrg.fsf@thumper.dhh.gt.org...
> The Natural Philosopher writes:
>> reboot the system - this usually cleans out spooled files..
>
> I wrote:
>> lprm will do that.
>
> philo writes:
>> Nope
>
> Yup. lprm will clean out spooled files.
>
>> already tried that both as user and as root
>
> Your problem is not spooled files. It is material buffered up in your
> printer.



OK...reasonable thought ...but:

when I used the command lprm it showed that there were no print jobs...

so it certainly makes sense that there was "material buffered" in the
printer...

however, I could boot over to another OS and the printer worked fine
there...
but as soon as I booted back to Fedora 10...
the printer still continued printing garbage... (until it finally ran it's
course)
so that implies the the job was still there (somewhere) in the OS

killing Cups, rebooting then restarting Cups was the only way I have figured
out to clear it.


Anyway...since this seems to happen when I print from a Win-app under
Wine...
I have since upgraded the Win-app to a newer version.

Since the problem can occur two times in a row....or not happen for several
months...
It will take me a while to get this figured out one way or the other.

John Hasler wrote:
> The Natural Philosopher writes:
>> reboot the system - this usually cleans out spooled files..
>
> I wrote:
>> lprm will do that.
>
> philo writes:
>> Nope
>
> Yup. lprm will clean out spooled files.
>
>> already tried that both as user and as root
>
> Your problem is not spooled files. It is material buffered up in your
> printer.
Bitter experience says this is not necessarily the case.

There are loads of intermediate files in the avearage CUPS process..the
file you queue, the file that gets created as a temporary postcript
entity..then on some non postcript printers, the file that is in the
printers native dialect. Plus the file that exists in the printer meory.

I've actually cleaned these out by hand on earlier LP systems..

I THINK disabling the printer queue itself via CUPS removes all the
temps, but I wouldn't bet on it..

The Natural Philosopher writes:
> There are loads of intermediate files in the avearage CUPS process...

CUPS... Sorry. I was forgetting that he's not using a sane printing
package.
--
John Hasler
john.DeleteThis@dhh.gt.org
Dancing Horse Hill
Elmwood, WI USA

On Tue, 11 Aug 2009 18:53:10 -0400, philo <philo.RemoveThis@privacy.net> wrote:

> Anyway...since this seems to happen when I print from a Win-app under
> Wine...

I don't use wine. Does it have it's own print manager, that may be
queuing the document?

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

<snip>
>>
>> Your problem is not spooled files. It is material buffered up in your
>> printer.
> Bitter experience says this is not necessarily the case.
>
> There are loads of intermediate files in the avearage CUPS process..the
> file you queue, the file that gets created as a temporary postcript
> entity..then on some non postcript printers, the file that is in the
> printers native dialect. Plus the file that exists in the printer meory.
>
> I've actually cleaned these out by hand on earlier LP systems..
>
> I THINK disabling the printer queue itself via CUPS removes all the temps,
> but I wouldn't bet on it..
>

Well, considering that stopping Cups was the only thing that worked,
it must have removed all the temps

"David W. Hodgins" <dwhodgins RemoveThis @nomail.afraid.org> wrote in message
news:op.uyiwytuaa3w0dxdave@hodgins.homeip.net...
> On Tue, 11 Aug 2009 18:53:10 -0400, philo <philo RemoveThis @privacy.net> wrote:
>
>> Anyway...since this seems to happen when I print from a Win-app under
>> Wine...
>
> I don't use wine. Does it have it's own print manager, that may be
> queuing the document?
>


Not that I know of,

philo wrote:
> <snip>
>>> Your problem is not spooled files. It is material buffered up in your
>>> printer.
>> Bitter experience says this is not necessarily the case.
>>
>> There are loads of intermediate files in the avearage CUPS process..the
>> file you queue, the file that gets created as a temporary postcript
>> entity..then on some non postcript printers, the file that is in the
>> printers native dialect. Plus the file that exists in the printer meory.
>>
>> I've actually cleaned these out by hand on earlier LP systems..
>>
>> I THINK disabling the printer queue itself via CUPS removes all the temps,
>> but I wouldn't bet on it..
>>
>
> Well, considering that stopping Cups was the only thing that worked,
> it must have removed all the temps
>
>
Ah. I'll file that for future reference..

WE had an issue like that..a site I do a bit of IT management for has
two color lasers, in case one breaks. One was low on ink, and the ruddy
thing caused CUPS to flag it as 'stopped'. Foolishly I started it
without checking the queues..'Oh its been like that a couple of weeks.
Works from windows, but not from the Linux server'

removed the queues, but had a devils own job with one print job.. I
couldn't remember what I did, because I tried everything..

The Natural Philosopher wrote:
> philo wrote:
>> <snip>
>>>> Your problem is not spooled files. It is material buffered up in your
>>>> printer.
>>> Bitter experience says this is not necessarily the case.
>>>
>>> There are loads of intermediate files in the avearage CUPS
>>> process..the file you queue, the file that gets created as a
>>> temporary postcript entity..then on some non postcript printers, the
>>> file that is in the printers native dialect. Plus the file that
>>> exists in the printer meory.
>>>
>>> I've actually cleaned these out by hand on earlier LP systems..
>>>
>>> I THINK disabling the printer queue itself via CUPS removes all the
>>> temps, but I wouldn't bet on it..
>>>
>>
>> Well, considering that stopping Cups was the only thing that worked,
>> it must have removed all the temps
>>
> Ah. I'll file that for future reference..
>
> WE had an issue like that..a site I do a bit of IT management for has
> two color lasers, in case one breaks. One was low on ink, and the ruddy
> thing caused CUPS to flag it as 'stopped'. Foolishly I started it
> without checking the queues..'Oh its been like that a couple of weeks.
> Works from windows, but not from the Linux server'
>
> removed the queues, but had a devils own job with one print job.. I
> couldn't remember what I did, because I tried everything..
>
>
>


Well

I updated the Win-app

removed any non-needed printing-related software

and went to print...and got the same thing.

gibbirish!


Killing cups and rebooting was the only way to stop it...
so if anything, the problem is actually getting worse
as it used to only happen occasionally!

The Natural Philosopher <t....DeleteThis@invalid.invalid> wrote:
> John Hasler wrote:
>
> > Your problem is not spooled files.  It is material buffered up in your
> > printer.
>
> Bitter experience says this is not necessarily the case.
>
> There are loads of intermediate files in the avearage CUPS process..the
> file you queue, the file that gets created as a temporary postcript
> entity..then on some non postcript printers, the file that is in the
> printers native dialect. Plus the file that exists in the printer meory.
>
> I've actually cleaned these out by hand on earlier LP systems..
>
> I THINK disabling the printer queue itself via CUPS removes all the
> temps, but I wouldn't bet on it.

I would sure like an O'Reilley book on CUPS! Or one in any of the
other series of tutorial books. The short howto files I've found so
far have left me digging through assorted directory trees with find.

Doug Freyburger wrote:
> The Natural Philosopher <t....DeleteThis@invalid.invalid> wrote:
>> John Hasler wrote:
>>
>>> Your problem is not spooled files. It is material buffered up in your
>>> printer.
>> Bitter experience says this is not necessarily the case.
>>
>> There are loads of intermediate files in the avearage CUPS process..the
>> file you queue, the file that gets created as a temporary postcript
>> entity..then on some non postcript printers, the file that is in the
>> printers native dialect. Plus the file that exists in the printer meory.
>>
>> I've actually cleaned these out by hand on earlier LP systems..
>>
>> I THINK disabling the printer queue itself via CUPS removes all the
>> temps, but I wouldn't bet on it.
>
> I would sure like an O'Reilley book on CUPS! Or one in any of the
> other series of tutorial books. The short howto files I've found so
> far have left me digging through assorted directory trees with find.



well it will give me something to do!

philo <philo RemoveThis @privacy.net> writes:

>The Natural Philosopher wrote:
>> philo wrote:
>>> <snip>
>>>>> Your problem is not spooled files. It is material buffered up in your
>>>>> printer.
>>>> Bitter experience says this is not necessarily the case.
>>>>
>>>> There are loads of intermediate files in the avearage CUPS
>>>> process..the file you queue, the file that gets created as a
>>>> temporary postcript entity..then on some non postcript printers, the
>>>> file that is in the printers native dialect. Plus the file that
>>>> exists in the printer meory.
>>>>
>>>> I've actually cleaned these out by hand on earlier LP systems..
>>>>
>>>> I THINK disabling the printer queue itself via CUPS removes all the
>>>> temps, but I wouldn't bet on it..
>>>>
>>>
>>> Well, considering that stopping Cups was the only thing that worked,
>>> it must have removed all the temps
>>>
>> Ah. I'll file that for future reference..
>>
>> WE had an issue like that..a site I do a bit of IT management for has
>> two color lasers, in case one breaks. One was low on ink, and the ruddy
>> thing caused CUPS to flag it as 'stopped'. Foolishly I started it
>> without checking the queues..'Oh its been like that a couple of weeks.
>> Works from windows, but not from the Linux server'
>>
>> removed the queues, but had a devils own job with one print job.. I
>> couldn't remember what I did, because I tried everything..
>>
>>
>>


>Well

>I updated the Win-app

>removed any non-needed printing-related software

>and went to print...and got the same thing.

>gibbirish!


>Killing cups and rebooting was the only way to stop it...
>so if anything, the problem is actually getting worse
>as it used to only happen occasionally!

That is great. Now you can actually have something to debug. The worst
things are those that happen on ly very sporadically.

Unruh wrote:
> philo <philo RemoveThis @privacy.net> writes:
>
>> The Natural Philosopher wrote:
>>> philo wrote:
>>>> <snip>
>>>>>> Your problem is not spooled files. It is material buffered up in your
>>>>>> printer.
>>>>> Bitter experience says this is not necessarily the case.
>>>>>
>>>>> There are loads of intermediate files in the avearage CUPS
>>>>> process..the file you queue, the file that gets created as a
>>>>> temporary postcript entity..then on some non postcript printers, the
>>>>> file that is in the printers native dialect. Plus the file that
>>>>> exists in the printer meory.
>>>>>
>>>>> I've actually cleaned these out by hand on earlier LP systems..
>>>>>
>>>>> I THINK disabling the printer queue itself via CUPS removes all the
>>>>> temps, but I wouldn't bet on it..
>>>>>
>>>> Well, considering that stopping Cups was the only thing that worked,
>>>> it must have removed all the temps
>>>>
>>> Ah. I'll file that for future reference..
>>>
>>> WE had an issue like that..a site I do a bit of IT management for has
>>> two color lasers, in case one breaks. One was low on ink, and the ruddy
>>> thing caused CUPS to flag it as 'stopped'. Foolishly I started it
>>> without checking the queues..'Oh its been like that a couple of weeks.
>>> Works from windows, but not from the Linux server'
>>>
>>> removed the queues, but had a devils own job with one print job.. I
>>> couldn't remember what I did, because I tried everything..
>>>
>>>
>>>
>
>
>> Well
>
>> I updated the Win-app
>
>> removed any non-needed printing-related software
>
>> and went to print...and got the same thing.
>
>> gibbirish!
>
>
>> Killing cups and rebooting was the only way to stop it...
>> so if anything, the problem is actually getting worse
>> as it used to only happen occasionally!
>
> That is great. Now you can actually have something to debug. The worst
> things are those that happen on ly very sporadically.
>


for the time being I think I'm just going to turn Cups off
and start it up only if I need it.

about one crossword puzzle a day is the extent of my printing!