-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
NotIdentifiedByImageMagickError with ImageMagick 6.9.4-7 #2223
Comments
There are two more places that use the [0]... Removing these makes identify work properly, though I didn't take the time to investigate what else it might break at this time. Apparently one of the things it does it make it ignore storage: :s3. Goes to show what you get for trying to do a rush job of trying to throw a band-aid on something, rather than trying to understand the actual cause. |
Just got bit by this as well after upgrading to the latest version of ImageMagick. |
👍 confirming bug, colleague of mine done another colleague has |
Same error here. I am using
|
If you've installed Imagemagick via Homebrew and temporarily need to revert back to the previous version you can do this doing the following.
When this issue resolves you can simply switch back to the latest version and run |
It seems a bug with imagemagick itself. I has been fixed on master: ImageMagick/ImageMagick#214 |
@KevinSjoberg that worked. Thanks! |
@KevinSjoberg When I get to the line:
I get the following error: Any ideas? |
@blakeage try |
@lifeiscontent I tried that, but no luck. I wonder if this is because I tried installing ImageMagick via the --HEAD option |
@blakeage what is the output of |
@KevinSjoberg Blakes-MacBook-Pro:homebrew-core blakemiller$ pwd |
@blakeage Looks okay to me. You can probably untap |
@KevinSjoberg I untapped boneyard.
|
@blakeage does |
@KevinSjoberg Yea,
I'm guessing reinstalling Homebrew may be the way to go? |
@blakeage this is beyond me. I'd try |
@KevinSjoberg Thanks for the help anyway Kevin. I'll report back if I figure it out. |
@blakeage I had the same problem, and it was because homebrew only pulls some commits from the taps (specifically it does a shallow pull). What I´ve done to get arround this is to clone the whole homebrew-tap and replaced my homebrew-tap with the full repository of the tap.
|
ImageMagick 6.9.4-8 is now available via homebrew, fixed it for me. |
Can confirm that ImageMagick 6.9.4-8 fixes it. Closing this issue. |
Installing libmagickwand-dev seemed to sort it out.
sudo apt install ffmpeg ImageMagick delegates video processing. I lost more than 5 hours to understand why such a bug NotIdentifiedByImageMagickError install make https://www.imagemagick.org/discourse-server/viewtopic.php?t=24284 |
If you hit this error since October 2018 on Ubuntu, here is the relevant Imagemagick changelog: https://launchpad.net/ubuntu/+source/imagemagick/8:6.7.7.10-6ubuntu3.13
To make PDF uploads work again, you have to update Change <policy domain="coder" rights="none" pattern="PDF" /> to <policy domain="coder" rights="read|write" pattern="PDF" /> Relevant stack overflow: https://stackoverflow.com/a/52661288 |
I hit this problem in Debian Stretch starting around early Dec 2018. I fixed it temporarily by reverting to an older version of ghostscript. My explanation, not yet confirmed, is that the recent update to Ghostscript 9.26 in Debian Stretch Security caused the issue to pop up. Further investigation to do... |
Being treated here as a bug of ghostscript: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915832 and https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1806517 |
I updated to ImageMagick 6.9.4-7 on OS X. Now I'm getting NotIdentifiedByImageMagickError. The identify command doesn't seem to work with the [0] suffix to the path. It works fine without the [0] suffix. I was able to reproduce it with GIF, JPG and PNG files.
ImageMagick 6.7.7 seems to work both with and without [0] suffix. I didn't test with older versions though.
The [0] bit is added at:
paperclip/lib/paperclip/geometry_detector_factory.rb
Line 22 in e60f000
I wonder wether this is a bug on ImageMagick side or they dropped backwards compatibility on this one.
The text was updated successfully, but these errors were encountered: