Description of problem: Can't define serial printer in printconf. Attempted to define a new serial printer (same in printconf-gui and printconf- tui): Local Printer Custom Device: /dev/ttyR7 Epson 9-pin 80 column (omni driver is only choice) Note that /dev/ttyR7 is a serial port on a Comtrol Rocketport card that does work for a serial terminal, and, once /etc/cups/printers.conf is edited, for printing. I expect I would see the same behavior for /dev/ttyS0 or /dev/ttyS1, since there is no option to select either of these ports in printconf, either. When you look in /etc/cups/printers.conf at the definition lines for the printer just created, you see: DeviceURI file:/dev/ttyR7 and, with this line, if you try to print to the attached serial printer, you get some printing sometimes, ususally with lots of garbage characters. If you edit the line so it looks like: DeviceURI serial:/dev/ttyR7 you are able to print to the printer without problems. Version-Release number of selected component (if applicable): redhat-config-printer-0.6.35-1 [root@award3 phl]# cat /etc/redhat-release Red Hat Linux release 8.0.93 (Phoebe) [root@award3 phl]# uname -m i686 How reproducible: always Steps to Reproduce: 1.Define a serial printer using a custom device and a working serial port. 2.Attempt to print (get garbage or job queued but no printing). 3.Edit /etc/cups/printers.conf for the printer you created; change the word 'file' to the word 'serial' and the printer will work. Actual results: Got garbage attempting to print after defining the printer. Expected results: Should have gotten a normal printout. Additional info:
I think /dev/ttyS* should be okay; the serial: scheme was chosen if the device name began '/dev/ttyS'. I changed the test to "begins '/dev/tty'". Fixed in CVS.
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2003-125.html