HARDWARE: Intel Core 2 Duo
OS: SuSE 10.2 32-bit

Please attach y2logs. If you are in doubt please follow:

http://en.opensuse.org/Bugs/YaST


Thanks!

Created attachment 115893 [details]
/var/log/YaST2/y2log

NOTE:  When I send a job to the printer (Xerox Phaser 6300 using Tektronix Phaser 850 drivers, which has worked for the past 3 or so SuSE distros) the printer briefly wakes up indicating that SOMETHING hit the printer, but the message panel never says anything about a job and nothing prints.  I've tried this on two separate Phaser 6300 printers with the same results.  Numerous other SuSE 10.1 systems in the area all continue to print normally using these settings.

could you attach also content of /etc/cups/* as a tarball?

decreasing of serverity to major (no data crash, or coruption)

Please provide exact facts about your printer setup.
Otherwise it is totally impossible for us to have a chance
to reproduce your problem.

I changed the subject from "SuSE 10.2 - Can't Print - CUPS is Broken"
to something meaningful: "Xerox Phaser 6300 doesn't print".

How exactly is your printer connected?
I.e. which exact DeviceURI do you use?
The DeviceURI is in /etc/cups/printers.conf

Which exact PPD file (i.e. which exact printer driver) do you use?
The PPD file is /etc/cups/ppd/<queuename>.ppd

What is in the CUPS error_log - see
http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html
---------------------------------------------------------------------------
If problems are encountered:

1. Set the "LogLevel debug" in /etc/cups/cupsd.conf.
2. Stop cupsd.
3. Move /var/log/cups/error_log* to another location (or delete it)
   in order to avoid having to search through gigantic log files.
4. Start cupsd.
5. Retry the action leading to the problem.
6. Now /var/log/cups/error_log* contains many messages that are useful
   for troubleshooting. 
---------------------------------------------------------------------------

Attach the PPD file and the error_log for exactly one failed printout
as mime type "text/plain" to this bug.

Additional question: did you install 10.2 from scratch or did you do an update?
Please answer above questions (comment#7) too / attach requested files.

Created attachment 116224 [details]
/etc/cups tar ball

Printer: Xerox Phaser 6300
Static TCP - 128.37.4.200
Netmask: 255.255.255.0
Gateway: 128.37.4.254

Spool is named: c32 (short for color printer in room 32)
Port number: 9100

Printer works fine from numerous SuSE 10.1 systems.

Printer is also connected directly to my 10.2 system via a USB 2.0 port.  SuSE 10.2 detected the USB connection and added the printer to the Cups configuration.

SuSE does not contain a specific Xerox Phaser 6300 driver.  I'm using a Tektronix Phaser 850 driver that SuSE DOES include with the distribution.

The /etc/cups/ppd/[queuename].ppd files are included in the tarball above.


----------------

OK, here's what I did:
  deleted all configured printers
  stopped cupsd
  removed the /var/log/cups log files
  restarted cupsd
  added 1 direct connection TCP network printer
  tried printing 1 page from Mozilla Firefox (Foxnews.com)

The printer spooled up for a second and then went idle again.

As far as I can tell the logs say the job was created and sent successfully to the printer.

We don't have a Tektronix Phaser printer therefore we cannot reproduce
it 100% but I did set up a queue "p850" which prints into a file
with your phaser6300n.ppd

I printed with "echo Hello | lp -d p850" and I got no errors in /var/log/cups/error_log and the file contains good looking PostScript
which I can display without errors with "gs" and which prints well
on my HP LaserJet 1220.

Therefore we need your /var/log/cups/error_log for exactly one failed
attempt.

By the way1:
As your printer is a PostScript printer, why don't you use a PPD
from the manufacturer of this printer which should match exactly
to your model?

By the way2:
Did you ever try out the "PreFilter/GhostScript pre-filtering"
option in your phaser6300n.ppd to enforce PostScript Level1 or Level2?
For background information see
http://en.opensuse.org/SDB:Using_Your_Own_Filters_to_Print_with_CUPS
"PostScript Preprocessing with Ghostscript on PostScript Printers"

Created attachment 116237 [details]
/var/log/cups/*_log

These are the cups log files that were created after the aforementioned steps were taken.

When the job was created and sent successfully to the printer,
it is the printer itself which cannot process the PostScript.

To verify, enable PostScript error messages in the printer
(see the printer's manual).

I assume enforce Level1 via the "PreFilter/GhostScript pre-filtering"
may help.

For testing print simple ASCII text via comand line like

echo Hello | lp -d phaser6300n -o PreFilter=Level2
echo Hello | lp -d phaser6300n -o PreFilter=Level1
echo Hello | lp -d c32 -o PreFilter=Level2
echo Hello | lp -d c32 -o PreFilter=Level1

Please provide a CUPS error_log and report if the "PreFilter" works.

Thanks for the CUPS error_log!

OK, now I feel like an idiot.  :-)

I didn't know how ppd files worked, how they were installed, or that manufacturers (Xerox) even provided them.  I downloaded the proper ppd file from Xerox and added the driver to cups' list of installed drivers and now the printer works fine.  Apparently the ppd file for the Tektronix Phaser 850 that had been working for a few years changed just enough to make it not work with the Phaser 6300 anymore.

Thanks for all your help guys.

Shawn