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.

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

or

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

Reply
Question marked as Top-ranking reply

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

99 replies

Apr 25, 2015 6:45 AM in response to 7heavens

Update: The problem restarted again after 1 day and continues. I couldn't find a permanent solution. I'm able to get the Mac to work for few hours by trying a combination of this solution, disk permission repair (when I can boot on Recovery mode -- doesn't work all the time). Still looking for a permanent solution. I suspect that the "Duet Display" Mac App has something to do with this, so now I quit it and not let it start by default. I will see what it does.

Apr 28, 2015 1:04 PM in response to mjoshea148

It works for me.

Updating to 10.10.3 in my Samsung monitor or in the LCD of the MBP (13-inch mid 2012) appears a flicker from time to time in a block of pixels in random places. Clicking in those places or moving a window the problem stops. I made a reset to PRAM, SMC, but without result.

In every reboot my permissions was the same:

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.

I tried a clean install of 10.10.3 and the problem not only remains when I pluged in the external monitor but also when I worked in Macbook alone.

User uploaded file User uploaded file User uploaded file

I rolled back to 10.10.2. I made a clean install from 10.10.0 to 10.10.2

Unfortunately during the installation and updates the problem with displaypolicyd was still there. I do not get why.

Finally I deleted the folder displaypolicyd.

The trouble with permissions is fixed. Everything works fine (fingers crossed)

Apr 28, 2015 2:23 PM in response to -ixen-

Same story here. the problem also persisted after a reinstall. How ??? That makes no sense As far as im concerned.

Deleted the folder and no permission issue since.

One bug remains where flash video player sometimes get croped with part of the image becoming black while the video is still playing. I have to exit fullscreen and back to fix it.

Apr 28, 2015 2:27 PM in response to mjoshea148

Yes as always. My only graphics problem was these flickering blocks of pixels.

Check the displaypolicyd.log in Console


u>101322527 /usr/libexec/displaypolicyd: Version: V1.0 starting [0]

u>101570392 /usr/libexec/displaypolicyd: Started at Sun Apr 26 19:52:52 2015

u>32863695 ERROR: unable to create path : /var/db/displaypolicyd/


I guess that the OS tries to create a file in the folder displaypolicyd but it fails.

However, I can see in my system in usr/libexec/ a file named displaypolicyd which is a Unix Executable file.

Did you also delete it?

Apr 28, 2015 4:37 PM in response to lplacencia

I guess they can just take any of their current MacBook, install there any fresh Yosemite and woila - the bug is there. Pretty sire Apple devs know about this bug, but have no time to fix it. So yeah reporting can speed up bigfix.


Don't remove displaypolicyd, it won't help, but will make more problems in future. Also fixing permissions won't help sometimes and sadly not permanent.

Apr 29, 2015 5:41 AM in response to mjoshea148

I can't tell. Probably someone who knows what these files do may say.

By the way a friend whose MBP (late 2008) updated to 10.10.3 and works perfectly said me that his system has also an empty displaypolicyd folder.

I tried this with everything unplugged just after a clean install of 10.10.2. Unplugged from external monitor I setup my mac and only at the end of the process I plugged in my Samsung monitor using an apple adapter (thunderbolt to VGA).

After all I think that 10.10.3 flashes the graphics chip with new drivers otherwise the problem with displaypolicyd permissions should not be there after a clean install of 10.10.0, 10.10.1 and 10.10.2 updates.

May 3, 2015 7:44 AM in response to lplacencia

I might be suffering from this problem as well. I have a mid-2010 iMac with an ATI video card inside and I have connected (extended desktop which I use to watch and stream videos) it to my HD Ready Sony LCD-TV via an HDMI cable and Mini Displayport adapter. I updated to 10.10.3 and then installed the supplemental update having to do with the video driver. Suddenly my iMac lost all ability to recognize my Sony. I checked all the cables and all the devices. Nothing. I ran Onyx Automation and did SMC/PRAM resets. Nothing. I then found out that this seems to be a common problem, especially to those who have older Macs with ATI video cards. Right now I'm waiting for someone to come up with fix, be it Apple and or someone with a temporary hack fix. I really don't want to do a clean install and then end up with 10.10.2 as it would take a lot of work (unfortunately I only had a SuperDuper backup where I had already installed 10.10.3) and I would like to be able to get Apple updates in the future.


A funny thing happened when I was initially tying out a possible solution someone suggested. It was suggested to me that I should cover up the 19th pin of HDMI male connector that goes into my Sony with a thin piece of tape. I did this and it did not solve anything. However, on my first try, I accidentally covered up the 2nd pin instead and when I switched my iMac on, it did recognize the Sony although I didn't get a picture.

May 11, 2015 4:47 AM in response to kenan79

I have the same permissions issue with a MacBook Pro (15-inch, Early 2011) where these following permission problems keep returning after reboot.



I also have done a full system wipe and installed Yosemite 10.10.3 and these permission issues still return. I don't use an external display, but have done in the past with a Thunderbolt adapter.



Did anyone managed a fix or the best thing to try? This couldn't be a thunderstrike issue could it?



Many thanks to anyone who can help



Group differs on “Library/Printers/InstalledPrinters.plist”; should be 80; group is 0.


Permissions differ on “Library/Printers/InstalledPrinters.plist”; should be -rw-rw-rw- ; they are -rw-r--r-- .


Repaired “Library/Printers/InstalledPrinters.plist”


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.


Repaired “private/var/db/displaypolicyd”

Permissions problem in displaypolicyd

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.