print problem (a tough one)

Unruh wrote:
> philo <philo.RemoveThis@privacy.net> writes:
>
>
>> I posted this before and got a reply that I thought
>> was going to work.
>
>> Been using Fedora 10 since the beginning of the year
>> and on a few rare occasions when I've gone to print...
>> I get a runaway process and end up with 20 or more pages of gibberish
>> that *cannot* be stopped.
>
>> I have killed *all* print jobs.
>> Turned the printer off, disconnected it and even rebooted
>> a number of times...but the print cannot be stopped until
>> it decides to quit on it's own.
>
>
>> The advice I got was to issue the command lprm
>
>> but today when my printer ran away and I issued the command...
>> the message I got was: no print jobs to be stopped
>
>
>> There surely must be some way to kill a runaway print
>> process .
>
> There is, but there are conditions.
> If the job has already been sent to the printer (ie is in the printer )
> then you cannot stop it from the computer. YOu have to switch off the
> printer. If it is in the computer (lpq should show it, assume it is the
> default printer, otherwise lpq -P nameofprinter) then you can use lprm.
> Note that your printer could be attached to another comptuer and you are
> sending the printerjob to it over the net.
>
>
>
>> any ideas?


printer is local

and yes, I turned the machine totally off

turned printer totally off

unplugged printer

issued the command lprm but no job is there to kill



but upon reboot, it keeps printing gibberish


machine is setup to multi-boot and I can run another Linux distro or
boot to Windows and it's fine


but when I boot back to Fedora, the job continues until it finally quits
on it's own.

Next time it happens I think I'll try stopping Cups

don't know what else to try

FWIW: I am current on my updates

philo wrote:
>
> I posted this before and got a reply that I thought
> was going to work.
>
> Been using Fedora 10 since the beginning of the year
> and on a few rare occasions when I've gone to print...
> I get a runaway process and end up with 20 or more pages of gibberish
> that *cannot* be stopped.
>

Ah. Postcript into an ASCII printer? a common probvblem..

> I have killed *all* print jobs.
> Turned the printer off, disconnected it and even rebooted
> a number of times...but the print cannot be stopped until
> it decides to quit on it's own.
>

Mmm. That can happen.

Usual thing to do ois

1/. pull the paper tray to halt printer
2/. Power printer off.
3/. Cancel all jobs..use lpq/cancel to ensure this.
4/. stop the printer
5/. reboot the system - this usually cleans out spooled files..
6/. switch printer on
7/. restart the print queue system.

>
> The advice I got was to issue the command lprm
>
> but today when my printer ran away and I issued the command...
> the message I got was: no print jobs to be stopped
>
>
> There surely must be some way to kill a runaway print
> process .
>
> any ideas?

philo <philo DeleteThis @privacy.net> writes:

>Unruh wrote:
>> philo <philo DeleteThis @privacy.net> writes:
>>
>>
>>> I posted this before and got a reply that I thought
>>> was going to work.
>>
>>> Been using Fedora 10 since the beginning of the year
>>> and on a few rare occasions when I've gone to print...
>>> I get a runaway process and end up with 20 or more pages of gibberish
>>> that *cannot* be stopped.
>>
>>> I have killed *all* print jobs.
>>> Turned the printer off, disconnected it and even rebooted
>>> a number of times...but the print cannot be stopped until
>>> it decides to quit on it's own.
>>
>>
>>> The advice I got was to issue the command lprm
>>
>>> but today when my printer ran away and I issued the command...
>>> the message I got was: no print jobs to be stopped
>>
>>
>>> There surely must be some way to kill a runaway print
>>> process .
>>
>> There is, but there are conditions.
>> If the job has already been sent to the printer (ie is in the printer )
>> then you cannot stop it from the computer. YOu have to switch off the
>> printer. If it is in the computer (lpq should show it, assume it is the
>> default printer, otherwise lpq -P nameofprinter) then you can use lprm.
>> Note that your printer could be attached to another comptuer and you are
>> sending the printerjob to it over the net.
>>
>>
>>
>>> any ideas?


>printer is local

USB, parallel port or network?


>and yes, I turned the machine totally off

Jobs are queued. Ie saved on disk. Or your printer may have an internal
disk/flash-rom to que jobs.


>turned printer totally off

>unplugged printer

>issued the command lprm but no job is there to kill

lpstat -o
as root.






>but upon reboot, it keeps printing gibberish


>machine is setup to multi-boot and I can run another Linux distro or
>boot to Windows and it's fine


>but when I boot back to Fedora, the job continues until it finally quits
>on it's own.

>Next time it happens I think I'll try stopping Cups

Which will make sure you cannot print. the job is queued.


>don't know what else to try

>FWIW: I am current on my updates

What kind of gibberish is it printing? What kind of file are you trying
to print?

The Natural Philosopher wrote:

> philo wrote:
>>
>> I posted this before and got a reply that I thought
>> was going to work.
>>
>> Been using Fedora 10 since the beginning of the year
>> and on a few rare occasions when I've gone to print...
>> I get a runaway process and end up with 20 or more pages of gibberish
>> that *cannot* be stopped.
>>
>
> Ah. Postcript into an ASCII printer? a common probvblem..
>
>> I have killed *all* print jobs.
>> Turned the printer off, disconnected it and even rebooted
>> a number of times...but the print cannot be stopped until
>> it decides to quit on it's own.
>>
>
> Mmm. That can happen.
>
> Usual thing to do ois
>
> 1/. pull the paper tray to halt printer
> 2/. Power printer off.
> 3/. Cancel all jobs..use lpq/cancel to ensure this.
> 4/. stop the printer
> 5/. reboot the system - this usually cleans out spooled files..
> 6/. switch printer on
> 7/. restart the print queue system.
>
>>
>> The advice I got was to issue the command lprm
>>
>> but today when my printer ran away and I issued the command...
>> the message I got was: no print jobs to be stopped
>>
>>
>> There surely must be some way to kill a runaway print
>> process .
>>
>> any ideas?

for cups......

In a browser

http://localhost:631/

Then select Manage Jobs

On Aug 11, 7:23 am, philo <ph... RemoveThis @privacy.net> wrote:
> Unruh wrote:
> > philo <ph... RemoveThis @privacy.net> writes:
>
> >> Unruh wrote:
> >>> philo <ph... RemoveThis @privacy.net> writes:
>
> >>>> I posted this before and got a reply that I thought
> >>>> was going to work.
> >>>> Been using Fedora 10 since the beginning of the year
> >>>> and on a few rare occasions when I've gone to print...
> >>>> I get a runaway process and end up with 20 or more pages of gibberish
> >>>> that *cannot* be stopped.
> >>>> I have killed *all* print jobs.
> >>>> Turned the printer off, disconnected it and even rebooted
> >>>> a number of times...but the print cannot be stopped until
> >>>> it decides to quit on it's own.
>
> >>>> The advice I got was to issue the command lprm
> >>>> but today when my printer ran away and I issued the command...
> >>>> the message I got was: no print jobs to be stopped
>
> >>>> There surely must be some way to kill a runaway print
> >>>> process .
> >>> There is, but there are conditions.
> >>> If the job has already been sent to the printer (ie is in the printer )
> >>> then you cannot stop it from the computer. YOu have to switch off the
> >>> printer. If it is in the computer (lpq should show it, assume it is the
> >>> default printer, otherwise lpq -P nameofprinter) then you can use lprm.
> >>> Note that your printer could be attached to another comptuer and you are
> >>> sending the printerjob to it over the net.
>
> >>>> any ideas?
>
> >> printer is local
>
> > USB, parallel port or network?
>
> >> and yes, I turned the machine totally off
>
> > Jobs are queued. Ie saved on disk. Or your printer may have an internal
> > disk/flash-rom to que jobs.
>
> >> turned printer totally off
>
> >> unplugged printer
>
> >> issued the command lprm but no job is there to kill
>
> > lpstat -o
> > as root.
>
> >> but upon reboot, it keeps printing gibberish
>
> >> machine is setup to multi-boot and I can run another Linux distro or
> >> boot to Windows and it's fine
>
> >> but when I boot back to Fedora, the job continues until it finally quits
> >> on it's own.
>
> >> Next time it happens I think I'll try stopping Cups
>
> > Which will make sure you cannot print. the job is queued.
>
> >> don't know what else to try
>
> >> FWIW: I am current on my updates
>
> > What kind of gibberish is it printing? What kind of file are you trying
> > to print?
>
> The printer is an old Epson Stylus color 740 using the parallel port.
>
> I only use it for printing out crossword puzzles or text.
>
> I have a number of printing packages and utilities I do not need,
> so will uninstall them.
>
> Since this problem has only occurred within the last 4 months or so,
> I may need to roll back to a former version of Cups
>
> Due to the many dependencies, that maynot be an easy task

Or update to Fedora 11. CUPS and the ghostscript on which it relies
for its printer drivers are fairly rapidly evolvong packages, and have
to be. as printer information gets updated.

Baho Utot wrote:
> The Natural Philosopher wrote:
>
>> philo wrote:
>>> I posted this before and got a reply that I thought
>>> was going to work.
>>>
>>> Been using Fedora 10 since the beginning of the year
>>> and on a few rare occasions when I've gone to print...
>>> I get a runaway process and end up with 20 or more pages of gibberish
>>> that *cannot* be stopped.
>>>
>> Ah. Postcript into an ASCII printer? a common probvblem..
>>
>>> I have killed *all* print jobs.
>>> Turned the printer off, disconnected it and even rebooted
>>> a number of times...but the print cannot be stopped until
>>> it decides to quit on it's own.
>>>
>> Mmm. That can happen.
>>
>> Usual thing to do ois
>>
>> 1/. pull the paper tray to halt printer
>> 2/. Power printer off.
>> 3/. Cancel all jobs..use lpq/cancel to ensure this.
>> 4/. stop the printer
>> 5/. reboot the system - this usually cleans out spooled files..
>> 6/. switch printer on
>> 7/. restart the print queue system.
>>
>>> The advice I got was to issue the command lprm
>>>
>>> but today when my printer ran away and I issued the command...
>>> the message I got was: no print jobs to be stopped
>>>
>>>
>>> There surely must be some way to kill a runaway print
>>> process .
>>>
>>> any ideas?
>
> for cups......
>
> In a browser
>
> http://localhost:631/
>
> Then select Manage Jobs


Well, I managed to clear the "gibberish" by stopping cups
rebooting.
then restarting cups...

so I have at least found a way to get the system to stop spewing out 20
pages of waste ...but now I need to prevent the problem from occurring
in the first place.

I have a bunch of spare printers so maybe I'll try another one to see if
the problem is in the specific driver for my printer...or is a larger
problem with cups itself...

of course I'll have to order ink so may not get around to this for a while

Unruh wrote:
> philo <philo DeleteThis @privacy.net> writes:
>
>> Unruh wrote:
>>> philo <philo DeleteThis @privacy.net> writes:
>>>
>>>
>>>> I posted this before and got a reply that I thought
>>>> was going to work.
>>>> Been using Fedora 10 since the beginning of the year
>>>> and on a few rare occasions when I've gone to print...
>>>> I get a runaway process and end up with 20 or more pages of gibberish
>>>> that *cannot* be stopped.
>>>> I have killed *all* print jobs.
>>>> Turned the printer off, disconnected it and even rebooted
>>>> a number of times...but the print cannot be stopped until
>>>> it decides to quit on it's own.
>>>
>>>> The advice I got was to issue the command lprm
>>>> but today when my printer ran away and I issued the command...
>>>> the message I got was: no print jobs to be stopped
>>>
>>>> There surely must be some way to kill a runaway print
>>>> process .
>>> There is, but there are conditions.
>>> If the job has already been sent to the printer (ie is in the printer )
>>> then you cannot stop it from the computer. YOu have to switch off the
>>> printer. If it is in the computer (lpq should show it, assume it is the
>>> default printer, otherwise lpq -P nameofprinter) then you can use lprm.
>>> Note that your printer could be attached to another comptuer and you are
>>> sending the printerjob to it over the net.
>>>
>>>
>>>
>>>> any ideas?
>
>
>> printer is local
>
> USB, parallel port or network?
>
>
>> and yes, I turned the machine totally off
>
> Jobs are queued. Ie saved on disk. Or your printer may have an internal
> disk/flash-rom to que jobs.
>
>
>> turned printer totally off
>
>> unplugged printer
>
>> issued the command lprm but no job is there to kill
>
> lpstat -o
> as root.
>
>
>
>
>
>
>> but upon reboot, it keeps printing gibberish
>
>
>> machine is setup to multi-boot and I can run another Linux distro or
>> boot to Windows and it's fine
>
>
>> but when I boot back to Fedora, the job continues until it finally quits
>> on it's own.
>
>> Next time it happens I think I'll try stopping Cups
>
> Which will make sure you cannot print. the job is queued.
>
>
>> don't know what else to try
>
>> FWIW: I am current on my updates
>
> What kind of gibberish is it printing? What kind of file are you trying
> to print?
>


The printer is an old Epson Stylus color 740 using the parallel port.

I only use it for printing out crossword puzzles or text.

I have a number of printing packages and utilities I do not need,
so will uninstall them.

Since this problem has only occurred within the last 4 months or so,
I may need to roll back to a former version of Cups

Due to the many dependencies, that maynot be an easy task

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

lprm will do that.
--
John Hasler
john.DeleteThis@dhh.gt.org
Dancing Horse Hill
Elmwood, WI USA

Unruh <unruh-s....RemoveThis@physics.ubc.ca> wrote:
>
> There is, but there are conditions.
> If the job has already been sent to the printer (ie is in the printer )
> then you cannot stop it from the computer. YOu have to switch off the
> printer.

A lot of printers keep the current job in their buffer in case
of a power loss. If the printer uses battery backed RAM
for its buffer then power cycling the printer won't work.

I suggest looking on the printer for an option that cancels
the current job. At the printer hardware level to flush the
job out of its internal buffer, not at the host level to flush
it out of the job queue.

Printing gibberish? The says the job is in the wrong format
for the printer. That might be the software that queued the
job producing the wrong format, or it might be the filter in
the queue incorrectly identifying the format. It's common
for a filter to automatically identify PostScipt versus PCL-5
versus text and wrap the job in some commands based on
that format.

If your printer doesn't support one of those formats but the
filter doesn't know, the result is gibberish pages. You need
to scan a couple of sheets of print to see if you recognize
what format it is in. PostScript tends to look like a
programming language. PCL-5 is more binary and tends to
look like line noise on a modem that connected at the wrong
speed.

philo <philo.DeleteThis@privacy.net> writes:

>Unruh wrote:
>> philo <philo.DeleteThis@privacy.net> writes:
>>
>>> Unruh wrote:
>>>> philo <philo.DeleteThis@privacy.net> writes:
>>>>
>>>>
>>>>> I posted this before and got a reply that I thought
>>>>> was going to work.
>>>>> Been using Fedora 10 since the beginning of the year
>>>>> and on a few rare occasions when I've gone to print...
>>>>> I get a runaway process and end up with 20 or more pages of gibberish
>>>>> that *cannot* be stopped.
>>>>> I have killed *all* print jobs.
>>>>> Turned the printer off, disconnected it and even rebooted
>>>>> a number of times...but the print cannot be stopped until
>>>>> it decides to quit on it's own.
>>>>
>>>>> The advice I got was to issue the command lprm
>>>>> but today when my printer ran away and I issued the command...
>>>>> the message I got was: no print jobs to be stopped
>>>>
>>>>> There surely must be some way to kill a runaway print
>>>>> process .
>>>> There is, but there are conditions.
>>>> If the job has already been sent to the printer (ie is in the printer )
>>>> then you cannot stop it from the computer. YOu have to switch off the
>>>> printer. If it is in the computer (lpq should show it, assume it is the
>>>> default printer, otherwise lpq -P nameofprinter) then you can use lprm.
>>>> Note that your printer could be attached to another comptuer and you are
>>>> sending the printerjob to it over the net.
>>>>
>>>>
>>>>
>>>>> any ideas?
>>
>>
>>> printer is local
>>
>> USB, parallel port or network?
>>
>>
>>> and yes, I turned the machine totally off
>>
>> Jobs are queued. Ie saved on disk. Or your printer may have an internal
>> disk/flash-rom to que jobs.
>>
>>
>>> turned printer totally off
>>
>>> unplugged printer
>>
>>> issued the command lprm but no job is there to kill
>>
>> lpstat -o
>> as root.
>>
>>
>>
>>
>>
>>
>>> but upon reboot, it keeps printing gibberish
>>
>>
>>> machine is setup to multi-boot and I can run another Linux distro or
>>> boot to Windows and it's fine
>>
>>
>>> but when I boot back to Fedora, the job continues until it finally quits
>>> on it's own.
>>
>>> Next time it happens I think I'll try stopping Cups
>>
>> Which will make sure you cannot print. the job is queued.
>>
>>
>>> don't know what else to try
>>
>>> FWIW: I am current on my updates
>>
>> What kind of gibberish is it printing? What kind of file are you trying
>> to print?
>>


>The printer is an old Epson Stylus color 740 using the parallel port.

>I only use it for printing out crossword puzzles or text.

>I have a number of printing packages and utilities I do not need,
>so will uninstall them.

>Since this problem has only occurred within the last 4 months or so,
>I may need to roll back to a former version of Cups

>Due to the many dependencies, that maynot be an easy task

It sounds like the printer is not being correctly set into graphics
mode, and is then printing out the scan lines being sent to it as text.
What creates those crossword puzzles or text? Ie are they yours, are
they pdf from the web ...?

Nico Kadel-Garcia wrote:
> On Aug 11, 7:23 am, philo <ph....RemoveThis@privacy.net> wrote:
>> Unruh wrote:
>>> philo <ph....RemoveThis@privacy.net> writes:
>>>> Unruh wrote:
>>>>> philo <ph....RemoveThis@privacy.net> writes:
>>>>>> I posted this before and got a reply that I thought
>>>>>> was going to work.
>>>>>> Been using Fedora 10 since the beginning of the year
>>>>>> and on a few rare occasions when I've gone to print...
>>>>>> I get a runaway process and end up with 20 or more pages of gibberish
>>>>>> that *cannot* be stopped.
>>>>>> I have killed *all* print jobs.
>>>>>> Turned the printer off, disconnected it and even rebooted
>>>>>> a number of times...but the print cannot be stopped until
>>>>>> it decides to quit on it's own.
>>>>>> The advice I got was to issue the command lprm
>>>>>> but today when my printer ran away and I issued the command...
>>>>>> the message I got was: no print jobs to be stopped
>>>>>> There surely must be some way to kill a runaway print
>>>>>> process .
>>>>> There is, but there are conditions.
>>>>> If the job has already been sent to the printer (ie is in the printer )
>>>>> then you cannot stop it from the computer. YOu have to switch off the
>>>>> printer. If it is in the computer (lpq should show it, assume it is the
>>>>> default printer, otherwise lpq -P nameofprinter) then you can use lprm.
>>>>> Note that your printer could be attached to another comptuer and you are
>>>>> sending the printerjob to it over the net.
>>>>>> any ideas?
>>>> printer is local
>>> USB, parallel port or network?
>>>> and yes, I turned the machine totally off
>>> Jobs are queued. Ie saved on disk. Or your printer may have an internal
>>> disk/flash-rom to que jobs.
>>>> turned printer totally off
>>>> unplugged printer
>>>> issued the command lprm but no job is there to kill
>>> lpstat -o
>>> as root.
>>>> but upon reboot, it keeps printing gibberish
>>>> machine is setup to multi-boot and I can run another Linux distro or
>>>> boot to Windows and it's fine
>>>> but when I boot back to Fedora, the job continues until it finally quits
>>>> on it's own.
>>>> Next time it happens I think I'll try stopping Cups
>>> Which will make sure you cannot print. the job is queued.
>>>> don't know what else to try
>>>> FWIW: I am current on my updates
>>> What kind of gibberish is it printing? What kind of file are you trying
>>> to print?
>> The printer is an old Epson Stylus color 740 using the parallel port.
>>
>> I only use it for printing out crossword puzzles or text.
>>
>> I have a number of printing packages and utilities I do not need,
>> so will uninstall them.
>>
>> Since this problem has only occurred within the last 4 months or so,
>> I may need to roll back to a former version of Cups
>>
>> Due to the many dependencies, that maynot be an easy task
>
> Or update to Fedora 11. CUPS and the ghostscript on which it relies
> for its printer drivers are fairly rapidly evolvong packages, and have
> to be. as printer information gets updated.


I have Fedora 11 on another drive
and am slowly migrating over...
however I am currently having problems with Nvidia drivers...
and that's a whole other story.

Anyway, I've decided not to revert to a previous version of Cups
and will simply update it the next time an update is available

Unruh wrote:
> philo <philo RemoveThis @privacy.net> writes:
>
>> Unruh wrote:
>>> philo <philo RemoveThis @privacy.net> writes:
>>>
>>>> Unruh wrote:
>>>>> philo <philo RemoveThis @privacy.net> writes:
>>>>>
>>>>>
>>>>>> I posted this before and got a reply that I thought
>>>>>> was going to work.
>>>>>> Been using Fedora 10 since the beginning of the year
>>>>>> and on a few rare occasions when I've gone to print...
>>>>>> I get a runaway process and end up with 20 or more pages of gibberish
>>>>>> that *cannot* be stopped.
>>>>>> I have killed *all* print jobs.
>>>>>> Turned the printer off, disconnected it and even rebooted
>>>>>> a number of times...but the print cannot be stopped until
>>>>>> it decides to quit on it's own.
>>>>>> The advice I got was to issue the command lprm
>>>>>> but today when my printer ran away and I issued the command...
>>>>>> the message I got was: no print jobs to be stopped
>>>>>> There surely must be some way to kill a runaway print
>>>>>> process .
>>>>> There is, but there are conditions.
>>>>> If the job has already been sent to the printer (ie is in the printer )
>>>>> then you cannot stop it from the computer. YOu have to switch off the
>>>>> printer. If it is in the computer (lpq should show it, assume it is the
>>>>> default printer, otherwise lpq -P nameofprinter) then you can use lprm.
>>>>> Note that your printer could be attached to another comptuer and you are
>>>>> sending the printerjob to it over the net.
>>>>>
>>>>>
>>>>>
>>>>>> any ideas?
>>>
>>>> printer is local
>>> USB, parallel port or network?
>>>
>>>
>>>> and yes, I turned the machine totally off
>>> Jobs are queued. Ie saved on disk. Or your printer may have an internal
>>> disk/flash-rom to que jobs.
>>>
>>>
>>>> turned printer totally off
>>>> unplugged printer
>>>> issued the command lprm but no job is there to kill
>>> lpstat -o
>>> as root.
>>>
>>>
>>>
>>>
>>>
>>>
>>>> but upon reboot, it keeps printing gibberish
>>>
>>>> machine is setup to multi-boot and I can run another Linux distro or
>>>> boot to Windows and it's fine
>>>
>>>> but when I boot back to Fedora, the job continues until it finally quits
>>>> on it's own.
>>>> Next time it happens I think I'll try stopping Cups
>>> Which will make sure you cannot print. the job is queued.
>>>
>>>
>>>> don't know what else to try
>>>> FWIW: I am current on my updates
>>> What kind of gibberish is it printing? What kind of file are you trying
>>> to print?
>>>
>
>
>> The printer is an old Epson Stylus color 740 using the parallel port.
>
>> I only use it for printing out crossword puzzles or text.
>
>> I have a number of printing packages and utilities I do not need,
>> so will uninstall them.
>
>> Since this problem has only occurred within the last 4 months or so,
>> I may need to roll back to a former version of Cups
>
>> Due to the many dependencies, that maynot be an easy task
>
> It sounds like the printer is not being correctly set into graphics
> mode, and is then printing out the scan lines being sent to it as text.
> What creates those crossword puzzles or text? Ie are they yours, are
> they pdf from the web ...?
>


Considering it works correctly about 99% of the time
and then corrects itself with me making *no* changes to the settings...
I say the settings are probably right...

I am using the NY times crossword puzzle and their Linux version of the
software does not work with my system...
so I am using the Windows version under Wine.

Very possibly a Wine problem...
though I may try the updated software they have available

Doug Freyburger wrote:
> Unruh <unruh-s....TakeThisOut@physics.ubc.ca> wrote:
>> There is, but there are conditions.
>> If the job has already been sent to the printer (ie is in the printer )
>> then you cannot stop it from the computer. YOu have to switch off the
>> printer.
>
> A lot of printers keep the current job in their buffer in case
> of a power loss. If the printer uses battery backed RAM
> for its buffer then power cycling the printer won't work.
>
> I suggest looking on the printer for an option that cancels
> the current job. At the printer hardware level to flush the
> job out of its internal buffer, not at the host level to flush
> it out of the job queue.
>
> Printing gibberish? The says the job is in the wrong format
> for the printer. That might be the software that queued the
> job producing the wrong format, or it might be the filter in
> the queue incorrectly identifying the format. It's common
> for a filter to automatically identify PostScipt versus PCL-5
> versus text and wrap the job in some commands based on
> that format.
>
> If your printer doesn't support one of those formats but the
> filter doesn't know, the result is gibberish pages. You need
> to scan a couple of sheets of print to see if you recognize
> what format it is in. PostScript tends to look like a
> programming language. PCL-5 is more binary and tends to
> look like line noise on a modem that connected at the wrong
> speed.


But it corrects itself once the fault finally clears.

and that's with me making no changes to the settings

There is no printer buffer as I can boot over to Windows or another
Linux install and the printer works.
but when booted back to Fedoara 10

the job keeps comming...
though my restarting Cups is at least a temporary option to stop the
printing