Dr Bee

Q: Apple Mail quitting unexpected since I upgraded to El Capitan

Mail Quit Unexpectedly Click reopen to open the application again.

This report will be sent to apple automatically.

 

Problem Details and System Configuration

Process: Mail [428]

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

Identifier: com.apple.mail

Version: 9.0 (3094)

Build Info: Mail-3094000000000000~1

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Mail [428]

User ID: 501

 

Date/Time: 2015-10-19 14:52:11.263 -0700

OS Version: Mac OS X 10.11 (15A284)

Report Version: 11

Anonymous UUID: 9242E1E1-C2E8-D764-98DE-7CF130724B86

 

Sleep/Wake UUID: 5627CDDA-785F-4A34-A0CB-D1EAC44CC012

Mac OS X (10.5.8), dual 2GHz powerPCG5

Posted on Oct 19, 2015 3:43 PM

Close

Q: Apple Mail quitting unexpected since I upgraded to El Capitan

  • All replies
  • Helpful answers

  • by Carolyn Samit,Solvedanswer

    Carolyn Samit Carolyn Samit Oct 19, 2015 3:48 PM in response to Dr Bee
    Level 10 (122,382 points)
    Apple Music
    Oct 19, 2015 3:48 PM in response to Dr Bee

    Try holding down the Shift key at the same time as opening the Mail app.

     

    It may be a particular mail message that's causing the app to crash >  If Mail unexpectedly quits

  • by Linc Davis,

    Linc Davis Linc Davis Oct 19, 2015 10:03 PM in response to Dr Bee
    Level 10 (207,995 points)
    Applications
    Oct 19, 2015 10:03 PM in response to Dr Bee

    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. 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.

    When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.