Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Safari Won't Open

Last night, I was browsing the web on Safari, and it was working perfectly. Before I got off the computer, I started an update. Today, when I open safari, I get an error message saying "Safari cannot be opened because of a problem. Check with a developer to make sure Safari works with this version of OS X. You may need to re install the application. Be sure to install any available updates for the application and OS X. Click report to see more detailed information and send a report to Apple."


When I open the App Store to try to install updates, nothing loads. When I tried to move Google Chrome from another computer onto this one, it gives the same message when I try to open it, except replacing "Safari" with "Google Chrome".


I am running a 2011 iMac, 21.5 in. Base model.

iMac, OS X Mavericks (10.9.5)

Posted on Dec 31, 2014 9:27 AM

Reply
Question marked as Best reply

Posted on Dec 31, 2014 7:50 PM

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES All Messages

from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION User Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

5 replies
Question marked as Best reply

Dec 31, 2014 7:50 PM in response to technojd123

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES All Messages

from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION User Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

Apr 22, 2015 2:52 PM in response to technojd123

Safari "Unexpectedly quits" every time I try to launch it. Just completed the latest system update today


4/22/15 2:40:21.612 PM com.apple.xpc.launchd[1]: (com.apple.Safari.83528[792]) Service exited due to signal: Segmentation fault: 11

4/22/15 2:40:21.723 PM ReportCrash[797]: Saved crash report for Safari[792] version 8.0.5 (10600.5.17) to /Users/macster/Library/Logs/DiagnosticReports/Safari_2015-04-22-144021_CliftonM ac.crash


Process: Safari [692]

Path: /Applications/Safari.app/Contents/MacOS/Safari

Identifier: com.apple.Safari

Responsible: Safari [692]

__TEXT 00000001031d3000-00000001031d4000 [ 4K] r-x/rwx SM=COW /Applications/Safari.app/Contents/MacOS/Safari

com.genieo.safari-K444F5Z2ZH (1 - 1.2) Omnibar

61 com.apple.Safari.framework 0x0000000103253220 -[BrowserApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 246

79 com.apple.Safari.framework 0x0000000103253220 -[BrowserApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 246

Thread 5:: Dispatch queue: com.apple.SafariShared.WBSHistorySQLiteStore

2 com.apple.Safari.framework 0x00000001037b7af1 -[WBSHistorySQLiteStore _loadRedirectVisitsForLoadedItems:] + 636

3 com.apple.Safari.framework 0x00000001037b70f5 -[WBSHistorySQLiteStore _loadFromDatabase] + 1059

4 com.apple.Safari.framework 0x00000001037b6c0d -[WBSHistorySQLiteStore _openDatabase:andCheckIntegrity:] + 1025

5 com.apple.Safari.framework 0x00000001037b64b1 -[WBSHistorySQLiteStore _loadHistory] + 94

0x1031d3000 - 0x1031d3fff com.apple.Safari (8.0.4 - 10600.4.10.7) <F71CED11-0193-30D0-B31F-448F3F66DFAC> /Applications/Safari.app/Contents/MacOS/Safari

0x1031db000 - 0x103b28ff7 com.apple.Safari.framework (10600 - 10600.4.10.7) <0D208BCD-98F2-31BA-AF37-3F4EE03F197B> /System/Library/StagedFrameworks/Safari/Safari.framework/Versions/A/Safari

0x103fd8000 - 0x1044ecff3 com.apple.JavaScriptCore (10600 - 10600.4.10.5) <701BFF63-9106-3B4E-93D4-FC699BF12584> /System/Library/StagedFrameworks/Safari/JavaScriptCore.framework/Versions/A/Jav aScriptCore

0x104653000 - 0x104914fff com.apple.WebKit (10600 - 10600.4.10.7) <09625C49-A4CC-3D25-8769-93572F2508C8> /System/Library/StagedFrameworks/Safari/WebKit.framework/Versions/A/WebKit

0x104bf4000 - 0x104bf4fff com.apple.WebKit2 (10600 - 10600.4.10.7) <58F13B1B-136C-38E7-84FE-189721ED1A0C> /System/Library/StagedFrameworks/Safari/WebKit2.framework/Versions/A/WebKit2

0x104bfb000 - 0x104d43ff7 com.apple.WebKitLegacy (10600 - 10600.4.10.7) <58B4E00D-BD97-3509-9B43-9E7EA151BAEC> /System/Library/StagedFrameworks/Safari/WebKitLegacy.framework/Versions/A/WebKi tLegacy

0x104e47000 - 0x105dffffb com.apple.WebCore (10600 - 10600.4.10.7) <71274846-C8A3-3C56-964A-7C1F0DA5A65E> /System/Library/StagedFrameworks/Safari/WebCore.framework/Versions/A/WebCore

0x7fff86b94000 - 0x7fff86b96ff3 com.apple.SafariServices.framework (10600 - 10600.4.10.7) <5EEAF0C0-077D-3377-89F6-C0F33938F1E0> /System/Library/PrivateFrameworks/SafariServices.framework/Versions/A/SafariSer vices

Apr 23, 2015 6:52 AM in response to cliftonlemon

You might want to consider starting a new discussion. Since this one is marked solved, less people are likely to look at it. You can link to this one.

Do a backup, using either Time Machine or a cloning program, to ensure files/data can be recovered. Two backups are better than one.


Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.


Isolating an issue by using another user account


If the problem is still there, try booting into the Safe Mode using your normal account. Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don't do them all at once.


Safe Mode

Aug 18, 2015 5:38 PM in response to Linc Davis

Aug 18 09:56:53 Madavias-MacBook-Air com.apple.xpc.launchd[1] (com.apple.Safari.72736[638]): Service exited due to signal: Segmentation fault: 11

Aug 18 09:56:54 Madavias-MacBook-Air.local ReportCrash[643]: Saved crash report for Safari[638] version 8.0.6 (10600.6.3) to /Users/Johnson/Library/Logs/DiagnosticReports/Safari_2015-08-18-095654_Madavias -MacBook-Air.crash

Aug 18 17:21:03 Madavias-MacBook-Aircom.apple.xpc.launchd[1] (com.apple.Safari.72736[682]): Service exited due to signal: Segmentation fault: 11

Aug 18 17:21:03 Madavias-MacBook-Air.local ReportCrash[643]: Saved crash report for Safari[682] version 8.0.6 (10600.6.3) to /Users/Johnson/Library/Logs/DiagnosticReports/Safari_2015-08-18-172103_Madavias -MacBook-Air.crash

Aug 18 17:22:18 Madavias-MacBook-Air.local SubmitDiagInfo[343]: Submitted problem report file:///Users/Johnson/Library/Logs/DiagnosticReports/Safari_2015-08-18-095654_M adavias-MacBook-Air.crash

Aug 18 17:22:18 Madavias-MacBook-Air.local SubmitDiagInfo[343]: Submitted problem report file:///Users/Johnson/Library/Logs/DiagnosticReports/Safari_2015-08-18-172103_M adavias-MacBook-Air.crash


User Diagnostic Reports


rocess: Safari [1005]

Path: /Applications/Safari.app/Contents/MacOS/Safari

Identifier: com.apple.Safari

Responsible: Safari [1005]

__TEXT 000000010b495000-000000010b496000[ 4K] r-x/rwxSM=COW /Applications/Safari.app/Contents/MacOS/Safari

10 com.apple.Safari.framework 0x00007fff84ab6d30 -[BrowserApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 246

28 com.apple.Safari.framework 0x00007fff84ab6d30 -[BrowserApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 246

Thread 9:: Dispatch queue:com.apple.SafariShared.WBSHistorySQLiteStore

7 com.apple.Safari.framework 0x00007fff8505561c -[WBSSQLiteRowEnumerator nextObject] + 45

8 com.apple.Safari.framework 0x00007fff850209ff -[WBSHistorySQLiteStore _checkDatabaseIntegrity] + 71

9 com.apple.Safari.framework 0x00007fff85020cd6 -[WBSHistorySQLiteStore _openDatabase:andCheckIntegrity:] + 458

10 com.apple.Safari.framework 0x00007fff850207b1 -[WBSHistorySQLiteStore _loadHistory] + 94

0x10b495000 - 0x10b495fff com.apple.Safari (8.0.8 - 10600.8.9) <4D9DB548-1D8B-3745-8F70-54D1786368B6> /Applications/Safari.app/Contents/MacOS/Safari

0x7fff84a3f000 - 0x7fff8539efff com.apple.Safari.framework (10600 - 10600.8.9) <82302F92-6E83-3115-935F-3EF2B973A559> /System/Library/PrivateFrameworks/Safari.framework/Versions/A/Safari

0x7fff8f8bb000 - 0x7fff8f8bdff3 com.apple.SafariServices.framework(10600 - 10600.8.9) <A5BE8C63-2391-326A-90AE-5EF1B7CCD014> /System/Library/PrivateFrameworks/SafariServices.framework/Versions/A/SafariSer vices

Safari Won't Open

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.