Permissions problem in displaypolicyd

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.

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.

I too have the same issue as many of you here.

I've tried to repair, reboot, delete folder etc etc.

I still get the message about private/var/db/displaypolicyd

And I too have flickering black areas on my screen.

If you have to use an external display - for example on a Mac Pro, deleting the folder will resolve nothing. I'm still stuck on a black screen - after the 10.10.3 update it is now even a permanent issue, although I can access it via screen sharing.

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.

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”

Apple engineering has requested to launch the TimingSnoop.app and submit the output information in order to further investigate this issue.

After this they sent me a new mail, "Engineering has determined that your bug report (20701735) is a duplicate of another issue (20800766) and will be closed". I suggest to submit to bug report your issues.

I have the same issues - once I boot up, I can work normally. After 1 restart however, I get this same permissions issue

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

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

Repaired "private/var/db/displaypolicyd"

When I shut down then restart the next day, the reboot stalls and I need to force shut down. If I then start up in 'safe mode' I can run the permissions verification and repair, but then I only get to restart one time until a second restart stalls midway in the boot up and I must force shut down then restart in 'safe mode'. Am I doomed to restarting in save mode everytime I use this computer? Its a Mac-Pro (Early 2008), 2 x 2.8 GHz Quad-Core Intel Xeon, 16GB Memory, Graphics card ATI Radeon HD 5770 1024 MB. I am using Dual monitors. This problem started on Aug. 12 after upgrading to Yosemite, have the latest 10.10.5 and have also erased the hard drive and did a clean install. Still this happens everytime I start the computer. Is there a permanent fix?

I asked developers in bug report if the following displaypolicyd log is normal.

u>52603393 ERROR: AGDC suppport not present in system

u>52603463 ERROR: Policy engine instance init failed

they said that "displaypolicyd log simply states system is not managed by AGDC and does not lead to any additional information about this panic report"

Did you try this? Re: Permissions problem in displaypolicyd

I am beginning to suspect this is at the heart of a few Yosemite bugs. I had a screensaver issue which appears to go away when this permission is fixed.

I have exactly the same problem as you... unfortunately I cannot leave my system 'unlocked' Its a royal PITA.

Did you ever get any other fix/feedback?

Iain.

Have the same issue with new MacBook Pro 15" retina (+discrete video). Just made clean re-install with PRAM reset of 10.10.1 and it still persist, so Apple doesn't fix it 😟

nothing changes ( every reboot - every time need to repair permissions (

Yeah I finally caved in here and wiped the partition and reinstalled. :/