Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 136483 - CUPS can't print plain ASCII text
CUPS can't print plain ASCII text
Status: CLOSED DUPLICATE of bug 136102
Product: Fedora
Classification: Fedora
Component: cups (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2004-10-20 09:26 EDT by Markku Kolkka
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-20 09:45:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
CUPS error log from printing the ASCII test page from printconf-gui (25.53 KB, text/plain)
2004-10-20 09:29 EDT, Markku Kolkka
no flags Details

  None (edit)
Description Markku Kolkka 2004-10-20 09:26:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)

Description of problem:
When I try to print a plain text file, pipe text output from a command
to lpr or try the ASCII test page from printconf, nothing gets sent to
the printer. Setting CUPS log level to debug shows Ghostscript
quitting with "unrecoverable error".
Printing PostScript works OK. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. echo 'Hello World!' | lpr

Actual Results:  Nothing happens.

Expected Results:  Printer outputs a page with text "Hello World!"

Additional info:

Printer is Epson Stylus Color 880 connected through USB,
gimp-print-ijs driver.
Comment 1 Markku Kolkka 2004-10-20 09:29:55 EDT
Created attachment 105506 [details]
CUPS error log from printing the ASCII test page from printconf-gui
Comment 2 Tim Waugh 2004-10-20 09:45:25 EDT

*** This bug has been marked as a duplicate of 136102 ***

Note You need to log in before you can comment on or make changes to this bug.