Description of problem: There are number if warnings in /var/log/cups/error_log: E [09/Dec/2010:04:02:09 +0300] Unsupported character set "localhost" from host iso-8859-1! Clients must use us-ascii or utf-8. Future versions will reject this request. E [09/Dec/2010:04:02:10 +0300] Unsupported character set "localhost" from host iso-8859-1! Clients must use us-ascii or utf-8. Future versions will reject this request. E [09/Dec/2010:04:02:14 +0300] Unsupported character set "localhost" from host iso-8859-1! Clients must use us-ascii or utf-8. Future versions will reject this request. Version-Release number of selected component (if applicable): kernel 2.6.18-194.26.1.el5 How reproducible: Always Steps to Reproduce: 1. Add new printer with command: lpadmin -p tally30 -i /etc/lp/interfaces/model.orig/tally30 -E -v socket://29.3.2.58 -o printer-error-policy=retry-job 2. Print with command: cat file | lp -d printername 3. Get warning Actual results: Warnings in /var/log/cups/error_log Expected results: No warnings Additional info: Same time in /var/log/cups/access_log: localhost - - [09/Dec/2010:04:02:09 +0300] "POST / HTTP/1.1" 200 134 CUPS-Get-Printers successful-ok localhost - - [09/Dec/2010:04:02:10 +0300] "POST / HTTP/1.1" 200 134 CUPS-Get-Classes successful-ok localhost - - [09/Dec/2010:04:02:14 +0300] "POST / HTTP/1.1" 200 134 CUPS-Get-Printers successful-ok System encoding settings /etc/i18n: #LANG=en_US LANG=ru_RU.cp866 SYSFONT=Cyr_a8x16 ACMTABLE=cp866 KEYTABLE=ru2
Is the problem the switched-around arguments in the string ("localhost" and "iso-8859-1"), or the fact that the warning message occurs at all? The first is being tracked in bug #608016; the second is intentional behaviour but perhaps ought to be rate-limited to once per client per boot or just once per boot.
Thanx Tim, the first one should be ok for customer, case can be closed.
*** This bug has been marked as a duplicate of bug 608016 ***