Keychain causing slow shutdowns

Discussion in 'OS X Mavericks (10.9)' started by Alfieg, Dec 23, 2013.

  1. Alfieg macrumors member

    Joined:
    Feb 5, 2011
    #1
    Hi all,

    Since owning my macbook pro-retina I've had a very annoying problem with slow shutdowns. When shutting down, it goes to a grey screen with cursor for 30 seconds or more. Annoying as I bootcamp a fair bit. Even without third party software installed it was happening and even on a fresh install of mavericks. It's also something to do with the login keychain I think as it happens with or without iCloud keychain enabled.

    I stumbled upon a fix, whereby resetting my default keychain reduced my shutdowns to about 1 second. Great! Then it started happening again. Not so great!

    It turns out, it's either game centre or my wifi password. So without resetting my keychain, I can remove the game centre application password or sometimes the wireless password from the keychain and back to 1 second shutdowns.

    Question is....why? This is clearly a bug and it's driving me mad. Has anyone got any ideas? When it's happening I something like this in the logs:

    23/12/2013 12:54:31.193 WindowServer[1145]: CGXGetConnectionProperty: Invalid connection 46083
    23/12/2013 12:54:31.193 WindowServer[1145]: CGXGetConnectionProperty: Invalid connection 46083
    23/12/2013 12:54:31.193 WindowServer[1145]: CGXGetConnectionProperty: Invalid connection 46083
    23/12/2013 12:54:31.193 WindowServer[1145]: CGXGetConnectionProperty: Invalid connection 46083
    23/12/2013 12:54:31.193 WindowServer[1145]: CGXGetConnectionProperty: Invalid connection 46083
    23/12/2013 12:54:31.194 WindowServer[1145]: CGXGetConnectionProperty: Invalid connection 46083
    23/12/2013 12:54:31.194 WindowServer[1145]: CGXGetConnectionProperty: Invalid connection 46083
    23/12/2013 12:54:31.194 WindowServer[1145]: CGXGetConnectionProperty: Invalid connection 46083
    23/12/2013 12:54:31.194 WindowServer[1145]: CGXGetConnectionProperty: Invalid connection 46083
    23/12/2013 12:54:57.488 WindowServer[1264]: CGXGetConnectionProperty: Invalid connection 46603
    23/12/2013 12:54:57.488 WindowServer[1264]: CGXGetConnectionProperty: Invalid connection 46603
    23/12/2013 12:54:57.488 WindowServer[1264]: CGXGetConnectionProperty: Invalid connection 46603
    23/12/2013 12:54:57.488 WindowServer[1264]: CGXGetConnectionProperty: Invalid connection 46603
    23/12/2013 12:54:57.488 WindowServer[1264]: CGXGetConnectionProperty: Invalid connection 46603
    23/12/2013 12:54:57.489 WindowServer[1264]: CGXGetConnectionProperty: Invalid connection 46603
    23/12/2013 12:54:57.489 WindowServer[1264]: CGXGetConnectionProperty: Invalid connection 46603
    23/12/2013 12:54:57.489 WindowServer[1264]: CGXGetConnectionProperty: Invalid connection 46603
    23/12/2013 12:54:57.489 WindowServer[1264]: CGXGetConnectionProperty: Invalid connection 46603

    In the case above, deleting my game centre password token from my key chain fixed it. Similar logs when it's my wi-fi password.

    From browsing forums, it appears this problem has been around since mountain lion, so is there any hope of a fix from apple?

    Thanks in advance for any help.
     
  2. LV426 macrumors 6502a

    Joined:
    Jan 22, 2013
    #2
    You will probably need to contact Apple to find out exactly what "Invalid connection 46083" means. A quick search of the support site lists an archived page with error codes going back a few years, but doesn't mention 46083.

    There might be more to this than meets the eye. It's not necessarily a bug.

    Thanks for not posting APPLE YOU NEED TO FIX THIS.
     
  3. Alfieg thread starter macrumors member

    Joined:
    Feb 5, 2011
    #3
    Thanks. When you say contact apple, what would you suggest as the most sensible method? It doesn't seem I am allowed to email them in the UK anymore and I don't have a developer login to report a bug. I suspect if I get someone on the phone I'd be wasting my time.

    Cheers.
     
  4. LV426 macrumors 6502a

    Joined:
    Jan 22, 2013
    #4
    Unless you have AppleCare, it's probably going to cost you.

    Although you speak to someone on the phone, if it's anything like Apple Care, things get followed up with email correspondence. I doubt it would be a waste of your time. At the very least you could expect a full description of what the error code means, exactly.
     

Share This Page