-
All replies
-
Helpful answers
-
May 11, 2015 4:47 AM in response to kenan79by flow2015,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”
-
May 11, 2015 5:08 AM in response to -ixen-by -ixen-,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.
-
May 11, 2015 8:22 AM in response to -ixen-by flow2015,What? TimingSnoop is not even developed by apple?
-
Jun 1, 2015 12:22 PM in response to mjoshea148by 7heavens,I finally got it solved (my problem sudden computer shutdowns, and horizontal lines on screen, with computer something not accepting to restart... saw that displaypolicyd permissions was always faulty as I was trying to troubleshoot).
It was actually a hardware problem: faulty video card covered by Apple recall: https://www.apple.com/sa/support/macbookpro-videoissues/
My computer is a MacBook Pro 15" Early 2011.
I got my computer to Apple's authorized distributor who replaced the motherboard for no charge (it took them 2 weeks ). I now it work fine.
I hope this helps.
-
Jul 2, 2015 1:11 AM in response to lplacenciaby -ixen-,Anyone still having this problem after the 10.10.4 update?
-
Jul 2, 2015 4:18 AM in response to -ixen-by chevysales,yes I see it when i went to check permissions after update. still there. no external monitor either being used. late 2013 15" rMBP loaded with 750GT
-
Jul 30, 2015 9:53 PM in response to lplacenciaby Just me 23,I Have absolutely no clue what any of your directions mean. starting with the first five words. Can you simplify please for ordinary people?
thank you
N
-
Aug 24, 2015 4:25 PM in response to -ixen-by idtstudio,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?
-
Dec 23, 2015 12:39 AM in response to idtstudioby -ixen-,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"
-