Greyed out preference panes

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
I have 3 panes in System Preferences that are greyed out, and can't seem to figure out how to get access to them. There's Flip4Mac, Growl, and MacFUSE.

After installing growl and opening System Preferences I get something about not being able to access the preferences pane: "To see this preferences pane, you may need to connect a device to your computer." I'm not sure which device it thinks it needs.

Hovering over the 3 panes I can't access I see: "Your access to this preference has been restricted." That also doesn't make sense since I've got an administrator account.

I've tried changing the owner/group of /Library/PreferencePanes/Growl, but that doesn't help. I've tried using the disk utility to fix permissions, but that doesn't help.

Any other ideas?
 

TheStu

Moderator<br>Mobile Devices & Gadgets
Moderator
Sep 15, 2004
12,089
45
91
What OS are you on? When did they become greyed out?
 

TheStu

Moderator<br>Mobile Devices & Gadgets
Moderator
Sep 15, 2004
12,089
45
91
Can you right click on them and remove them? If yes, try that and then try re-installing them.

If they are still greyed out, try it again, but this time, under a new Admin user account.

Are any other third party Pref Panes greyed out?
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
Can you right click on them and remove them? If yes, try that and then try re-installing them.

If they are still greyed out, try it again, but this time, under a new Admin user account.

Are any other third party Pref Panes greyed out?

The option to remove them is also greyed out. I've tried using the uninstall scripts for Growl, but on re-install it's still greyed out.

I'll try with another account a bit later. Thanks for the idea.
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
This ended up being some setting on the ldap side. It's fixed now. Thanks for the help!
 

lottscarson

Junior Member
Jun 7, 2012
1
0
0
This ended up being some setting on the ldap side. It's fixed now. Thanks for the help!

Hey n0cmonkey - I realize that it's been a few years since the original post, but do you happen to remember which LDAP setting was responsible for this?