So many problems with El Capitan

Question

Can someone please help me with these problems or let me know if I should just revert to the previous OS since I&#x27;m having so many problems since upgrading to El Capitan?  I might take care of one problem for a little bit, but then it comes back.  Even though I&#x27;m probably forgetting some of the issues, these are the main problems I&#x27;m dealing with:Constant problems with keychain.  I have 42 public keys for iMessage Encryption Key and 42 private keys for iMessage Encryption Key, and they just keep building.  I&#x27;m asked for my keychain password for accountsd, local keychain, iCloud keychain, cloudd, and possibly others.  If I have too many Safari windows running, the fan kicks in and my laptop gets hot.  Time machine will backup every so often, but only shows 3-5 snapshots from today and the night before, and not every hour but sporadically.  None are kept past the day before.  It does have the backups I&#x27;ve done manually though, so it shows 3-5 snapshots from today and last night and the manuel backups.  It won&#x27;t show today&#x27;s date or yesterday&#x27;s date in three days; they&#x27;re gone and replaced with today&#x27;s and last night&#x27;s.  Snapshots are not kept. (sorry, it&#x27;s confusing)   System preferences, keychain, Safari, and iCloud preferences crash often, and for the first time today iTunes crashed.I&#x27;ve tried various things at different times to try to take care of these issues, and since I haven&#x27;t had any success and the Apple Support calls haven&#x27;t resolved the issues either, I won&#x27;t bore you with those details unless asked.  I know I&#x27;m not the only one dealing with these issues, so as you know, this is very time consuming and frustrating, and I can&#x27;t wait for these bugs in El Capitan to be behind us.

Linc Davis · Answer

I won&#x27;t bore you with those details unless asked.Please bore me with the details.

dianeoforegon · Answer

I just fixed this on a client&#x27;s Mac using the following steps. I first tried to reset keychain so I suggest you try this option first. You&#x27;ll be asked to re-enter passwords at least once but you shouldn&#x27;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&#x27;s Library folder. (see below)Scroll down to the Keychain folder.Rename to KeychainXXXLog out under the Apple in the Menu bar.Log inA new Keychain folder is created in your User&#x27;s Library.You&#x27;ll need to enter your password for your Apple ID in System Preferences &gt; iCloud along with all your other accounts like email, In your Apple apps: Messages, Contacts, CalendarsWe 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&#x27;s LibraryThe User&#x27;s Library folder is hidden by default. To unhide: Select the Finder in the Dock. Under Go in the Menu bar &gt; hold down the Option key and you’ll see the Library.Finding the User Library Folderhttp://www.takecontrolbooks.com/resources/0167/site/chap11.html#FindingtheUserLi braryFolder

Dani258 · Answer

Apple Support had me reinstall El Capitan and change the password through user &amp; 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&#x27;t tried that yet.

Dani258 · Answer

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&#x27;ll try that soon, though, and will report back with the results.

barubin · Answer

Did you apply the update to 10.11.1 yet?If not, why not?If you have, did it fix any of your issues?

Dani258 · Answer

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&#x27;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&#x27;t.

Linc Davis · Answer

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?

barubin · Answer

Dani258,Thanks for the reply and explanation.Good luck getting this solved!

Dani258 · Answer

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&#x27;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&#x27;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&#x27;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&#x27;t. Probably more information than you needed or wanted to hear so I apologize for that.  Thank you for any advice you can provide.

Linc Davis · Answer

Is there any data on either of the external drives other than Time Machine backups?

Dani258 · Answer

The Lacie has my daughter&#x27;s Mac backup on it, but other than that, only my backups on both external drives.  Nothing but backups.  And as of this morning, the oldest snapshot is from last night at 10:53.

Linc Davis · Answer

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 1For this step, the title of the Console window should be All Messages. If it isn&#x27;t, select          SYSTEM LOG QUERIES ▹ All Messagesfrom the log list on the left. If you don&#x27;t see that list, select          View ▹ Show Log Listfrom the menu bar at the top of the screen.In the top right corner of the Console window, there&#x27;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&#x27;t indiscriminately dump thousands of lines from the log into this discussion.Please don&#x27;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 2In 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&#x27;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&#x27;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&#x27;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&#x27;s a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

dianeoforegon · Answer

We had the same issue with iCloud password. After resetting the password, it did work. Note: the reset was AFTER we did the clean Keychain folder.

Dani258 · Answer

Here is the link to pastebin for a finder crash from today:http://pastebin.com/v0zbFkrWHopefully, 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 AccessDate/Time:       2015-11-08 11:55:40 -0600OS Version:      Mac OS X 10.11.1 (Build 15B42)Architecture:    x86_64hReport Version:  22Command:         Keychain AccessPath:            /Applications/Utilities/Keychain Access.app/Contents/MacOS/Keychain AccessVersion:         9.0 (55171.10.2)Build Version:   59Project Name:    KeychainAccessSource Version:  55171010002000000Parent:          launchd [1]PID:             536Event:           hangDuration:        1.90s (process was unresponsive for 47 seconds before sampling)Steps:           19 (100ms sampling interval)Hardware model:  MacBookPro11,1Active cpus:     4Fan speed:       1293 rpm--------------------------------------------------Timeline format: stacks are sorted chronologicallyUse -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 PreferencesDate/Time:       2015-11-08 12:34:04 -0600OS Version:      Mac OS X 10.11.1 (Build 15B42)Architecture:    x86_64hReport Version:  22Command:         System PreferencesPath:            /Applications/System Preferences.app/Contents/MacOS/System PreferencesVersion:         14.0 (14.0)Build Version:   21Project Name:    SystemPrefsAppSource Version:  303000000000000Parent:          launchd [1]PID:             5728Event:           hangDuration:        1.90s (process was unresponsive for 22 seconds before sampling)Steps:           19 (100ms sampling interval)Hardware model:  MacBookPro11,1Active cpus:     4Fan speed:       1290 rpm--------------------------------------------------Timeline format: stacks are sorted chronologicallyUse -i and -heavy to re-report with count sorting--------------------------------------------------Heaviest stack for the main thread of the target process:  19  ??? (&lt;99396189-E53A-3A78-BC49-449236DA7CFF&gt; + 13741) [0x1107f85ad]  19  ??? (&lt;9B600863-6A16-31CB-8138-97AC8F43FBC6&gt; + 28606) [0x10cf2dfbe]  19  ??? (&lt;9B600863-6A16-31CB-8138-97AC8F43FBC6&gt; + 253224) [0x10cf64d28]  19  ??? (&lt;9B600863-6A16-31CB-8138-97AC8F43FBC6&gt; + 299461) [0x10cf701c5]  19  ??? (&lt;9B600863-6A16-31CB-8138-97AC8F43FBC6&gt; + 302486) [0x10cf70d96]  19  ??? (&lt;359FC9DB-B64C-3BC7-B9DA-401D8A5337DC&gt; + 199119) [0x10feef9cf]  19  ??? (&lt;359FC9DB-B64C-3BC7-B9DA-401D8A5337DC&gt; + 199319) [0x10feefa97]  19  ??? (&lt;359FC9DB-B64C-3BC7-B9DA-401D8A5337DC&gt; + 200021) [0x10feefd55]  19  ??? (&lt;86B26482-C917-34F2-80D8-02911B6001E0&gt; + 561096) [0x10e485fc8]  19  ??? (&lt;86B26482-C917-34F2-80D8-02911B6001E0&gt; + 563661) [0x10e4869cd]  19  ??? (&lt;86B26482-C917-34F2-80D8-02911B6001E0&gt; + 829849) [0x10e4c7999]  19  ??? (&lt;438F4595-0731-34A2-ACAD-60121A76D1FF&gt; + 89115) [0x1107b1c1b]  19  ??? (&lt;438F4595-0731-34A2-ACAD-60121A76D1FF&gt; + 9155) [0x11079e3c3]  19  ??? (&lt;438F4595-0731-34A2-ACAD-60121A76D1FF&gt; + 55541) [0x1107a98f5]  19  ??? (System Preferences + 32160) [0x10b85dda0]Canon ScannerProcess:               Canon IJ Scan Utility2 [738]Path:                  /Applications/Canon Utilities/*/Canon IJ Scan Utility2.app/Contents/MacOS/Canon IJ Scan Utility2Identifier:            jp.co.canon.ij.scanutility2Version:               2.0.0 (29)Build Info:            ScanningCanon-1~1Code Type:             X86 (Native)Parent Process:        ??? [1]Responsible:           Canon IJ Scan Utility2 [738]User ID:               501Date/Time:             2015-11-10 13:41:08.571 -0600OS Version:            Mac OS X 10.11.1 (15B42)Report Version:        11Anonymous UUID:        XXXXXXSleep/Wake UUID:       50ADB688-C0DB-4EEA-83AA-547D021D48EBTime Awake Since Boot: 3000 secondsTime Since Wake:       2800 secondsSystem Integrity Protection: enabledCrashed Thread:        0  Dispatch queue: com.apple.main-threadException Type:        EXC_BREAKPOINT (SIGTRAP)Exception Codes:       0x0000000000000002, 0x0000000000000000Exception Note:        EXC_CORPSE_NOTIFYDyld Error Message:  can&#x27;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 loadedThread 0 Crashed:: Dispatch queue: com.apple.main-thread0   dyld                          0x8fe8b085 dyld_fatal_error + 11   dyld                          0x8fe8df59 dyld::fastBindLazySymbol(ImageLoader**, unsigned long) + 1502   libdyld.dylib                 0x989dd31c dyld_stub_binder_ + 203   jp.co.canon.ij.scanutility2.UIC 0x00736d10 Wrap_Call_CSGetMainInfo(signed char const*, NSMutableString*, tagResultS*, tagCSCommonV*, short*, short*) + 854   jp.co.canon.ij.scanutility2.UIC 0x0071eb84 UC_Caddis::GetMainInfo(std::vector&lt;tagResultS, std::allocator&lt;tagResultS&gt; &gt;&amp;, std::vector&lt;tagCSCommonV, std::allocator&lt;tagCSCommonV&gt; &gt;&amp;, short*, short*) const + 685   jp.co.canon.ij.scanutility2.UIC 0x0072056a UC_LLDCaddis::Update() + 3526   jp.co.canon.ij.scanutility2.UIC 0x00725784 UC_MergeInfo::Update(unsigned long) + 8327   jp.co.canon.ij.scanutility2.UIC 0x0071f1aa UC_UIControl::Update(unsigned long) + 328   jp.co.canon.ij.scanutility2.UIC 0x00735f1b UIController_Update + 1059   jp.co.canon.ij.scanutility2   0x000351e7 UIControllInterface::Update(int, unsigned long) + 5710  jp.co.canon.ij.scanutility2   0x00037fea -[CIJSU_AppDelegate StartScanUtility:] + 49011  com.apple.Foundation          0x99b5f961 __NSFireDelayedPerform + 48912  com.apple.CoreFoundation      0x9a6e6476 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 2213  com.apple.CoreFoundation      0x9a6e5f22 __CFRunLoopDoTimer + 125014  com.apple.CoreFoundation      0x9a6e59ad __CFRunLoopDoTimers + 34915  com.apple.CoreFoundation      0x9a6dc8a1 __CFRunLoopRun + 211316  com.apple.CoreFoundation      0x9a6dbdf6 CFRunLoopRunSpecific + 39017  com.apple.CoreFoundation      0x9a6dbc5b CFRunLoopRunInMode + 12318  com.apple.HIToolbox           0x94732719 RunCurrentEventLoopInMode + 26719  com.apple.HIToolbox           0x9473251b ReceiveNextEventCommon + 50320  com.apple.HIToolbox           0x94732314 _BlockUntilNextEventMatchingListInModeWithFilter + 99Process:               securityd [79]Path:                  /usr/sbin/securitydIdentifier:            securitydVersion:               57336.10.29Code Type:             X86-64 (Native)Parent Process:        launchd [1]Responsible:           securityd [79]User ID:               0Date/Time:             2015-11-08 11:54:53.923 -0600OS Version:            Mac OS X 10.11.1 (15B42)Report Version:        11Anonymous UUID:        XXXXXSleep/Wake UUID:       2CEB1304-8D46-4B82-A709-7233EABC077ETime Awake Since Boot: 1800 secondsTime Since Wake:       540 secondsSystem Integrity Protection: enabledCrashed Thread:        0  Dispatch queue: com.apple.main-threadException Type:        EXC_BAD_ACCESS (SIGSEGV)Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000Exception Note:        EXC_CORPSE_NOTIFYVM Regions Near 0:--&gt;     __TEXT                 0000000103ae9000-0000000103bbc000 [  844K] r-x/rwx SM&#x3D;COW  /usr/sbin/securitydThread 0 Crashed:: Dispatch queue: com.apple.main-thread0   libc++abi.dylib               0x00007fff8e37eb1e __dynamic_cast + 341   securityd                     0x0000000103af63bc 0x103ae9000 + 542042   securityd                     0x0000000103af7072 0x103ae9000 + 574583   securityd                     0x0000000103af6b6d 0x103ae9000 + 56173

Linc Davis · Answer

Please read this whole message before doing anything.This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.Step 1The purpose of this step is to determine whether the problem is localized to your user account.Enable guest logins* and log in as Guest. Don&#x27;t use the Safari-only “Guest User” login created by “Find My Mac.”While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.Test while logged in as Guest. Same problem?After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.Step 2The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.Please take this step regardless of the results of Step 1.Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem.Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.Test while in safe mode. Same problem?After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.