Bug 113424
Summary: | cupsomatic filter causes samba PostScript printing to fail | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Allen Akin <akin> |
Component: | foomatic | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | ||
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: | 2007-10-19 19:31:24 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: |
Description
Allen Akin
2004-01-13 19:29:23 UTC
The move from cupsomatic to foomatic-rip will happen in a future release, but is too big a change for doing in an update. Just to clarify the situation: you have a Windows machine sending PJL-wrapped PostScript to the samba share on the Linux machine, but the Linux machine is trying to munge the PostScript? I think you need to set the queue up as a raw print queue for that situation. In other words, you should only need to tell one of the computers what type of printer it is. About the clarification: There are two problems. The first one is that cupsomatic can't handle a filename passed to it on the command line. As far as I can tell that's exactly what happens with it's used with Samba, and the result is that cupsomatic simply fails (producing the error message "inputfile handling is broken!!!"). Without a workaround for that, you never run into the second problem. As for the second problem, yes, the Windows machine is sending PJL-wrapped PostScript to the samba share on the Linux machine. Here's what happens after that. CUPS decides that the file is of MIME type application/vnd.cups-postscript because it passes the tests around line 134 of /etc/cups/mime.types. Note that those tests specifically allow for PJL wrapping. application/vnd.cups-postscript files get filtered by cupsomatic because that's what the printer's PPD defines in its "cupsFilter" attribute. However, cupsomatic chokes because the very first characters in the file aren't the PostScript magic string "%!". (They're actually the PJL magic string "<0x1B>%-12345X".) cupsomatic seems to have code for parsing the PJL options, but it never gets invoked because the test for detecting PostScript is wrong. About the raw print queue: Yeah, I tried that before writing the wrapper for cupsomatic. The problem is that the raw queue passes *everything* sent by the Windows machine directly to the printer. The printer doesn't understand the PJL options that the Windows drivers prepend to the PostScript file, so it just generates PostScript errors and prints nothing. I certainly could be misunderstanding something about how the system is supposed to work, but it looks to me like things are basically OK with the exception of the two problems in cupsomatic itself. This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |