-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After Jamf install, system idling to sleep causes complete logout #39
Comments
(Tweaked the issue title slightly to make it more clear what's happening.) FWIW, I am not experiencing this, and hadn't heard of this yet, so I assume it's unexpected behavior. It's definitely un-ideal behavior, and I think should be treated as a bug. |
Every time I wake my system up from sleep I have to restart my dev environment and it's wicked frustrating. This happens probably 10 times a day. Are y'all actively working on problems like this, or should I dive in and try to figure it out myself? |
I also have this issue, sporadically. |
After six months of this, I went to System Preferences ->Security & Privacy -> Advanced and unchecked "Log out after ___ minutes of inactivity." I have no idea if that selection violates some kind of privacy, but this is no way to work. |
That may resolve the issue for you personally, but I want to keep this open as an unresolved ticket for Mac laptop management at GSA. @waldoj I don't know if you were ever asked to submit this as a ticket to GSA IT, but if you haven't yet, would you mind copy/pasting the text of the issue body (not the comments), and a link to this URL, into an email to It should take just a few seconds, and if you share your ticket number here when you're done, I'll escalate this during our next call. |
Now that I have Jamf installed, when my system idles to sleep after the mandatory 10 minutes, I am logged out entirely. Waking up my system requires logging in (i.e., typing in my both username and password), reopening all programs, Chrome reloading all tab contents from remote servers, etc. I assumed that this was an intended behavior, but @konklone requested that I file a ticket here.
To reproduce this:
The text was updated successfully, but these errors were encountered: