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.

Bug 1585291

Summary: [RFE] Add lcms2 support to ImageMagick
Product: Red Hat Enterprise Linux 7 Reporter: Andrew Mike <amike>
Component: ImageMagickAssignee: Jan Horak <jhorak>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: alanm, amike, bgollahe, jeischma, jwright, mboisver, mkolbas, tpelka
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:17:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1656436    

Description Andrew Mike 2018-06-01 18:24:21 UTC
Description of problem: In RHEL 6, ImageMagick supported color profile operations by default through lcms. In RHEL 7, lcms was dropped for security holes, and thus lcms support in ImageMagick was dropped in 6.7.8.9-5.2.

lcms2 is shipped in RHEL 7, and used in builds of GIMP and other programs (see Bug 1009360, Bug 973965, Bug 1006967, etc), but it doesn't seem that ImageMagick was included in this. Judging from the compilation instructions, lcms2 support is already included in ImageMagick and requires a configuration flag (--with-lcms2=yes) to turn on (https://www.imagemagick.org/script/advanced-unix-installation.php).

How would the customer like to achieve this? (List the functional requirements here)  
- A version of the ImageMagick package with lcms2 support -- or other support for color profile operations -- compiled in. The package should ideally maintain feature compatibility with earlier versions.
  
Is there already an existing RFE upstream or in Red Hat Bugzilla?  
- No Red Hat Bugzilla RFE were present at time of filing. Upstream already has lcms2 support.
  
Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
- As soon as possible.
  
Is the sales team involved in this request and do they have any additional input?  
- Sales is not involved.

List any affected packages or components.  
- ImageMagick

Would the customer be able to assist in testing this functionality if implemented?
- Yes

Comment 18 errata-xmlrpc 2019-08-06 13:17:39 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.

https://access.redhat.com/errata/RHBA-2019:2312