You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

lplacencia Author

Level 1

2 points

Permissions problem in displaypolicyd

I'm having a very strange problem with Yosemite 10.10 (14A389) on my MacBook Pro (13-inch, Mid 2009). Waking from sleep the monitor receives no signal.

The only problems I have come across is a few permission errors:

User differs on private/var/db/displaypolicyd; should be 0; user is 244.

Group differs on private/var/db/displaypolicyd; should be 0; group is 244.

sudo chown -R root /private/var/db/displaypolicyd && sudo chgrp -R wheel /private/var/db/displaypolicyd

sudo diskutil repairPermissions /

After repairing permissions problem reappears after a reboot.

MacBook Pro (13-inch Mid 2009), OS X Yosemite (10.10)

Posted on Oct 23, 2014 2:39 PM

Top-ranking reply

lplacencia Author

Level 1

2 points

Posted on Oct 24, 2014 4:41 AM

My temporary solution

1 - Create a shell script example: fixesPermissions.sh

sudo chown -R root /private/var/db/displaypolicyd && sudo chgrp -R wheel /private/var/db/displaypolicyd

2 - Path in my case

/etc

3 - Allow my user to run the script without root password

sudo nano /etc/sudoers

below the line

# Samples

# %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom

# %users localhost=/sbin/shutdown -h now

add line

myuser ALL=NOPASSWD: /etc/fixesPermissions.sh

key cmd + x

key y

key cmd + m

4 - Run the shell script when my user logs

sudo defaults write com.apple.loginwindow LoginHook /etc/fixesPermissions.sh

View in context

99 replies

MyMChic

Level 1

0 points

Apr 4, 2015 5:28 PM in response to brandonfisherman

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 lplacencia

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 BAthompsonite

This has helped me, but doesn't work by typing private/var/db/displaypolicyd in Finder > Go > Go to folder.

I followedthis 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 zuzuthechief

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.

w4vz

Level 1

0 points

Apr 5, 2015 8:21 AM in response to BAthompsonite

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 w4vz

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.

7heavens

Level 1

5 points

Apr 20, 2015 3:32 AM in response to brandonfisherman

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 BAthompsonite

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 7heavens

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 mjoshea148

You had this problem on the early 2015, 13" macbook pro?

Apr 25, 2015 5:51 AM in response to zuzuthechief

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 mjoshea148

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 zuzuthechief

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.

Apr 25, 2015 6:27 AM in response to mjoshea148

I don't have an external display to test this out, but I had problems with my internal display and messages in Disk Utility after verifying the permissions.

Since deleting that folder I haven't had any problems.

Apr 25, 2015 6:45 AM in response to zuzuthechief

I don't have the problem when the external monitor isn't connected. Everything works fine. So my previous 'solution' was to ditch the external monitor. Anyone have any positive experiences with external monitors after deleting the Displaypolicyd folder?

Permissions problem in displaypolicyd