-
All replies
-
Helpful answers
-
Oct 24, 2014 4:41 AM in response to lplacenciaby lplacencia,★HelpfulMy 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
-
Oct 25, 2014 9:47 PM in response to lplacenciaby Scott Lahteine,I just found this same permissions issue and repaired them with Disk Utility. I'm hopeful that this will fix the issue I've been having with my HDMI monitor failing to activate when connecting through a MDP-to-HDMI adapter cable. I'm not at home now to test it but I will post results as soon as I can. I'm not the only one having this problem, so let's hope it's as simple as this!
-
Oct 31, 2014 9:58 AM in response to lplacenciaby dr_click,I had a similar issue where my MacBook Pro would freeze after entering the password on a lock screen. The problem happened only when using a lock screen; if I did not use a lock screen (System Preferences->Security->General->"Require password..." unticked), then my Pro would come back from sleep without issue. Using Disk Utility to fix permissions in /private/var/db/displaypolicyd appears to fix the problem, but the permissions require fixing after each reboot, it seems.
-
Nov 3, 2014 9:34 PM in response to lplacenciaby SungMatt,Did the fix, added the 5 lines to the file, but it's giving an error saying syntax is wrong (something similar to that, my computer likes to crash every 2 minutes before)
Am I doing the fix properly?
Thanks,
Matt.
-
Nov 4, 2014 10:08 AM in response to SungMattby SungMatt,I have gotten it to work, hope this doesn't happen again, cos' its really troublesome. Read key as a command and stuck it in sudoers, yikes. Had to modify permissions on each of the files to get it to open without sudo.
However, it seems like the shell file is wiped every time the system boots up, why is that so?
-
Nov 4, 2014 2:38 PM in response to lplacenciaby Scott Lahteine,This didn't seem to help my HDMI connectivity problem. But I didn't restart after the permissions repair, nor install the script. I just applied the fix then tried connecting the display, whereupon it still failed to start. Is the script and restart absolutely necessary, or does the permission repair fix the issue even after the system has booted?
-
Nov 5, 2014 8:57 AM in response to lplacenciaby Oujmik,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.
-
Nov 13, 2014 9:24 AM in response to lplacenciaby wiherek,There seem to be three solutions:
- correct permissions
- download thunderbolt firmware update (1.2) from appStore
- reset PRAM + unplug then replug the monitor cable from the adapter (I have dvi -> thunderbolt)
so for me the last one worked, and now I have two external displays on Yosemite working ok. I did all three of them though, so perhaps the combination worked.
-
Nov 14, 2014 4:31 AM in response to dr_clickby Iain Devine,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.
-
Nov 14, 2014 4:35 PM in response to Iain Devineby dr_click,Gah. Tried the "repair permissions" utility with no joy. I can't leave my computer locked when connected to a Thunderbolt display. I can leave the computer locked when connected to a Mini DisplayPort LED display, which is better.
My Thunderbolt display firmware was already up to date, and so did not need the recent 1.2 update. So whatever the problem is, it's not the firmware.
-
Nov 14, 2014 9:50 PM in response to dr_clickby larisa pedroncell,i am having the same issue with the permission and it seems like a part of several bugs in the discussions that i am following. still haven't found a way to make it stick and now i can only boot up in safe mode.
hoping to find a fix as i don't want to go through a clean install only to have it be a yosemite bug and happen again.
-
Nov 18, 2014 11:51 AM in response to lplacenciaby chevysales,have same issue originally it was just:
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” but found on MacRumors Forum the fix for it which was getting printer plist in library and unlocking it. reboot and haven't had it again
This is on a late 2013 15" rMBP 16gbs ram and 2.6 with nvidia 750GT and 512SSD with external Lacie 1TB for Time Machine. No external monitor as have a 27" NEC for my photo work on my windows box which was a Puget System Build to my specs last year before I decided to leave the all plastic side of computing . To me I'll continue searching as the lines don't help me. Will post back anything I find.
about a month or more back the same error in Disk Utility started showing up. Lappy came with Mavericks 10.9.1 on it was picked up the day before Xmas (great time to be in Apple Store with 2 daughters that have Teachers Discount....free AppleCare for 3 years with discount).
Anyhow sure would like fix as have updated each time one came out. on Yosemite 10.10.1 know I did the .1 last night. Have had no issues at all except for learning the mac world coming from Windows and still have to use BootCamp and Windows 7 pro 64 bit for 1 program we need for General Motors. Have been with iPhones since the 3GS and loving my 6Plus but like fixing any registry issues in Windows I like a clean machine so will try whats needed to fix this permissions issue.
Thank you
-
Nov 19, 2014 2:16 AM in response to chevysalesby vitorg,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
-
Nov 22, 2014 10:04 AM in response to lplacenciaby zuzuthechief,I'm having the same problem on a MacBook Pro (15-inch, Mid 2012)+ discrete graphics, closed the clamshell and the next day to my surprise the display didn't turn on after I opened the mac. Did a Permission check & repair and I reported it to apple at bugreport.apple.com
