Skip to main content

This sounds ridiculously simple, but it has worked for me in the past. Try checking and then unchecking Universal Access » Hearing » Flash the screen when an alert sound occurs -- this really sounds like that is the behavior in question, and sometimes setting it and the unsetting it resets to the desired behavior. (Note, this might be under Audio in newer versions of Mac OS.)

This basically checks that the preference file can be written to have a no then a yes and will clear up all sorts of minor issues in how apps can store preferences. The next step is to delete (or move to the desktop) the preference file for the affected application. In this case, the system stores this flash preference here:

~/Library/Preferences/com.apple.universalaccess.plist

At this point, you might need to expand to see if rebooting, trying a new user account helps isolate the issue.

This sounds ridiculously simple, but it has worked for me in the past. Try checking and then unchecking Universal Access » Hearing » Flash the screen when an alert sound occurs -- this really sounds like that is the behavior in question, and sometimes setting it and the unsetting it resets to the desired behavior.

This basically checks that the preference file can be written to have a no then a yes and will clear up all sorts of minor issues in how apps can store preferences. The next step is to delete (or move to the desktop) the preference file for the affected application. In this case, the system stores this flash preference here:

~/Library/Preferences/com.apple.universalaccess.plist

At this point, you might need to expand to see if rebooting, trying a new user account helps isolate the issue.

This sounds ridiculously simple, but it has worked for me in the past. Try checking and then unchecking Universal Access » Hearing » Flash the screen when an alert sound occurs -- this really sounds like that is the behavior in question, and sometimes setting it and the unsetting it resets to the desired behavior. (Note, this might be under Audio in newer versions of Mac OS.)

This basically checks that the preference file can be written to have a no then a yes and will clear up all sorts of minor issues in how apps can store preferences. The next step is to delete (or move to the desktop) the preference file for the affected application. In this case, the system stores this flash preference here:

~/Library/Preferences/com.apple.universalaccess.plist

At this point, you might need to expand to see if rebooting, trying a new user account helps isolate the issue.

Bounty Ended with 50 reputation awarded by bmike
added 337 characters in body
Source Link
bmike
  • 241.3k
  • 80
  • 433
  • 958

This sounds ridiculously simple, but it has worked for me in the past. Try checking and then unchecking Universal Access » Hearing » Flash the screen when an alert sound occurs -- this really sounds like that is the behavior in question, and sometimes setting it and the unsetting it resets to the desired behavior.

This basically checks that the preference file can be written to have a no then a yes and will clear up all sorts of minor issues in how apps can store preferences. The next step is to delete (or move to the desktop) the preference file for the affected application. In this case, the system stores this flash preference here:

~/Library/Preferences/com.apple.universalaccess.plist

At this point, you might need to expand to see if rebooting, trying a new user account helps isolate the issue.

This sounds ridiculously simple, but it has worked for me in the past. Try checking and then unchecking Universal Access » Hearing » Flash the screen when an alert sound occurs -- this really sounds like that is the behavior in question, and sometimes setting it and the unsetting it resets to the desired behavior.

This basically checks that the preference file can be written to have a no then a yes and will clear up all sorts of minor issues in how apps can store preferences.

This sounds ridiculously simple, but it has worked for me in the past. Try checking and then unchecking Universal Access » Hearing » Flash the screen when an alert sound occurs -- this really sounds like that is the behavior in question, and sometimes setting it and the unsetting it resets to the desired behavior.

This basically checks that the preference file can be written to have a no then a yes and will clear up all sorts of minor issues in how apps can store preferences. The next step is to delete (or move to the desktop) the preference file for the affected application. In this case, the system stores this flash preference here:

~/Library/Preferences/com.apple.universalaccess.plist

At this point, you might need to expand to see if rebooting, trying a new user account helps isolate the issue.

added 168 characters in body
Source Link
bmike
  • 241.3k
  • 80
  • 433
  • 958

This sounds ridiculously simple, but it has worked for me in the past. Try checking and then unchecking Universal Access » Hearing » Flash the screen when an alert sound occurs -- this really sounds like that is the behavior in question, and sometimes setting it and the unsetting it resets to the desired behavior.

This basically checks that the preference file can be written to have a no then a yes and will clear up all sorts of minor issues in how apps can store preferences.

This sounds ridiculously simple, but it has worked for me in the past. Try checking and then unchecking Universal Access » Hearing » Flash the screen when an alert sound occurs -- this really sounds like that is the behavior in question, and sometimes setting it and the unsetting it resets to the desired behavior.

This sounds ridiculously simple, but it has worked for me in the past. Try checking and then unchecking Universal Access » Hearing » Flash the screen when an alert sound occurs -- this really sounds like that is the behavior in question, and sometimes setting it and the unsetting it resets to the desired behavior.

This basically checks that the preference file can be written to have a no then a yes and will clear up all sorts of minor issues in how apps can store preferences.

Source Link
Daniel
  • 35.1k
  • 31
  • 155
  • 193
Loading