Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Safari 2.0.1

Object-X said:
Now Safari doesn't work. :mad: Apple's site won't let me download the browser so now I'm screwed. How can I get the old Safari back? This update corrupted my browser. Beware!
Click to expand...
Have you got any third party plugins installed?

It seems others have downloaded the update and it is working fine. Issue is most likely to be with your machine.
 
liketom said:
...another reboot needed
Click to expand...

Somebody has to ask, so it might as well be me: Why should upgrading a web browser require a reboot? This would make sense if shared system components such as WebKit were being upgraded, but then it would be inaccurate to describe this as a Safari update, wouldn't it?
 
munkle said:
Have you got any third party plugins installed?

It seems others have downloaded the update and it is working fine. Issue is most likely to be with your machine.
Click to expand...

Nope, just the stock browser. Not even my backup works. When I install it I get the same file corrupted error. I don't want to have to pay for support because an update killed my system. Anyone have a suggestion?
 
So much for the "application stability"

It still crashes when using search.earthlink.net and before anybody says that it doesn't you have to search a couple of times
 
Object-X said:
Nope, just the stock browser. Not even my backup works. When I install it I get the same file corrupted error. I don't want to have to pay for support because an update killed my system. Anyone have a suggestion?
Click to expand...

Use Pacifist and reinstall Safari.
 
antirealist said:
Somebody has to ask, so it might as well be me: Why should upgrading a web browser require a reboot? This would make sense if shared system components such as WebKit were being upgraded, but then it would be inaccurate to describe this as a Safari update, wouldn't it?
Click to expand...
Since the update (1) doesn't fix the Image of Doom and (2) is VERY vaguely worded, my guess would be that what was fixed is a component (or components) that Safari uses, but which is/are not part of Safari.

Quite often, the modus operandi when releasing such updates, especially if they address a particularly heinous problem that isn't public information, is to tell a little white lie about what's being fixed.
 
Update worked fine for me, was available in SU the moment this thread was created. Installed, rebooted, works fine, now I can continue to not use it whatsoever.

Long live Firefox... :D
 
It's all WebKit

antirealist said:
Somebody has to ask, so it might as well be me: Why should upgrading a web browser require a reboot? This would make sense if shared system components such as WebKit were being upgraded, but then it would be inaccurate to describe this as a Safari update, wouldn't it?
Click to expand...

It probably does change WebKit and thus the required restart. The non tech savvy people don't know or care what WebKit is or that it even exists so calling the update WebKit might confuse, scare, upset or confound them.
 
Safari's hunger for memory knows no bounds

For what it's worth, Safari still eats more of my memory than anything else. Except maybe Dashboard with 25 widgets running.
 
clayj said:
Quite often, the modus operandi when releasing such updates, especially if they address a particularly heinous problem that isn't public information, is to tell a little white lie about what's being fixed.
Click to expand...
It's a bug fix for something that should not have been released. They'll word it with euphemisms such as "improves compatibility" or "general maintenance release" or some other phrase. It's part of Apple lingo. It's part of the RDF™.
 
makeme said:
It probably does change WebKit and thus the required restart.
Click to expand...

But isn't this the sort of thing that got Microsoft into trouble with IE and its entanglement with the rest of the OS? Suppose I'm a committed Firefox user and I want to remove Safari from my system. I can do that and retain other apps which use WebKit, like Mail. But then I'm not going to be installing Safari updates, which may fix WebKit bugs. Updating WebKit through Safari makes it necessary to keep Safari around and current, even if I don't want it.
 
Lacero said:
It's a bug fix for something that should not have been released. They'll word it with euphemisms such as "improves compatibility" or "general maintenance release" or some other phrase. It's part of Apple lingo. It's part of the RDF™.
Click to expand...
That's pretty much standard across the board, not just to the Kool-Aid iCreators. It's marketing lingo.
 
I'm $#@$@#

My system is completely hosed. :mad: Finder is crashing my system, the icons are all missing, .dmg packages are not working. This really sucks.
 
It'll be nice if you listed system specs, software versions, if you got hacks or anything before going off wildly with your problems.
 
*snickers at the thought that no System Update to date has caused him any problems*

Sorry to hear that, Object-X.. :eek:

</jinx>
 
antirealist said:
But isn't this the sort of thing that got Microsoft into trouble with IE and its entanglement with the rest of the OS? Suppose I'm a committed Firefox user and I want to remove Safari from my system. I can do that and retain other apps which use WebKit, like Mail. But then I'm not going to be installing Safari updates, which may fix WebKit bugs. Updating WebKit through Safari makes it necessary to keep Safari around and current, even if I don't want it.
Click to expand...

All the more reason that Apple needs to hurry up and make Safari the best web browser EVAR!

Seriously though, you are right and it is a conundrum. On the one hand it would be foolish for Dashboard, Safari, Mail and whatever else uses WebKit to go and do all that themselves duplicating code and work. Then again, it would be nice if the user could plug in their prefered engine of choice (WebKit, Gecko, etc.) into these applications. They would all have to be standardized to work together though. I proposed this for Windows a long time ago, when Microsoft built IE's rendering engine into the Windows API. Needless to say nobody followed my advice and I doubt they will this time.

A dedicated mac and firefox fanatic would probably jump for joy if they could plug firefox's gecko engine into Safari giving them Safari's interface and firefox's rendering, right? We can dream antirealist, we can dream.
 
ohcrap said:
*snickers at the thought that no System Update to date has caused him any problems*

Sorry to hear that, Object-X.. :eek:

</jinx>
Click to expand...

First time for everything I guess. Reinstalling.... :(
 
Loge said:
Seems exactly the same to me. Guess I wasn't running into the bugs that it fixed.
Click to expand...

I here you! Does anybody know exactly what this did, if anything? www.edmunds.com and www.newegg.com work now, but did they work before this update? I don't often visit them myself, but I heard that Safari was having problems with them.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back