MacBook Pro (13-inch, Mid 2012) (Technical Specifications)īluetooth: Good - Handoff/Airdrop2 supportedīattery: Health = Check Battery - Cycle count = 431 - SN = W02474PAAD3LC It varies between letting me type my log in, to being frozen, to making me repeat the log in process multiple times, to going black.Ĭlick the links for help with non-Apple products.Ĭlick the links for more information about that line.
From there, it’ll take anywhere from 5 to 10 minutes to get through the log in page. Upon opening, it takes about two minutes to get to the log in screen. My Mac takes a really long time to start up. Please post the text on Pastebin, then post a link here to the page you created. 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 don’t post other kinds of diagnostic report-they're very long and rarely helpful. 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.) Choose DIAGNOSTIC AND USAGE INFORMATION instead. If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. I know the report is long, maybe several hundred lines. Use copy and paste to post the entire contents-the text, not a screenshot. The contents of the report will appear on the right. A GPU restart report has a name that begins with "Kernel" and ends in ".gpuRestart". A panic report has a name that begins with "Kernel" and ends in ".panic". A crash report has a name that begins with the name of the crashed process and ends in ".crash". If the triangle is pointing to the right, click it so that it points down. There is a disclosure triangle to the left of the list item.
( not Diagnostic and Usage Messages) from the log list on the left. Anonymize before posting.ĭIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports Some private information, such as your name, may appear in the log. Please don't post screenshots of log messages-post the text. Please don't indiscriminately dump thousands of lines from the log into this discussion. In most cases, a few dozen lines are more than enough. When posting a log extract, be selective. Don’t post many repetitions of the same message. If there are long runs of repeated messages, please post only one example of each. Please include the BOOT_TIME message at the beginning of the log extract-not at the end. Paste into a reply to this message by pressing command-V.įor example, if the problem is a slow startup taking three minutes, post the messages timestamped within three minutes after the boot time, not before. Copy them to the Clipboard by pressing the key combination command-C. Select the ones logged after the boot, during the time something abnormal was happening. Now clear the search box to reveal all messages. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Enter "BOOT_TIME" (without the quotes.)Įach message in the log begins with the date and time when it was entered. In the top right corner of the Console window, there's a search box labeled Filter.
If you don't see that list, selectįrom the menu bar at the top of the screen. If it isn't, selectįrom the log list on the left. ☞ Open LaunchPad and start typing the name.įor this step, the title of the Console window should be All Messages. The application is in the folder that opens. ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. Select it in the results (it should be at the top.) ☞ Enter the first few letters of its name into a Spotlight search. Launch the Console application in any of the following ways: If you have only one user account, you are the administrator. These instructions must be carried out as an administrator.
0 kommentar(er)
