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.
Bug 1149245 - FINAL_CONTENT_TYPE incorrect for all backends
Summary: FINAL_CONTENT_TYPE incorrect for all backends
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cups
Version: 7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Tim Waugh
QA Contact: qe-baseos-daemons
Depends On: 1149244
TreeView+ depends on / blocked
Reported: 2014-10-03 15:15 UTC by Pierre Ossman
Modified: 2015-03-05 09:09 UTC (History)
6 users (show)

Fixed In Version: cups-1.6.3-17.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1149244
Last Closed: 2015-03-05 09:09:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0386 0 normal SHIPPED_LIVE cups bug fix and enhancement update 2015-03-05 14:06:04 UTC

Description Pierre Ossman 2014-10-03 15:15:39 UTC
+++ This bug was initially created as a clone of Bug #1149244 +++

Bug 1010580 killed FINAL_CONTENT_TYPE and forced every CUPS backend into raw mode. The patch added by that bug is horribly wrong and needs to be dropped ASAP.

The original bug is something else with CUPS re-running a filter even though the data is already in the desired format. Possibly a bug in the relevant PPD.

Comment 2 Pierre Ossman 2014-10-16 08:27:47 UTC
The Fedora version of this bug is now fixed, so will RHEL be updated right away as well?

Comment 3 Tim Waugh 2014-10-16 08:44:28 UTC
If Fedora changes went immediately into Red Hat Enterprise Linux, it would be Fedora. :-)

This change is pretty well understood, so it shouldn't take too long.

Comment 5 Pierre Ossman 2014-10-27 11:01:27 UTC
Can I download and test this somehow? I can't see any testing or QA channel available.

Comment 6 Tim Waugh 2014-10-27 15:06:27 UTC
I've put some test packages here:

Comment 7 Pierre Ossman 2014-10-28 15:38:27 UTC
Looks good:

> D [28/Oct/2014:16:20:46 +0100] [Job 20] envp[22]="CONTENT_TYPE=application/pdf"
> D [28/Oct/2014:16:20:46 +0100] [Job 20] envp[29]="FINAL_CONTENT_TYPE=application/pdf"

> D [28/Oct/2014:16:26:55 +0100] [Job 21] envp[22]="CONTENT_TYPE=text/plain"
> D [28/Oct/2014:16:26:55 +0100] [Job 21] envp[29]="FINAL_CONTENT_TYPE=application/pdf"

Comment 8 Tim Waugh 2014-10-28 17:59:00 UTC
Great, thanks for testing it out.

Comment 11 errata-xmlrpc 2015-03-05 09:09:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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