![insomniax for mac disable lid sleep not working sierra insomniax for mac disable lid sleep not working sierra](https://venturebeat.com/wp-content/uploads/2018/01/arkit-breakdown.png)
Your problem must be something in one of these locations. A manageably small list of things is disabled during a Safe Mode startup, including /System/Library/Extensions, /Library/StartupItems, and notably, any fonts outside of /System/Library/Fonts. Your experiments so far suggest that whatever is causing the problem is in your /Library directory, and not in your User folder. Good news is that this should be straightforward to fix.
![insomniax for mac disable lid sleep not working sierra insomniax for mac disable lid sleep not working sierra](https://sportsclinictampico.com/wp-content/uploads/2021/04/how-keep-your-43505C.jpg)
That strongly suggests the problem is something you're loading at startup. I gather that booting in Safe Mode solves the problem, but creating a new user doesn't. I hope your problem is more straightforward than that! Do that by creating a new, pristine user account and using that to see if the problem persists.Ī genuine "clean install" of Lion is still a debated procedure, but some people who exhaust all other diagnostic possibilities have ended up going that route with good success. It also might help to generate ideas if you can determine if the problem is system-wide or user-specific.
![insomniax for mac disable lid sleep not working sierra insomniax for mac disable lid sleep not working sierra](https://venturebeat.com/wp-content/uploads/2017/12/uspresidentssiri.jpg)
Permissions errors have caused a wide range of bizarre problems in the Lion upgrade. It's worth repairing your permissions, if you haven't already done that.
INSOMNIAX FOR MAC DISABLE LID SLEEP NOT WORKING SIERRA INSTALL
User level processes can not block sleep when instigated by the user.ĭo you have any utilities installed that install kernel extensions (kext)? These might include screen recording or audio capture tools utilities than need low level access to your Mac. The behaviour you are seeing suggests a kernel extension or IOKit problem. However, processes should be forced asleep after 30 seconds on lid close. Applications and other processes can keep your Mac awake if they are providing a service, such as file sharing or remote access. Look out for applications that may be keeping your Mac awake and active. Message: PMConnection AirPort configd plug-in .slowresponse 1399 ms You will see a list of entries in form: * Domain: applicationresponse.slowresponse Use the following Terminal command to view a detailed log showing your Mac's power history: pmset -g log The sleep mechanism has started but never completes. A lack of wake reason entries suggests your Mac is never fully sleeping.