#SIGN OUT KINDLE ON MAC HOW TO#
#SIGN OUT KINDLE ON MAC INSTALL#
#SIGN OUT KINDLE ON MAC SOFTWARE#
#SIGN OUT KINDLE ON MAC MAC#

Sudo ln -s libWebCoreKRF.dylib libWEbCoreKRF.dylibĪt that point it will ask for your password. If you have this window up in a browser you should be able to copy from the browser window and paste into the Terminal window:Ĭd /Applications/Kindle.app/Contents/Frameworks Once Terminal is up and running type the following two commands exactly. Bring up a Finder window and go to Applications -> Utilities -> Terminal and launch that application. So I had to employ the sudo command in addition to what you typed above.ĭetailed instructions for others to follow: Even when running as the Admin account it still failed.

#SIGN OUT KINDLE ON MAC MAC#

I run my Mac with multiple generic users for security reasons. When I tried it (OS Mountain Lion) the ln -s command failed due to no file permissions. Allow me to explain for the benefit of others. Lancer Kind - That was absolutely great and solved my problems too, but I did have to make a slight tweak.

#SIGN OUT KINDLE ON MAC HOW TO#

And does someone know how to report the problem to Amazon? I imagine many people have the same problem as I am. If you're not getting the exact same symptom as I am, then this solution will not help you. Other solutions: probably could use dyld to re-assign what library libWebCoreViewer.dylib is using and tell it to use the one with the lower-case 'e'. Make sure you DON'T put the arguments in the wrong order or you'll overwrite your existing libWebCoreKRF.dylib (a common mistake even among seasoned professionals), so make sure the argument with the captial 'E' is at the end. Workaround you only have to do once: make a 'file alias' using the ln command: $ln -s libWebCoreKRF.dylib libWEbCoreKRF.dylib.But we don't have time to wait for Amazon, we've got books to read, so read on. And tell them to test their releases on a 'clean machine' so they catch these problems in the future. Best solution: Amazon correct how it's linking libWebCoreViewer.dylib to libWebCoreKRF.Reveals that it's spelled libWebCoreKRF.dylib (NO capital E, per conventional coding standards.)

$ls /Applications/Kindle.app/Contents/Frameworks Note with interest the suspicious spelling of is spelled WEbCore (the capital 'E' is not to conventional coding standards and should be a lower case 'e'. : Referenced from: /Applications/Kindle.app/Contents/MacOS/./Frameworks/libWebCoreViewer.dylibħ/10/12 12:01:07.495 AM. The symptom: Using the Console I got the following error message for Kindle:ħ/10/12 12:01:07.495 AM. Today I had some time to play and with the above information, this is what I discovered the problem to be: Today I got it working again for Kindle V1.9.2 (38421).

An old version of Kindle did work but I let it 'get away' from me and so I just didn't use it on the Mac for 8 months. Since Lion and probably even on Snow Leopard, my Kindle app wouldn't work when installed from Amazon or via the App Store.

#SIGN OUT KINDLE ON MAC INSTALL#

Reading through this thread, I was able to discover the root cause, at least for my install of the Kindle. I think the problem originates with the programmers' or publishers' concern about DRM and copying files.

#SIGN OUT KINDLE ON MAC SOFTWARE#

I use free Tinker Tool software that lets system and hidden files be visible when I want them to be. I don't really know UNIX, so outside of Terminal you can access this hidden folder by choosing Finder>Go>Go To Folder and typing the path, then right clicking on the folder when it appears. Then you shouldn't have any problems launching the Kindle app, even from aliases. Adjust permissions as you like for other users of the computer, but leave the padlock unlocked. Click the padlock at the lower right of the window that opens, then type your administrator password. Then I right-clicked and selected Get Info on the folder. What I ended up doing was accessing ~/Library/Application Support/Kindle/My Kindle Content (which is a system/hidden file). Someone at Amazon doesn't understand the Lion permissions structure (I don't either, I guess). It's when it's moved or aliased that it won't launch. I tested it by downloading and launching the app directly from the Kindle disk img without moving it, and it opened without a problem. I believe it is in fact a permissions problem.

Sign out kindle on mac