-
All replies
-
Helpful answers
-
Apr 25, 2015 6:45 AM in response to zuzuthechiefby mjoshea148,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?
-
Apr 25, 2015 6:45 AM in response to 7heavensby 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 25, 2015 6:48 AM in response to mjoshea148by 7heavens,Indeed, I also started the have the problem again after 1 days, and couldn't find a solution. After some reading, I got to suspect the "Duet Display" App may be behind this, so I quit and it and not let it start by default. Will see what happens
-
Apr 25, 2015 6:48 AM in response to 7heavensby mjoshea148,FYI. I don't have duet display installed. I do have latest version of Dropbox though. Wondering if I should try uninstalling and seeing if that has any effect? Thoughts?
-
Apr 28, 2015 1:04 PM in response to mjoshea148by -ixen-,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.
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 1:55 PM in response to -ixen-by mjoshea148,Thanks for your update. Out of curiosity, if you plug in the external monitor, is it recognized? Mine wasn't after deleting that folder.
-
Apr 28, 2015 2:23 PM in response to -ixen-by w4vz,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 mjoshea148by -ixen-,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 3:45 PM in response to w4vzby -ixen-,I just had a mail from Apple Developer Support. They want to further investigate the issue and ask for a full report of my system.
So I suggest you all to report your problem to apple in bug reporter http://bugreport.apple.com
-
Apr 28, 2015 4:37 PM in response to lplacenciaby vitorg,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 mjoshea148by -ixen-,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 1, 2015 1:46 AM in response to -ixen-by Johsam,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.
-
May 1, 2015 12:00 PM in response to zuzuthechiefby Carlifornia,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.
-
May 3, 2015 7:44 AM in response to lplacenciaby Tigerman82,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.



