Bug 121547
Summary: | Lexmark Optera S 1255 printer reports an PostScript error | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kyrre Ness Sjøbæk <kyrsjo> | ||||||
Component: | cups | Assignee: | Tim Waugh <twaugh> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | |||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 1 | ||||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2005-09-05 11:57:13 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Kyrre Ness Sjøbæk
2004-04-22 18:14:43 UTC
Sent an example file to Tim Waugh (twaugh) - wasn't able to upload it as a attachment - 2 MB of size... Got a response from Lexmark this morning. They said: Use our PS/PCL driver kit for UNIX (which we linked to). If you do not want to use this driver, I will have to see the setup page for the printer, so we can see if it is possible to upgrade the codes in the printer. (Your mail to me didn't have any attachment.) The problem might be something like trying to set duplex printing when it is not duplex-capable. So I'll need to know two things: 1. Please attach to this bug report the output of 'printconf-tui --Xexport', so that I can see the print queue settings -- make sure to remove any passwords it might contain. 2. Is the 2Mb file you tried to attach a PostScript file, and if so which application did you use to generate it? I shall do that (when I get back to my shool where the problem-printers exists). The problem is definatly not the cable - as we are seeing the same problem at network-attached printers too (another Optera S 1255 and a Optera S 1850), even when trying to print over SMB (showing up as "raw data" or something at windows'es print-manager - but still nothing shows up at the printer(the network attached ones has not been set to print error messages)). After installing the RPM with their print-drivers (which integrates with CUPS), "everything" worked great. The printer connected to lp0 even showed up in redhat-config-printers. The 2 MB file i tried to attach is the .swx file i was trying to print (the same which I sent you on mail). Created attachment 99900 [details]
The output from one of the pc's without working printing
Created attachment 99901 [details]
The output from the machine which has the properitary drivers
How about if you set the printer model to Generic PostScript? What do you mean? Set it as a "raw" printer? How do I do that? Anyway I got it working now - added the printers via Lexmarks properitary drivers, shared them (Lexmark did'nt know how - their tool, that is, and redhat-config-printer only showed the one connected directly into the paralell port... (found out how to edit cupsd.conf and use lpadmin to give everybody (on the LAN) access - why isn't this included in the web interface, which btw is great!)), and disabling the wicked firewall on the client-computers. Then all was a silk ride, they automagically appeared on the clients. When we upgrade to FC2 soon, at least we know how to fix things! In the 'Printer driver' tab, choose 'Generic' as the manufacturer and 'Raw Print Queue' as the model. I am personally no longer able to debug this, as the printers have been decomissioned (replaced by better HP ones), and i have moved over to university - no longer having access. Anyway, for future reference: The lexmark supplied drivers acctually worked, but i had to install some xorg-compat (or somesuch) to get their config tools to work on fc3. Then the config was a chore, since we wanted to share them over CUPS IPP printer sharing - as their config tools did not make this possible, system-config-printer did not pick up anything setup by their tool, and the cups ipp config files... Well. They aren't that bad, acctually, when you get used to them. You may or may not close this bug. |