Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Starting with CUPS 1.2, only the UTF-8 character set is supported.
RHEL 4 clients will use the character set specified in LANG as the
charset attribute in CUPS IPP requests. This can lead to
incompatibilities between RHEL 4 CUPS clients and RHEL 6 CUPS
servers.
It appears that RHEL 5 and RHEL 6 CUPS clients ignore LANG and
always use UTF-8.
Version-Release number of selected component (if applicable):
client: cups-1.1.22-0.rc1.9.32.el4_8.10
server: cups-1.4.2-35.el6
How reproducible:
100%
Steps to Reproduce:
1. Configure the RHEL 6 CUPS server to accept connections from everywhere.
2. Run "lpstat -h <server-name> -s" on the RHEL 4 client
Actual results:
lpstat: get-classes failed: client-error-bad-request
lpstat: get-printers failed: client-error-bad-request
Expected results:
No failure.
Additional info:
Would we consider patching RHEL 4 CUPS clients to always use UTF-8?
Created attachment 453213[details]
cups-undo-str2537.patch
More likely we'd patch RHEL-6 to allow non-UTF-8 clients, like we did with RHEL-5:
"- Revert STR #2537 so that non-UTF-8 clients continue to be accepted."
Attached is the RHEL-5 patch forward-ported to RHEL-6.
An advisory 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 therefore 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-2011-0715.html
Description of problem: Starting with CUPS 1.2, only the UTF-8 character set is supported. RHEL 4 clients will use the character set specified in LANG as the charset attribute in CUPS IPP requests. This can lead to incompatibilities between RHEL 4 CUPS clients and RHEL 6 CUPS servers. It appears that RHEL 5 and RHEL 6 CUPS clients ignore LANG and always use UTF-8. Version-Release number of selected component (if applicable): client: cups-1.1.22-0.rc1.9.32.el4_8.10 server: cups-1.4.2-35.el6 How reproducible: 100% Steps to Reproduce: 1. Configure the RHEL 6 CUPS server to accept connections from everywhere. 2. Run "lpstat -h <server-name> -s" on the RHEL 4 client Actual results: lpstat: get-classes failed: client-error-bad-request lpstat: get-printers failed: client-error-bad-request Expected results: No failure. Additional info: Would we consider patching RHEL 4 CUPS clients to always use UTF-8?