Skip to content
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

Prompted for password after sleep/wake/unlocking. #14

Closed
VioletPixel opened this issue Aug 30, 2015 · 5 comments
Closed

Prompted for password after sleep/wake/unlocking. #14

VioletPixel opened this issue Aug 30, 2015 · 5 comments
Labels

Comments

@VioletPixel
Copy link

Every time my Mac sleeps and is woken up I'm prompted to enter my administrator credentials for Turbo Boost Switcher. Because the Turbo Boost Switcher process is constantly running I would only expect to have to do this when it's initially launched.

I have a MacBook Pro (Retina, 15-inch, Mid 2014) running 10.10.5, although this issue existed on previous versions of Yosemite as well.

@VioletPixel
Copy link
Author

Here's what happens in Console when I close the lid, open it, unlock, and enter the password to authorize Turbo Boost Switcher:

8/30/15 1:01:12.348 PM Turbo Boost Switcher[1006]: kextstat output:   157    0 0xffffff7f82f41000 0x2000     0x2000     com.rugarciap.DisableTurboBoost (0.0.1) <7 5 4 1>
8/30/15 1:01:39.000 PM kernel[0]: Re-enabled Turbo Boost: 4000850089 -> 850089
8/30/15 1:01:40.000 PM kernel[0]: Disabled Turbo Boost: 850089 -> 4000850089
8/30/15 1:01:40.491 PM Turbo Boost Switcher[1006]: kextstat output:   162    0 0xffffff7f82f41000 0x2000     0x2000     com.rugarciap.DisableTurboBoost (0.0.1) <7 5 4 1>

@kmarekspartz
Copy link

I've got the same issue. This also seems to be indirectly asked for in #12.

@vikbez
Copy link

vikbez commented Sep 8, 2015

That would be perfect if this wasn't needed.
(same issue in 10.9.4)

@StephanOnTour
Copy link

try this:
#4

@rugarciap
Copy link
Owner

Turbo Boost Switcher installs a kernel extension and that operation needs to be done by an admin user (or root) in order to do that. The user you choose to run the app must be also capable of gaining root permissions (sudoers list) in order to change file permissions, since apple forces the kext file to be owned by the user root.

This is not an issue, is just a requirement and a security configuration Apple forces. Review your user permissions and if all is fine then the app won't ask the root password more than once per session.

Best!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants