I am running OS X El Capitan version 10.11.6 on a MacBook Pro. Here’s what happened:
[ul][li]I opened the Mueller Report in Preview.[/li][li]I copied some text and did a Find (command-F).[/li][li]I pasted the text into the Find box and hit Enter.[/li][li]Preview ‘quit unexpectedly’.[/li][li]I tried reopening the file, and Preview immediately quit.[/li][li]I restarted my computer.[/li][li]Upon restarting, I tried opening the file again.[/li][li]Preview quit immediately.[/li][li]I tried to open a .jpg file, and Preview quit immediately.[/ul][/li]I searched ‘preview quit unexpectedly’ and found this page:
I am uncomfortable removing files, but I thought I’d give it a try. I opened Finder and did a command-J to get to Show View Options. There is no ‘Show Library Folder’ option, so I’m dead in the water right there. I kept searching, and found the last three files and deleted them. Preview still quits immediately.
Question 1: How to I get Preview working again?
Question 2: I did a backup using Time Machine about a week ago. If I need to recover from there, how do I do it?
I can’t answer your questions directly, but I’d suggest you contact apple customer support directly and ask them.
I had a similar situation with Photos recently, the app would launch then crash. I’m using a 5 year old MacBook Pro. I called Apple 1-800 # and I spent over 2 hours on the phone with a senior support tech. The guy walked me through possible solutions and finally we ended up doing a full OS wipe and then reloaded the new OS from scratch followed by a compete (non-OS) restore from Time Machine.
Since the restore took a few hours, the guy gave me his personal Apple email so I could contact him immediately/directly if anything went wrong. He also scheduled a call back in a couple days to check in and verify the problem was resolved. All for a 5 year old laptop.
The guy said since the problem was with Photos, which a “core” apple software product, they take issues seriously.
Since Preview is a similar Apple product, hopefully they’ll help you out.
I’ve never had any luck with Apple Support. Either I can’t get through, or there’s something else.
I have restored my system to the 27th of May. I emailed an important, daily-updated file to myself, so I have it back. (NB: I shut down, and then restarted with command-R.)
I guess if I want to read the Mueller Report, I should do it from a website.
The other way to access that folder is to go to the Finder, select “Go To Folder…” under the “Go” menu, and enter “/Users/[username]/Library” into the dialog box that pops up.
Or put a Finder window in View as columns; go into your Home folder (if it’s not on the sidebar, go into Macintosh Hard Drive and into Users and then into Home). In the Home folder you should see, among other things, the Library folder; and inside that a whole list of things – one of them for instance is Container and the Container items are inside that.
Command+Shift+dot/period will also show you hidden folders. (Only putting this out there because I just discovered it today. I’ve long just used a terminal command to display all hidden files and folders, but I guess there’s been an easier way to do this for awhile now. Looks like it was introduced in Sierra.)
Also, if you have the usual files and folders hidden, just click on your desktop background to bring Finder to the fore, and hold down alt while clicking on “Go” in the menu, and “Library” will show up as an option.
Huh. I just discovered that the “go” menu, which I never use (is that new?) has the Library folder right in it. Also Utiilies, and a batch of others. Maybe I will use it once in a while.
ETA: you don’t need to hold down alt. Just go into Finder and then click on Go in the menu bar; slide down to Library and click on that.
Sometimes you do, sometimes you don’t. Depends what version of OS X you’re running and/or what your settings are.
In OS X Lion (10.7) and earlier, it’s not hidden.
In OS X Mountain Lion (10.8), you have to use the alt key, or you can permanently unhide it by opening Terminal and entering “chflags nohidden ~/Library” [enter].
In OS X Mavericks (10.9) and later, it’s simply an option in Finder “View Options”: open a Finder window (don’t just click on the desktop)->View->Show View Options->check the box next to “Show Library Folder.”
I wasn’t actually doing any of those (though usually what I’ve done has been to open a Finder window and click on “home”, which I put on my Finder sidebar quite a while ago.) What I just discovered was that if I go into Finder (with or without a window open), the menu bar at the top of the screen has as one of the items “Go”, and that clicking on that produces a list of options one of which is “Library”.
Did you unhide the hidden folders by any chance? I’m on Mojave 10.14.5, and if I unhide hidden folders when I use the command-shift-period shortcut (or through the terminal command), then Library shows up in Finder under Go without having to use alt. If I hide the folders again by using the shortcut or the terminal command, then Library doesn’t show up under Finder > Go unless I do hit alt.
It some point you must have told the OS to unhide that folder.
That setting is honored through system updates.
The /Library and ~/Library folders have been hidden by default for over a decade.
Ah. That would explain it; I’ve been using a Mac longer than that.
If updates have all honored previous settings, then it’s just copying that over – except, wait a minute, the new computer comes with a new system. I transferred files; maybe the setup assistant transferred those settings, also.
I’m pretty sure I’d remember if at some point my library folder had disappeared and I’d had to hunt around trying to figure out how to make it appear again.
Generally, you can get the same results by moving files elsewhere instead of deleting them. That’s a good first step if you’re nervous about following instructions to delete something. If it fixes things, then you can leave them in the new location for as long as you feel comfortable. If it doesn’t, you can move them back, which also helps make sure that you vary as few things as possible at time.
The worst bugs to diagnose are the ones where your first attempt to fix things broke something else, so even when you solve the original thing, you’ve broken it in some other way.