Resolved ImageMagick 6.9.13-25 breaks PDF reading

[Sebahat.hadzhi]

That issue was fixed in Plesk Obsidian 18.0.70. Please let us know if you are still experiencing any issues after the update.

 

[kriteodoro]

Username:

TITLE

ImageMagick 6.9.13-25 breaks PDF reading

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

AlmaLinux 9.5 (Teal Serval), Plesk Obsidian 18.0.68 Update #2

PROBLEM DESCRIPTION

Latest release of ImageMagick 6.9.13-25 updated via YUM breaks PDF reading and returns an error. This is the stock version that comes from the EPEL library.

STEPS TO REPRODUCE

Try running a PHP script to read anything about a PDF file:

$pdfMain = new \Imagick( dirname(__FILE__) . '/test.pdf' );
    $numberPages = $pdfMain->getNumberImages();

    printf( '<pre>%1$s</pre>', print_r( $numberPages, 1 ) );
    die( 'end' );

ACTUAL RESULT

Fatal error: Uncaught ImagickException: Failed to read the file

EXPECTED RESULT

Should read a PDF file

ANY ADDITIONAL INFORMATION

• Bug started with latest release of ImageMagick 6.9.13-25
• Checked that there were no custom exceptions set in the policy xml file
• Attempted to add a manual PDF coder read|write policy and following a full server restart, to no avail
• No other ImageMagick versions installed
• Attempted removing/reinstalling both GhostScript as well as ImageMagick (all default settings) via YUM as these worked until the latest release
  Because it seems that the problem is in the 6.9.13-25 release, and here it is either to wait for a fix, or to install the previous build. And to be honest, lately I have been trying to run PDF through other tools, because there is no better solution yet. Even for a quick PDF check, it is sometimes convenient to use things like pdf summarizer because you can at least quickly look at what is inside while the server reading is failing. I think that Plesk will confirm the bug and EPEL will quickly release a patch. Have you tried installing a newer or older version manually?

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

I would also try installing a previous working version from the repository. Maybe even via a manual build or an alternative RPM, just to check if it's definitely a bug.