-
All replies
-
Helpful answers
-
Jun 27, 2016 6:00 AM in response to Montenegrinby lllaass,Just how are you trying to Share?
• Note the time that yo try to share a closed file. Then open the Console app in Finder>Applications>Utilities and look for log entries at the time of the reboot. Post suspicious ones here.
Repeat for open file
You can also try:
- Try resetting the SMC and NVRAM/PRAM
Intel-based Macs: Resetting the System Management Controller (SMC)
https://support.apple.com/en-us/HT201295
About NVRAM and PRAM
https://support.apple.com/en-us/HT204063
- Try starting in Safe Mode
OS X: What is Safe Boot, Safe Mode?
https://support.apple.com/en-us/HT201262
- Boot to Recovery and repair the startup disk
OS X: About OS X Recovery - Apple Support
https://support.apple.com/en-us/HT201314
- If it is repairable reinstall the OSX
How to reinstall OS X on your Mac - Apple Support
https://support.apple.com/en-us/HT204904
- If you do not have a backup use disk utility to restore the internal disk to an external disk so you can try to recover data.
Then format the startup disk and do a fresh install of OSX
-
Jun 27, 2016 6:19 AM in response to Montenegrinby Linc Davis,Please launch the Console application in any one 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.
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.
Click the Clear Display icon in the toolbar. Then take an action that isn't working the way you expect. Select any lines that appear in the Console window. 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 or email address, may appear in the log. Anonymize before posting.
When you post the log extract, 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.
If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.
-
Jun 27, 2016 7:07 AM in response to Linc Davisby Montenegrin,Thank you, guys!
It seemed easier to do first what Linc Davis suggested.
Here are the lines you suggested I post:
27/06/16 16:03:06,974 com.apple.xpc.launchd[1]: (com.apple.coresymbolicationd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
27/06/16 16:03:07,533 ReportCrash[5269]: Invalid connection: com.apple.coresymbolicationd
27/06/16 16:03:10,473 ReportCrash[5269]: Saved crash report for ShareMail[5268] version 1.0 (454.21) to /Users/USERNAME/Library/Logs/DiagnosticReports/ShareMail_2016-06-27-160310_USER NAMEs-MacBook-Pro.crash
-
Jun 27, 2016 7:10 AM in response to Montenegrinby Linc Davis,There's a problem with your OS X installation. The simplest way, but not the fastest way, to fix it is to reinstall the OS. Unless you're in a hurry or have metered network access, that's what I suggest, especially since I don't know whether there are other problems with the installation. Please back up all data before reinstalling. You won't need the backup unless something goes wrong.
The advanced shortcut below, if it works, may save you some downtime (and the cost of a multi-gigabyte download, if applicable.)
1. Back up all data.
2. Disconnect all external storage devices.
3. Start up in Recovery mode. Select a language, if prompted. The OS X Utilities screen will appear. One of the options is to install OS X. That's not what you're going to do.
4. This step is only necessary if you use FileVault 2. If you don't know what FileVault is, you're not using it. Go to the next step. Otherwise, launch Disk Utility, then select the icon of the FileVault volume ("Macintosh HD," unless you gave it a different name.) It will be nested below another drive icon. Select Unlock from the File menu and enter your login password when prompted. Then quit Disk Utility to be returned to the main screen.
5. Select Get Help Online. Safari will launch. While in Recovery, you'll have no access to your bookmarks, but you won't need them. Load this web page.
6. Triple-click anywhere in the line below to select it:
chflags -R norestricted /V*/*/S*/*/Caches
Copy the selected text to the Clipboard by pressing the key combination command-C.
7. Quit Safari. You'll be returned to the OS X Utilities screen.
From the menu bar, select
Utilities ▹ Terminal
The Terminal application will launch. Paste into the Terminal window by pressing the key combination command-V.
Wait for a new line ending in a hash sign (#) to appear. Quit Terminal to be returned to the main screen.
8. Select
▹ Restart
from the menu bar.
9. This step must be carried out after the restart and while you're logged in as an administrator—not in Recovery mode. If you have only one user account, you are the administrator.
Select and copy this line as in Step 6:
sudo /usr/libexec/xpchelper --rebuild-cache
Paste into a Terminal window as before. You'll be prompted for your login password. Nothing will be displayed when you type it. Type carefully and then press return. If you don’t have a login password, you’ll need to set one before you can run the command. You may get a one-time warning to be careful. Confirm. You don't need to post the warning.
If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator. Log in as one and start this step over. You don't have to repeat the earlier steps.
Wait for a new line ending in a dollar sign ($) to appear below what you entered.
10. Do as in Step 9 with this line:
sudo /usr/libexec/*/app_sandbox_cache_builder --rebuild-cache
You can then quit Terminal.