-
All replies
-
Helpful answers
-
Mar 31, 2015 2:47 PM in response to brandonfishermanby w4vz,brandonfisherman wrote:
I had the same problem yesterday on a 2014 Retina Macbook Pro: black screen on boot (boot progress bar would move to about 25% and then I would get the black screen), permissions problem in displaypolicyd even after repairing permissions multiple times, I even reinstalled Yosemite on top of my current system, but nothing helped.
Then I called Apple Care and they gave me the following procedure:
- Boot in single-user mode (cmd+S at boot)
- At the prompt, type the following commands:
mount -uw /
(press the return key)
cd /Library/Preferences
(press the return key)
mv com.apple.loginwindow.plist com.apple.loginwindow.plist.old
(press the return key)
reboot
(press the return key)
Voilà. If all goes well, your computer should reboot and take you to the login window. The problem seems to come from a corrupted com.apple.loginwindow.plist preference file. The above procedure will help you create a new one the next time your computer starts up.
Hope it helps someone!
Did this solve your display policy d permission issue by any chance ? Im desperate to fix it because I have a few "minor" display issues which Im sure are related to it.
Thank you
-
Apr 4, 2015 5:28 PM in response to brandonfishermanby MyMChic,Thanks for your comment I could resolve very quickly the same problem as you described it. I spent half an hour with the support of Apple and unco I could detect the problem was in private / var / db / displaypolicyd, never repaired mode repair permissions.
I found his comment did his footsteps and the solution was then instant restart. Thank You So Much!
-
Apr 4, 2015 10:20 PM in response to lplacenciaby BAthompsonite,Use the Go To Folder feature in the finder to navigate to private/var/db/displaypolicyd. Delete the folder named displaypolicyd, which should be empty. It was empty on my computer. Go to your disk utility and verify the disk permissions. It should no longer pop up in the results. Reboot your computer and then run the verify disk permissions in the disk utility again just to make sure it is still not there. I did this last night and now my MacBook Pro wakes just fine from sleep mode, it restarts just fine, it shuts down just fine and hasn't randomly blacked out since last night. I'm running a Late 2011 15-inch MacBook Pro.
-
Apr 5, 2015 12:13 AM in response to BAthompsoniteby zuzuthechief,This has helped me, but doesn't work by typing private/var/db/displaypolicyd in Finder > Go > Go to folder.
I followed this steps to show hidden files in OS X Yosemite and the navigated to "Disk name">private>var>db>displaypolicyd (an empty folder?! strange) and sent it to trash.
-
Apr 5, 2015 12:39 AM in response to zuzuthechiefby BAthompsonite,Did you put a forward slash before private, because if not that's why it didn't work in the go to function of the finder. Sorry i forgot to mention that part. Glad you were still able to use the fix though.
-
Apr 5, 2015 8:21 AM in response to BAthompsoniteby w4vz,BAthompsonite wrote:
Use the Go To Folder feature in the finder to navigate to private/var/db/displaypolicyd. Delete the folder named displaypolicyd, which should be empty. It was empty on my computer. Go to your disk utility and verify the disk permissions. It should no longer pop up in the results. Reboot your computer and then run the verify disk permissions in the disk utility again just to make sure it is still not there. I did this last night and now my MacBook Pro wakes just fine from sleep mode, it restarts just fine, it shuts down just fine and hasn't randomly blacked out since last night. I'm running a Late 2011 15-inch MacBook Pro.
That did it for me but the folder cannot be found now: OS X did not recreate it. I hope that won't affect any stability. wait & see
-
Apr 5, 2015 8:43 AM in response to w4vzby BAthompsonite,I personally don't want OS X to recreate that folder. It appears to have been the root of all the evils that prevented me from consistently using my Macbook Pro for at least an entire month. I couldn't get anything done. I even bought an SSD when the problem first started (which I don't regret at all because my Macbook is fast as **** now) because I thought my hard drive was failing. As of right now I feel like the nightmare is over but we shall see.
-
Apr 20, 2015 3:32 AM in response to brandonfishermanby 7heavens,I had the same problem since now few days on my MacBook 15" Mid-2011 on Yosemite 10.10.3. I was able to get it to work again by repairing file permission and disk but then the problem was appearing again and I noticed that displaypolicyd file was always the one to be repaired. Searching using that term took to this discussion.
I have just tried the solution proposed by brandonfishreman and it works for the moment. Thanks Brandon.
-
Apr 23, 2015 5:04 AM in response to BAthompsoniteby mjoshea148,Just an FYI - tried this solution to resolve external monitor issues related to this thread. My folder had one file inside - displaypolicyd.cache. After restart, the 2015 MBP wouldn't recognize the monitor at all, even after restarts and reset of PRAM. So, restoring the file resolved that issue but overall issue remains. On to next possible solution.
-
Apr 25, 2015 5:44 AM in response to 7heavensby mjoshea148,I also tried this solution. No issue on day 1. On day 2, same kernel panic...displaypolicyd.
-
Apr 25, 2015 5:47 AM in response to mjoshea148by zuzuthechief,You had this problem on the early 2015, 13" macbook pro?
-
Apr 25, 2015 5:51 AM in response to zuzuthechiefby mjoshea148,Yes. The new model with the force touch touchpad. Only since the 10.10.3 update.
-
Apr 25, 2015 5:57 AM in response to mjoshea148by zuzuthechief,I am having the same model delivered next week....
Since April the 5th, when I deleted that folder I haven't had the problem on my mid 2012, non-retina 15" macbook pro.
-
Apr 25, 2015 6:02 AM in response to zuzuthechiefby mjoshea148,I tried that first. After deleting it, my MBP wouldn't recognize the external monitor at all, until I restored the folder. In my case it wasn't empty, it had one file called displaypolicyd.cache inside of it. So, unless there's a way to allow it to recognize external monitors after that step, I'm stuck.
-
