Cyberholmes

Q: Keychain access windows close

I recently restored my user folder, System Library, and System Applications folder from Crashplan, all with "original permissions." Now, when I open Keychain Access and try to show a password or secure note, it briefly shows the content and then the window closes immediately.

 

I am using OS X Yosemite on a 2012 MacBook Pro. Is this a permissions issue?

Macbook Pro, Mac OS X (10.4.7)

Posted on May 31, 2015 6:38 AM

Close

Q: Keychain access windows close

  • All replies
  • Helpful answers

Previous Page 2
  • by bwigs2,

    bwigs2 bwigs2 Mar 28, 2016 1:22 PM in response to LovesSleep
    Level 1 (4 points)
    Mar 28, 2016 1:22 PM in response to LovesSleep

    Yeah already have all my email accounts set up as IMAP. I tried quitting mail and then opening keychain access. same issues. also tried restarting and never opening mail. same issues still. For that matter i even tried isolating the computer with no internet access. same issues still show up. This seems like a regression defect in the keychain access application to be honest. it just showed up one day. like there is some sort of security setting internally that wants to close dormant windows, but is being triggered way to soon.

  • by JasperCram,

    JasperCram JasperCram May 19, 2016 12:43 PM in response to Cyberholmes
    Level 1 (4 points)
    Mac OS X
    May 19, 2016 12:43 PM in response to Cyberholmes

    I also got this problem out of nothing. The list view works just fine. When I double click, I see a window with details for a specific entry, but after a few seconds, it disappears (even if I don't press the "show password" checkbox). I hope somebody can help me because I have a big problem now that I cannot access my passwords.

     

    For the record, I run Mac OS X 10.11.4 (15E65)

  • by JasperCram,

    JasperCram JasperCram May 19, 2016 1:01 PM in response to JasperCram
    Level 1 (4 points)
    Mac OS X
    May 19, 2016 1:01 PM in response to JasperCram

    I just did a restart in safe mode as suggested. I could not reproduce the problem is safe mode. After the next normal restart, I could still not reproduce the problem. So it seems the safe mode restart solved my problem.

Previous Page 2