Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I have a new MacBook Air set up with FileVault.

In the Security Preference pane I have "Require password 1 hour after sleep or screen saver begins" enabled, but the "Logout after 60 minutes of inactivity" is disabled.

When I leave the computer on overnight I manually lock the screen (from the Keychain status menu bar, which I enabled via the Keychain Access preferences).

Alas, in the morning I find that instead of a locked screen I see the login window, after my user was logged out with all applications terminated... (e.g. Firefox thinks it previously crashed when I launch it).

This type of behavior only started after I enabled FileVault.

Why is this happening? How do I prevent such auto-logout?

share|improve this question
1  
Something interesting in /Applications/Utilities/Console.app? Any error messages through the night? Did this problem appear repeatedly, or only once, maybe twice? –  Daniel Beck Jan 8 '11 at 13:26
    
@Daniel - since I need to leave some processes running continuously –  MBA_fv Jan 8 '11 at 17:22
    
@Daniel - nothing interesting in console log. –  MBA_fv Jan 8 '11 at 17:26
    
Thanks, your question actually answered mine. –  Andy Dec 7 '11 at 17:38

2 Answers 2

I had the same issue but it was because "Logout after 60 minutes of inactivity" checkbox was enabled.

share|improve this answer

I've experienced a similar issue. My MacBook Pro was actually rebooting itself during the night, so in the morning, I found it displaying the login screen instead of where I left it in the afternoon (converting a TV recording from my DVR).

You can check when your MacBook was rebooted the last time. To do so, open Terminal.app and enter

uptime

The command will output something like this:

 9:44  up 1 day, 14:19, 1 user, load averages: 0.38 0.29 0.32

This displays the current time (9:44) and how long ago the machine was rebooted the last time (1 day, 14 hours, and 19 minutes ago).

This won't exactly solve your problem but help you to find or eliminate a particular root cause (the reboot).

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.