Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#17110 - [cups] EPSON TM-U950 doesn't print
Attached to Project:
Arch Linux
Opened by Maxwell Draven (Ravenman) - Thursday, 12 November 2009, 16:06 GMT
Last edited by Allan McRae (Allan) - Monday, 25 January 2010, 07:35 GMT
Opened by Maxwell Draven (Ravenman) - Thursday, 12 November 2009, 16:06 GMT
Last edited by Allan McRae (Allan) - Monday, 25 January 2010, 07:35 GMT
|
DetailsDescription:
I'm migrating some POS equipped with EPSON printers and it isn't working properly on Arch (and it works perfectly on Xubuntu, the current operating system of the POS). The printer is configured with the Generic ESC/P Dot Matrix Printer Foomatic/epson driver, the system recognizes my printer as EPSON TM-P2.01 parallel port, but when I send a print, the system it isn't printing. In reviewing the status of work, appearing as stopped ... but if I send one print directly to the port, it prints correctly. Additional info: * package version(s) cups 1.4.2-1 foomatic-db 4.0.3_20090904-2 * config and/or log files etc. Steps to reproduce: Try to print in one EPSON TM-U950 printer with CUPS |
This task depends upon
Closed by Allan McRae (Allan)
Monday, 25 January 2010, 07:35 GMT
Reason for closing: No response
Additional comments about closing: No response in +2 months. Please reopen if still valid with a link to upstream report.
Monday, 25 January 2010, 07:35 GMT
Reason for closing: No response
Additional comments about closing: No response in +2 months. Please reopen if still valid with a link to upstream report.
Comment by Andreas Radke (AndyRTR) -
Friday, 13 November 2009, 15:49 GMT
Looks like something inside ghostscript processing goes wrong. Can you please ask upstream?
error_log