ImageMagick problems after Upgrade to OSX 10.9 Mavericks
I recently upgraded to OSX 10.9 Mavericks and so far almost everything worked like it should. I am using MAMP Pro for developing web applications and TYPO3 websites locally – and therefor I rely on ImageMagick for serverside image processing.
There are several ways of installing ImageMagick on OSX, some of them use Macports, I prefer a clean and lean installation through the command line (which I did when I set up my mac with 10.7).
However, ImageMagick did not work properly at all after the Mavericks update. TYPO3 was complaining that “there was no suitable ImageMagick installation at all” and image processing simply did not work. I was already looking up how to install ImageMagick again all over, when I realized the binaries where still there in /usr/local/bin.
I called one of the command line tools of ImageMagick and – ‘voila’ – a real OSX popup appeared, telling me I needed QuartzX in order to run ImageMagick.
Which I did, the (Mavericks compatible) download can be found here; after the installation of QuartzX everything ran smoothly again.
It’s not cool that Apple breaks ImageMagick during the 10.9 update, but – there is a simple way out of it. Wish the QuartzX popup / tip would have come up earlier..
iMac Super Drive seemed to be stuck/broken. Seemed!
I recently had an unpleasant experience with the slot-in Super Drive in my 2011 iMac: the empty drive did not take in dvds nor cds – when I tried inserting disks they went halfway through and then something seemd to block the disks.
I rebooted, pressed the eject button multiple times, resetted pram and nvram, nothing happened. Drive seemed to be broken, Disk Utility and System Information showed an empty drive.
Since this is my main work machine, I was not too happy about the thought to bring it to a certified reseller, waiting for at least a week to be repaired etc.. (there is still not a single apple store in Austria, hello Apple? Even Bologna has an Apple Store!)
Some googling brought up the idea of tapping the disks inside the drive, applying a bit of force (which seemed not to be a brilliant idea without breaking anything nor did it work). Not to talk about the “solution” with using 2 plastic credit cards..
Finally I fould a useful post searching the Apple support communities and Dan8954’s suggestion did save my day: The command
drutil eject
typed into the terminal unlocked the drive (somehow it seemd to have thought there is a disk in the drive) – since then it is working flawlessly again.
