Safari 3.1: uninstalling and going back to 3.0.4, more

Uninstalling and going back to 3.0.4 Safari 3.1 is causing such serious issues for some users that many are choosing to revert to Safari 3.0.4 rather than continue to use the current version. Take MacFixIt reader Debbie for instance:

"Since updating to Safari 3.1 I am experiencing unexpected quits, hanging, pages not loading and very slow response in most other applications, too."

Unfortunately, downgrading isn't an easy process. The Safari installer modifies a number of files other than the Safari application itself, including WebKit and more. As such, there are two viable options:

Follow our tutorial for reinstalling the system, then upgrade to either Mac OS X 10.5.2 or Mac OS X 10.4.11 and apply all recommended updates, but refrain from installing Safari 3.1.

Download Pacifist and either the Mac OS X 10.4.11 or Mac OS X 10.5.2 combo updater (if you run Tiger or Leopard, respectively) -- available from Apple's download page. After installing Pacifist, drag the appropriate combo package updater onto the Pacifist icon and select /Applications/Safari.app from the list. Use the "Install" button at the top of the Pacifist window to force an installation of Safari. Next, select /System/Library/Frameworks/WebKit.framework and install it in the same manner. Restart your Mac.

The latter method is quicker but more prone to potential issues.

Repair permissions for various issues A number of issues apparent after installation of Safari 3.1 can be solved with a simple permissions repair, which can be performed with Disk Utility (located in /Applications/Utilities.)

MacFixIt reader Jeff writes:

"I have had many problems with the latest update of safari and after reinstalling the standalone update and trying your suggested fixes the app kept crashing my mac. Not only would safari 3.1 crash but the whole system would crash, sometimes even as a kernel panic. Finally i decided to verify permissions and repair. Verify found many problems with the flash player plugin. I repaired and now no problems, for now anyway."

Check DNS settings Several users have reported that DNS settings were mysteriously changed after applying the Safari 3.1 update. MacFixIt reader Russ Crum writes:

"I have encountered a serious slow down issue on two of three systems that have had Safari 3.1 installed.  On both portables (a one year old MacBook and a three year old iBook) serious internet slow downs were experienced after the install and reboot. The problem was traced to a set of DNS addresses that were somehow placed in the system preferences (64.79.64.4 and .5) on both systems. Both systems are at 10.4.11 and both operating to Airport Express base stations. Removing the DNS entries completely solved the slow down problems. Previously neither system had had a manually entered DNS address. The third system, a 24" IMac, did not have these DNS address put in during the Safari install. That system is also running 10.4.11 but was not operating via Airport at the time of the Safari install."

See our previous article on entering DNS settings for further coverage.

Secure site issues -- change cookie settings If you're experiencing problems with secure sites after the Safari update, try modifying your cookie settings. MacFixIt reader Kit experienced success with changing the cookie setting to "Always Accept." You can toggle this setting by going to Safari > Preferences > Security.

Kit writes:

"With Safari 3.1 & TD*Ameritrade I can't place trades unless I set cookies at 'always accept' as opposed to my normal setting of 'only sites you navigate to'. I though 3.1 was supposed to more secure. This seems like a step backwards."

Feedback? Late-breakers@macfixit.com.

Previous coverage:

• Sync issues after Safari 3.1 (.Mac, iPhone/iPod, etc.)
• Widgets can cause system slowdown, crashes after Safari 3.1
• Safari 3.1: Problems running Java applets -- fix; Exorbitant processor usage
• Safari 3.1: Google Reader/Gmail problems; PithHelmet fix; Secure site issues; more
• Troubleshooting Safari 3.1: Crashes, won't load pages, utilities broken

Resources