![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
and even large companies like adobe and amazon seem blissfully unaware of such a thing. what is this, the dark ages?
so today i installed the kindle for mac program since i broke down to buy a book i really needed right away, and which was most easily available on the kindle.
the app died on me right away with the incredibly helpful error message "there was a problem". no shit?
fortunately we have the console, which told me:
12/07/15 5:23:42 PM [0x0-0xa90a9].com.amazon.Kindle[1427] dyld: Library not loaded: @executable_path/../Frameworks/libWEbCoreKRF.dylib
12/07/15 5:23:42 PM [0x0-0xa90a9].com.amazon.Kindle[1427] Referenced from: /Applications/Kindle.app/Contents/MacOS/../Frameworks/libWebCoreViewer.dylib
12/07/15 5:23:42 PM [0x0-0xa90a9].com.amazon.Kindle[1427] Reason: image not found
thanks to adobe i am primed to look for case-sensitivity issues, so the difference between libWEbCore and libWebCore jumped right out at me. looking inside the app bundle showed that indeed, libWebCoreKRF.dylib is present and accounted for.
fortunately this is easily fixed by creating a dynamic link from the correct lib to the misspelled one:
using terminal, admin privileges, go to the directory in question (/Applications/Kindle.app/Contents/Frameworks if you've installed in the usual place), and issue this command:
ln -s libWebCoreKRF.dylib libWEbCoreKRF.dylib
and the app will work for now -- until the next update. any bets on whether that'll fix the problem? yeah, didn't think so.
in better news, market day left us with ripe, local strawberries, and they are SO GOOD. and moroccan spice bread. and baked bread pudding. and fresh fudge.
so today i installed the kindle for mac program since i broke down to buy a book i really needed right away, and which was most easily available on the kindle.
the app died on me right away with the incredibly helpful error message "there was a problem". no shit?
fortunately we have the console, which told me:
12/07/15 5:23:42 PM [0x0-0xa90a9].com.amazon.Kindle[1427] dyld: Library not loaded: @executable_path/../Frameworks/libWEbCoreKRF.dylib
12/07/15 5:23:42 PM [0x0-0xa90a9].com.amazon.Kindle[1427] Referenced from: /Applications/Kindle.app/Contents/MacOS/../Frameworks/libWebCoreViewer.dylib
12/07/15 5:23:42 PM [0x0-0xa90a9].com.amazon.Kindle[1427] Reason: image not found
thanks to adobe i am primed to look for case-sensitivity issues, so the difference between libWEbCore and libWebCore jumped right out at me. looking inside the app bundle showed that indeed, libWebCoreKRF.dylib is present and accounted for.
fortunately this is easily fixed by creating a dynamic link from the correct lib to the misspelled one:
using terminal, admin privileges, go to the directory in question (/Applications/Kindle.app/Contents/Frameworks if you've installed in the usual place), and issue this command:
ln -s libWebCoreKRF.dylib libWEbCoreKRF.dylib
and the app will work for now -- until the next update. any bets on whether that'll fix the problem? yeah, didn't think so.
in better news, market day left us with ripe, local strawberries, and they are SO GOOD. and moroccan spice bread. and baked bread pudding. and fresh fudge.
no subject
on 2012-07-16 01:56 (UTC)no subject
on 2012-07-16 02:04 (UTC)no subject
on 2012-07-17 02:01 (UTC)no subject
on 2012-07-16 02:13 (UTC)no subject
on 2012-07-17 02:00 (UTC)no subject
on 2012-07-17 02:07 (UTC)no subject
on 2012-07-16 03:13 (UTC)no subject
on 2012-07-17 01:56 (UTC)wisdomdenial, adobe decided to force installation on the root disk, and if that is case-sensitive you're completely out of luck. ergo, i haven't upgraded. now that CS6 is out i guess i should check whether they fixed the problems but i seriously doubt it. oh, "amusingly" they blame it all on apple, like it's apple's fault some adobe programmers don't bother to tell "a" from "A". interestingly the folks who wrote lightroom have managed it. *rolls eyes*.no subject
on 2012-07-17 01:31 (UTC)Who am I fooling. I won't even remember that I mem'ed it.
I want to mem you for the next time I'm troubleshooting. (And now I bet I know why both Kindle for Mac and Nook for Mac work for shit.)
no subject
on 2012-07-17 01:58 (UTC)