Q: So many problems with El Capitan
-
Nov 9, 2015 2:52 PMby dianeoforegon,I just fixed this on a client's Mac using the following steps. I first tried to reset keychain so I suggest you try this option first. You'll be asked to re-enter passwords at least once but you shouldn't get the constant password requests.
Reset your Keychain
Open Keychain Access, which is in the Utilities folder within the Applications folder.
From the Keychain Access menu, choose Preferences.
Click General, then click Reset My Default Keychain.
Authenticate with your account login password.
Quit Keychain Access.
Restart your computer.
If this fails, try this step.
Go to your User's Library folder. (see below)
Scroll down to the Keychain folder.
Rename to KeychainXXX
Log out under the Apple in the Menu bar.
Log in
A new Keychain folder is created in your User's Library.
You'll need to enter your password for your Apple ID in System Preferences > iCloud along with all your other accounts like email, In your Apple apps: Messages, Contacts, Calendars
We also had to reset the Apple ID password.
You can revert to the old Keychain folder by deleting the new and removing xxx from old folder.
Show User's Library
The User's Library folder is hidden by default. To unhide: Select the Finder in the Dock. Under Go in the Menu bar > hold down the Option key and you’ll see the Library.
Finding the User Library Folder
http://www.takecontrolbooks.com/resources/0167/site/chap11.html#FindingtheUserLi braryFolder
-
Nov 9, 2015 8:23 PMby Dani258,Apple Support had me reinstall El Capitan and change the password through user & groups preferences. I also did a clean install, created an admin user account, reset my login Keychain through Keychain Access, reset password through terminal in Recovery mode, and I did as you suggested to someone in the post “File Saving Permission.”
I did reset Keychain through Keychain Access again today and that created the problem of not being able to sign into iCloud System Preferences. I have not tried the other option that Dianeoforegon suggested, but I will since I haven't tried that yet.
-
Nov 9, 2015 8:31 PMby Dani258,Thank you for the suggestions to correct the keychain issues. I did try to reset login keychain through keychain access, and I still received the same login popups. I started having a problem signing into iCloud System Preferences soon after resetting the keychain so I needed to take care of that before trying Option 2. I'll try that soon, though, and will report back with the results.
-
Nov 9, 2015 8:51 PMby Dani258,Actually, a good portion of these problems started after updating to 10.11.1 so I restored a backup from 10.11 when these issues didn't exist hoping it would help. Doing this did correct some issues for a little bit, but then I started having problems again so I decided to update back to 10.11.1 hoping it would be better the second time around, but unfortunately, it wasn't.
-
Nov 9, 2015 9:01 PMby Linc Davis,The most important issue you raise in your original post concerns backups. You must be sure that your data is being safely backed up before you do anything else. What is the backup device, and how far back does the timeline on the right go when you enter Time Machine?
-
Nov 9, 2015 10:32 PMby Dani258,I have two external drives for backup. The first is the LaCie Slim I have been using since I got my Mac, and it has backups from July 2014 to Sept. 2015. Once I updated to El Capitan, it said there wasn't enough space, even though it had 120GB free, so I bought a Seagate Slim 1TB for backups. The Seagate already has used up 300GB from Oct. 10 to Nov. 6; maybe 7-8 backups, and LaCie only used 300GB in a year and a half. And even though the recent backups are probably good, I'm not confident that they are since backing up was so much different before El Capitan.
I wanted to still use the Lacie drive though since it had over 100GB free so I tried to backup on Lacie once the Seagate had a complete backup. It said "preparing backup" then said there wasn't enough space, even though the amount it showed for the backup was much less than what it showed as available. At that point, it started deleting my earlier backups from when I first bought my Mac. It deleted everything from Jan. 2014 through July 2014. I thought it would start the backup but it just kept deleting previous backups, I finally stopped it and removed the drive from Time Machine immediately. I wish I stopped it sooner before losing those backups, but unfortunately, I didn't.
Probably more information than you needed or wanted to hear so I apologize for that. Thank you for any advice you can provide.
-
Nov 10, 2015 7:34 AMby Linc Davis,It sounds like you need larger backup drives, but your backups are otherwise OK. Since 1 TB is not enough, try 3 TB.
Returning to the original question, please see below.
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.
-
Nov 10, 2015 3:52 PMby Dani258,Here is the link to pastebin for a finder crash from today:
Hopefully, these are what you want. I wasn’t able to reenact the crash today for the issues except for the canon scanner. This looks a lot like the crash report from the user diagnostic’s link to pastebin though so please let me know if you need something else. Thank you!
Keychain Access
Date/Time: 2015-11-08 11:55:40 -0600
OS Version: Mac OS X 10.11.1 (Build 15B42)
Architecture: x86_64h
Report Version: 22
Command: Keychain Access
Path: /Applications/Utilities/Keychain Access.app/Contents/MacOS/Keychain Access
Version: 9.0 (55171.10.2)
Build Version: 59
Project Name: KeychainAccess
Source Version: 55171010002000000
Parent: launchd [1]
PID: 536
Event: hang
Duration: 1.90s (process was unresponsive for 47 seconds before sampling)
Steps: 19 (100ms sampling interval)
Hardware model: MacBookPro11,1
Active cpus: 4
Fan speed: 1293 rpm
--------------------------------------------------
Timeline format: stacks are sorted chronologically
Use -i and -heavy to re-report with count sorting
--------------------------------------------------
Heaviest stack for the main thread of the target process:
19 start + 1 (libdyld.dylib + 13741) [0x7fff9364f5ad]
19 NSApplicationMain + 1176 (AppKit + 28606) [0x7fff94bc9fbe]
19 -[NSApplication run] + 682 (AppKit + 253224) [0x7fff94c00d28]
19 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454 (AppKit + 299461) [0x7fff94c0c1c5]
19 _DPSNextEvent + 1067 (AppKit + 302486) [0x7fff94c0cd96]
19 _BlockUntilNextEventMatchingListInModeWithFilter + 71 (HIToolbox + 199119) [0x7fff91f589cf]
19 ReceiveNextEventCommon + 432 (HIToolbox + 199567) [0x7fff91f58b8f]
19 RunCurrentEventLoopInMode + 235 (HIToolbox + 200021) [0x7fff91f58d55]
19 CFRunLoopRunSpecific + 296 (CoreFoundation + 561096) [0x7fff8ea3bfc8]
19 __CFRunLoopRun + 1949 (CoreFoundation + 563661) [0x7fff8ea3c9cd]
19 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9 (CoreFoundation + 829849) [0x7fff8ea7d999]
19 _dispatch_main_queue_callback_4CF + 1685 (libdispatch.dylib + 89115) [0x7fff92a41c1b]
19 _dispatch_client_callout + 8 (libdispatch.dylib + 9155) [0x7fff92a2e3c3]
19 _dispatch_call_block_and_release + 12 (libdispatch.dylib + 55541) [0x7fff92a398f5]
19 ___notify_dispatch_local_notification_block_invoke + 31 (libsystem_notify.dylib + 36235) [0x7fff970edd8b]
19 ??? (Keychain Access + 30169) [0x1055bb5d9]
System Preferences
Date/Time: 2015-11-08 12:34:04 -0600
OS Version: Mac OS X 10.11.1 (Build 15B42)
Architecture: x86_64h
Report Version: 22
Command: System Preferences
Path: /Applications/System Preferences.app/Contents/MacOS/System Preferences
Version: 14.0 (14.0)
Build Version: 21
Project Name: SystemPrefsApp
Source Version: 303000000000000
Parent: launchd [1]
PID: 5728
Event: hang
Duration: 1.90s (process was unresponsive for 22 seconds before sampling)
Steps: 19 (100ms sampling interval)
Hardware model: MacBookPro11,1
Active cpus: 4
Fan speed: 1290 rpm
--------------------------------------------------
Timeline format: stacks are sorted chronologically
Use -i and -heavy to re-report with count sorting
--------------------------------------------------
Heaviest stack for the main thread of the target process:
19 ??? (<99396189-E53A-3A78-BC49-449236DA7CFF> + 13741) [0x1107f85ad]
19 ??? (<9B600863-6A16-31CB-8138-97AC8F43FBC6> + 28606) [0x10cf2dfbe]
19 ??? (<9B600863-6A16-31CB-8138-97AC8F43FBC6> + 253224) [0x10cf64d28]
19 ??? (<9B600863-6A16-31CB-8138-97AC8F43FBC6> + 299461) [0x10cf701c5]
19 ??? (<9B600863-6A16-31CB-8138-97AC8F43FBC6> + 302486) [0x10cf70d96]
19 ??? (<359FC9DB-B64C-3BC7-B9DA-401D8A5337DC> + 199119) [0x10feef9cf]
19 ??? (<359FC9DB-B64C-3BC7-B9DA-401D8A5337DC> + 199319) [0x10feefa97]
19 ??? (<359FC9DB-B64C-3BC7-B9DA-401D8A5337DC> + 200021) [0x10feefd55]
19 ??? (<86B26482-C917-34F2-80D8-02911B6001E0> + 561096) [0x10e485fc8]
19 ??? (<86B26482-C917-34F2-80D8-02911B6001E0> + 563661) [0x10e4869cd]
19 ??? (<86B26482-C917-34F2-80D8-02911B6001E0> + 829849) [0x10e4c7999]
19 ??? (<438F4595-0731-34A2-ACAD-60121A76D1FF> + 89115) [0x1107b1c1b]
19 ??? (<438F4595-0731-34A2-ACAD-60121A76D1FF> + 9155) [0x11079e3c3]
19 ??? (<438F4595-0731-34A2-ACAD-60121A76D1FF> + 55541) [0x1107a98f5]
19 ??? (System Preferences + 32160) [0x10b85dda0]
Canon Scanner
Process: Canon IJ Scan Utility2 [738]
Path: /Applications/Canon Utilities/*/Canon IJ Scan Utility2.app/Contents/MacOS/Canon IJ Scan Utility2
Identifier: jp.co.canon.ij.scanutility2
Version: 2.0.0 (29)
Build Info: ScanningCanon-1~1
Code Type: X86 (Native)
Parent Process: ??? [1]
Responsible: Canon IJ Scan Utility2 [738]
User ID: 501
Date/Time: 2015-11-10 13:41:08.571 -0600
OS Version: Mac OS X 10.11.1 (15B42)
Report Version: 11
Anonymous UUID: XXXXXX
Sleep/Wake UUID: 50ADB688-C0DB-4EEA-83AA-547D021D48EB
Time Awake Since Boot: 3000 seconds
Time Since Wake: 2800 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Dyld Error Message:
can't resolve symbol _CSGetMainInfo in /Applications/Canon Utilities/IJ Scan Utility/Canon IJ Scan Utility2.app/Contents/MacOS/../Frameworks/UIC.framework/Versions/A/UIC because dependent dylib #1 could not be loaded
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 dyld 0x8fe8b085 dyld_fatal_error + 1
1 dyld 0x8fe8df59 dyld::fastBindLazySymbol(ImageLoader**, unsigned long) + 150
2 libdyld.dylib 0x989dd31c dyld_stub_binder_ + 20
3 jp.co.canon.ij.scanutility2.UIC 0x00736d10 Wrap_Call_CSGetMainInfo(signed char const*, NSMutableString*, tagResultS*, tagCSCommonV*, short*, short*) + 85
4 jp.co.canon.ij.scanutility2.UIC 0x0071eb84 UC_Caddis::GetMainInfo(std::vector<tagResultS, std::allocator<tagResultS> >&, std::vector<tagCSCommonV, std::allocator<tagCSCommonV> >&, short*, short*) const + 68
5 jp.co.canon.ij.scanutility2.UIC 0x0072056a UC_LLDCaddis::Update() + 352
6 jp.co.canon.ij.scanutility2.UIC 0x00725784 UC_MergeInfo::Update(unsigned long) + 832
7 jp.co.canon.ij.scanutility2.UIC 0x0071f1aa UC_UIControl::Update(unsigned long) + 32
8 jp.co.canon.ij.scanutility2.UIC 0x00735f1b UIController_Update + 105
9 jp.co.canon.ij.scanutility2 0x000351e7 UIControllInterface::Update(int, unsigned long) + 57
10 jp.co.canon.ij.scanutility2 0x00037fea -[CIJSU_AppDelegate StartScanUtility:] + 490
11 com.apple.Foundation 0x99b5f961 __NSFireDelayedPerform + 489
12 com.apple.CoreFoundation 0x9a6e6476 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 22
13 com.apple.CoreFoundation 0x9a6e5f22 __CFRunLoopDoTimer + 1250
14 com.apple.CoreFoundation 0x9a6e59ad __CFRunLoopDoTimers + 349
15 com.apple.CoreFoundation 0x9a6dc8a1 __CFRunLoopRun + 2113
16 com.apple.CoreFoundation 0x9a6dbdf6 CFRunLoopRunSpecific + 390
17 com.apple.CoreFoundation 0x9a6dbc5b CFRunLoopRunInMode + 123
18 com.apple.HIToolbox 0x94732719 RunCurrentEventLoopInMode + 267
19 com.apple.HIToolbox 0x9473251b ReceiveNextEventCommon + 503
20 com.apple.HIToolbox 0x94732314 _BlockUntilNextEventMatchingListInModeWithFilter + 99
Process: securityd [79]
Path: /usr/sbin/securityd
Identifier: securityd
Version: 57336.10.29
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: securityd [79]
User ID: 0
Date/Time: 2015-11-08 11:54:53.923 -0600
OS Version: Mac OS X 10.11.1 (15B42)
Report Version: 11
Anonymous UUID: XXXXX
Sleep/Wake UUID: 2CEB1304-8D46-4B82-A709-7233EABC077E
Time Awake Since Boot: 1800 seconds
Time Since Wake: 540 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0:
-->
__TEXT 0000000103ae9000-0000000103bbc000 [ 844K] r-x/rwx SM=COW /usr/sbin/securityd
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libc++abi.dylib 0x00007fff8e37eb1e __dynamic_cast + 34
1 securityd 0x0000000103af63bc 0x103ae9000 + 54204
2 securityd 0x0000000103af7072 0x103ae9000 + 57458
3 securityd 0x0000000103af6b6d 0x103ae9000 + 56173
