-
All replies
-
Helpful answers
-
-
Nov 19, 2015 3:51 PM in response to raybluby OpalCheek,THANK YOU, rayblu! This finally worked for me. I only figured it out because you told me how to get to the "Go go folder". After following your instructions, and deleting the two files, iPhoto no longer crashes after I open it. I also closed out iPhoto, reopened it, and it stayed open, allowed me to edit, etc. Everything seems back to normal. I appreciate the suggestion!
-
Nov 19, 2015 4:01 PM in response to Huxly647by Larryfromab,Huxly647 - removing Googlemap and Googlesearch worked for me. You are the guru today.
I tried other fixes and this is the one that finally worked. The problem just started for me today.
-
-
Nov 19, 2015 9:56 PM in response to raybluby ladarlene,It worked!! May you have turkey with no leftovers and bottles of wine for Thanksgiving!
-
Nov 19, 2015 11:01 PM in response to Huxly647by carvermon,Howdy,
I finally got around to deleting the google files (you're quite the hero around the forum for figuring that fix) and upon launching iPhoto got an option to deny or allow incoming connections - what is the best choice here?
Thanks!
-
Nov 20, 2015 12:10 AM in response to carvermonby Huxly647,★HelpfulHi,
i'd click yes to allow if you use shared photostreams. Then check in the iphoto preferences and see if the sharing box is checked too. If this pop appears next time you start iphoto try checking disk permissions.
Huxly647
-
Nov 20, 2015 12:16 AM in response to Huxly647by carvermon,Thanks for the reply. Yeah, I went ahead and allowed after remembering I had flickr and facebook connections to iPhoto.
Iphoto has been open all evening, thanks to you! Did get to wondering how you figured that those google files were the troublemakers, and why they affected the "info" panel (the Places thing made sense, but not so much the info thing).
-
Nov 20, 2015 12:39 AM in response to carvermonby Huxly647,Oh i just tried all the usual steps etc for rebuilding iphoto database at first, then I thought it was due to apples locations services but that wasnt it. Tried disconnecting my internet connection and iphoto opened just fine. So pursued that route...lots of digging and testing and any clues i could find online...
-
Nov 20, 2015 12:48 AM in response to Huxly647by Abbax,Hi Huxley 647
Since last night, I have the same issue with iPhoto (crashing immediately after opening) and wanted to try your recommendation: "goto /Applications/iPhoto.app/Contents/ Resources". I cannot get to .../contents/resources in the finder. When I go to Applications/iPhoto in the Finder, there is no option for me to get further. Where on my Mac would I be able to follow the recommended path?
Please excuse the question, I am not that versed with the technical stuff on my Mac.
Thanks,
Abbax -
Nov 20, 2015 1:15 AM in response to Abbaxby Huxly647,Hi Abbax
The easiest way as pointed out by Rayblu is to do the following:
"click Finder and the "Go" menu item. Then click "Go to folder ..." at the bottom and enter /Applications/iPhoto.app/Contents/Resources and click "go". Then delete the 2 google files"
-
Nov 20, 2015 1:22 AM in response to Huxly647by Abbax,Thank you Huxley 647. This got me one step further. The result is getting the message "this folder cannot be found"
Any idea how I could work around this? -
Nov 20, 2015 1:54 AM in response to Abbaxby Huxly647,Hmm you might have to enable 'show hidden files' - check google for instructions. I'm not in front of my mac at the moment so cant check.
-
Nov 20, 2015 2:15 AM in response to Abbaxby Terence Devlin,Right click on the iPhoto icon and choose 'Show Package Contents...'
-
Nov 20, 2015 2:27 AM in response to Terence Devlinby Dredger,I don't want to sound argumentative or dismissive, but I don't feel confident enough to go poking about in areas to remove this, change that, move the other.
The whole point is that this is a sudden and common problem affecting dozens and none of us should be having to do this.
It was working perfectly before the other day, so what's stopped it now? There needs to be a fix or update that takes care of this, not for dozens of users to be poking about in areas they know nothing about to make something work that worked perfectly the other day.