View Single Post
Old 12-04-2019, 11:48 PM   #666
odamizu
just an egg
odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.odamizu ought to be getting tired of karma fortunes by now.
 
odamizu's Avatar
 
Posts: 1,892
Karma: 8046246
Join Date: Mar 2015
Device: Kindle, iOS
Quote:
Originally Posted by Amazondoc View Post
Gah.

I had this all set up and running in Catalina -- but suddenly the Kindle-for-Mac app decided it would never open again. Ever. Dunno why -- but I was also doing a lot of overloading the RAM with bazillions of Firefox tabs at the time, and getting a lot of kernel panics. I mean, like 40 or 50 crashes. The crashes have calmed down since I pared down the windows and tabs open, but the Kindle app still won't open.

I originally used the "chmod -x /Applications/Kindle.app/Contents/MacOS/renderer-test" string; if I want to remove that to see if I can get the app to open, do I use "chmod +x (etc.)"?

I know you've posted this instruction somewhere, but now that I need it I can't find it.

If you have any other suggestions, any ideas would be welcomed!
Yes, changing chmod -x to chmod +x will undo chmod -x and re-enable renderer-test. (Note: this will give you KFX that Alf can't deal with.)

You might also try deleting the Kindle for Mac app and re-installing it. But delete only the app itself. Do not delete anything else, leave everything in your Library folder untouched.

Good luck!
odamizu is offline