[JKT]

Well, for me 2 out of 3 Macs went perfectly. The third didn't restart correctly as it failed at the first shut down following installation (where it oscillated between a blank blue screen and a blue screen with a spinning dial after the account had been logged out and stayed that way for well over half an hour; I had to force a shut down but it rebooted fine after that). The sad thing is, this was the Mac that should have given me least trouble as it barely has anything installed on it and no hacks of any kind whatsoever (my other two have MenuCracker installed to permit me to use a few menu bar items and that is it). Colour me confused

[JKT]

Oops, slight mistake... I forgot that my Powerbook, for whatever reason, reindexed its Spotlight database afterwards too.

So 1 out of 3 Macs went perfectly, 1 went near perfectly, and 1 failed in a not so bad way, but not in a way that makes me feel any more confident about 10.5.

[JellyBeen]

10.5.7 seems to have fixed my problem when waking from sleep. When I would wake from sleep, I would get a few applications start to freeze, my internet connection would get dropped and I would have to restart. After 5 sleep cycles, it has not happened yet. Thank you Apple!

[ghporter]

Originally Posted by JKT 

Well, for me 2 out of 3 Macs went perfectly. The third didn't restart correctly as it failed at the first shut down following installation (where it oscillated between a blank blue screen and a blue screen with a spinning dial after the account had been logged out and stayed that way for well over half an hour; I had to force a shut down but it rebooted fine after that). The sad thing is, this was the Mac that should have given me least trouble as it barely has anything installed on it and no hacks of any kind whatsoever (my other two have MenuCracker installed to permit me to use a few menu bar items and that is it). Colour me confused

That vacillating between blank and blue screens with the pinwheel sounds an awful lot like what I saw in my iMac's update. When I restarted the machine manually, it took a while, including giving me a notice that it was doing something about "rebuilding boot caches." I wonder if that's what it was trying to do during that back-and-forth crap...

[voicebox]

Hi there,
It was with some trepidation that I 'grasped the nettle' and downloaded the Combo from the Apple site. (Never use Software Update)
Before installing it, I first repaired permissions, then I verified the disk - after which I installed the update.
My MBP restarted a couple of times and was running a-ok. I again checked permissions. I then downloaded the Safari 4 beta update and ran a permission check again.
I have to say that I have not had any problems whatsoever - in fact the system seems to be snappier, if not a little faster.
Nothing missing, no sleep problems - all files seem to be in their right place etc, etc ....
So, a positive and happy outcome - with no tearing of hair or rending of garments!
voicebox

[AKcrab]

Originally Posted by voicebox 

... I first repaired permissions, then I verified the disk ... I again checked permissions. ... and ran a permission check again.

Interesting.

[voicebox]

Originally Posted by AKcrab 

Interesting.

Just following a well tried practice when upgrading - have always done it - always will ... and in doing so, it has always worked!
I don't want to sound pompous - but in following those guidelines I have never had any serious problems with any of my Mac computers!

[Art Vandelay]

I've never done it and have never had any serious problems either. I will never repair permissions unless I actually have a problem that calls for it.

If you insist on repairing permissions when updating, just do it after the update. Doing it before is a total waste of time. Even if your permissions were totally borked, it won't matter. The installer runs as root and permissions have no effect on root.

[Spheric Harlot]

Originally Posted by voicebox 

Just following a well tried practice when upgrading - have always done it - always will ... and in doing so, it has always worked!
I don't want to sound pompous - but in following those guidelines I have never had any serious problems with any of my Mac computers!

The fact that you enter your password to install a system update means that it is completely irrelevant whether the proper permissions have been set beforehand; the installer has superuser rights and will install whatever it needs to, wherever it wants to, with exactly the permissions it requires.

Repairing permissions before AND after an update just means you have too much time to waste.

[voicebox]

Originally Posted by Spheric Harlot 

The fact that you enter your password to install a system update means that it is completely irrelevant whether the proper permissions have been set beforehand; the installer has superuser rights and will install whatever it needs to, wherever it wants to, with exactly the permissions it requires.

Repairing permissions before AND after an update just means you have too much time to waste.

Well it works for me - and it seems to keep my MPB happy - so there - with knobs on!!

[Spheric Harlot]

"Oi! Just what do you think you're doing, spreading that powder all over the street!"

"It's elephant powder, constable. It's to keep the elephants away."

"There aren't any elephants around here!"

"See?"

[voicebox]

Originally Posted by Spheric Harlot 

"Oi! Just what do you think you're doing, spreading that powder all over the street!"

"It's elephant powder, constable. It's to keep the elephants away."

"There aren't any elephants around here!"

"See?"

Hi Spheric Harlot,
Interesting take ...mmm..
By the way, have you had any problems during and after installing 10.5.7?

[Spheric Harlot]

Originally Posted by voicebox 

Hi Spheric Harlot,
Interesting take ...mmm..
By the way, have you had any problems during and after installing 10.5.7?

None whatsoever - so far.

This is my production machine, and it's gone right on chugging along.

::knocks on wood::

[Maflynn]

I'm going to take the plunge later this morning, I just finished installing my new 500gig 7200 RPM drive WOOHOO in my MBP and I opted to reinstall OSX as opposed to using TM to do a full restore. Its currently pulling back my data now, but I thought it was better in the long run to start with a clean install. I've been adding/deleting all sorts of apps lately, but I digress.

I've got my fingers crossed, because I have > gig of updates to download and apply, including a huge 10.5.7 combo update.

[voicebox]

Originally Posted by Spheric Harlot 

None whatsoever - so far.

This is my production machine, and it's gone right on chugging along.

::knocks on wood::

Congratulations Spheric Harlot,
It would appear that we both, in our own way, have reached nirvana .... we must count ourselves lucky - other people have not been able to share our good fortune!
voicebox

[Wiskedjak]

Originally Posted by DCJ001 

Maybe "Apple's shoddy QA" missed something with 10.5.4, and 10.5.5, 10.5.6, & 10.5.7 updates have fixed the errors?

Actually, I just checked and realized that my MacBook is still at 10.5.2. My general process with Apple's OSs is to apply updates until I get to a build that has no errors for how I use the OS, and then I stay at that build until they release something new that entices me to upgrade. 10.5.2 is working for me without any problems. Given how difficult Apple makes it to get back to previously stable builds, I think I'll stay at 10.5.2 until something else appealing shows up.

Interestingly, I have no such worries with Windows and have it set to auto-update.

[JKT]

Apple does give an easy way to roll back an update - it is called Time Machine. Prior to 10.5, it was called Backup and Restore in Disk Utility.

[Spheric Harlot]

Originally Posted by voicebox 

Congratulations Spheric Harlot,
It would appear that we both, in our own way, have reached nirvana .... we must count ourselves lucky - other people have not been able to share our good fortune!

Certainly.

I dare propose, though, that it wasn't their lack of discipline in performing questionable acts (of "maintenance") wot messed them up.

[ghporter]

Originally Posted by Wiskedjak 

Interestingly, I have no such worries with Windows and have it set to auto-update.

Windows fixes are most commonly to repair yet another hole or other method of exploiting a flaw in the code that implements the OS. They take their sweet time in actually fixing functions that don't work correctly or that fail in some way to do what they are supposed to.

How long did it take for MS to come out with OS support for WPA2 in XP? And then they hid it, marking it as a not "high-priority" update, then didn't make it explicitly clear that SP3 did indeed contain this update.

In this case, your "auto-update" is actually patching the ever increasing number of holes and hazards that are inherent to Windows, while OS X updates actually FIX things and provide new features as soon as possible within reason-there's a balance between getting the updates out and making sure they are as bobble-free as possible.

So your "interesting" observation is really an attempt to compare apples to bananas.

[voicebox]

Originally Posted by Spheric Harlot 

Certainly.

I dare propose, though, that it wasn't their lack of discipline in performing questionable acts (of "maintenance") wot messed them up.

Would you like to meet for coffee ....?

[msuper69]

Originally Posted by Art Vandelay 

I've never done it and have never had any serious problems either. I will never repair permissions unless I actually have a problem that calls for it.

If you insist on repairing permissions when updating, just do it after the update. Doing it before is a total waste of time. Even if your permissions were totally borked, it won't matter. The installer runs as root and permissions have no effect on root.

Heed these words of wisdom.

Art speaks the truth.

[cgc]

Just noticed another upgrade I've been waiting on forever is OSX...Apple changed the Energy Saver icon to this:

[- - e r i k - -]

Originally Posted by cgc 

Just noticed another upgrade I've been waiting on forever is OSX...Apple changed the Energy Saver icon to this:

That's on all recent macs only from at least 10.5.5.

Older macs still have the same icon even with 10.5.7.

[ghporter]

Originally Posted by - - e r i k - - 

That's on all recent macs only from at least 10.5.5.

Older macs still have the same icon even with 10.5.7.

My 2007 aluminum iMac still has incandescent, not CFL.

By the way, my wife's month-old MacBook updated last night without any bobbles. It didn't even seem to take as long to do its thing as other updates on my iMac have.

[angelmb]

My 2007 aluminum iMac still has incandescent, not CFL.

Older macs still have the same icon even with 10.5.7.

Weird, all the Macs I have here (2006 Mac Pro, 2007 aluminum iMac, 2008 MacBook Pro Unibody and even the 2003 Power Mac G4 MDD) got the CFL icon.

The MDD has the 23" ACD -aluminum- attached to it but I don't think that has anything to do with it. I can remember it's been on the MacBook Pro since day one, hence 10.5.5 as Erik says.

[Big Mac]

That's an uglier icon. This is what Apple artists are spending their time on?

[cgc]

Originally Posted by - - e r i k - - 

That's on all recent macs only from at least 10.5.5.

Older macs still have the same icon even with 10.5.7.

Really? Seems odd Apple would have it check Mac version prior to drawing an icon...

[TETENAL]

Apple doesn't check the Mac version. System Preferences caches the icon. If you had it open before while the old icon was current, you still get that. New accounts get the new icon.

[ghporter]

Originally Posted by TETENAL 

Apple doesn't check the Mac version. System Preferences caches the icon. If you had it open before while the old icon was current, you still get that. New accounts get the new icon.

Any way to purge the cache?

[angelmb]

With OnyX maybe?

[Hal Itosis]

Originally Posted by ghporter 

Any way to purge the cache?

Quite likely, dumping this file should do the trick:
~/Library/Caches/com.apple.preferencepanes.cache

Originally Posted by Big Mac 

That's an uglier icon. This is what Apple artists are spending their time on?

I don't see enough difference to qualify one as being "uglier" than the other... but certainly the newer one is far more apropos. Don't the stores in your neck of L.A. carry the new energy saving light bulbs yet?

[- - e r i k - -]

Originally Posted by TETENAL 

Apple doesn't check the Mac version. System Preferences caches the icon. If you had it open before while the old icon was current, you still get that. New accounts get the new icon.

Originally Posted by Hal Itosis 

Quite likely, dumping this file should do the trick:
~/Library/Caches/com.apple.preferencepanes.cache

*ding ding ding*

That did the trick.

I wish real energy saving bulbs had the warmth of that icon though

[chris v]

Originally Posted by - - e r i k - - 

*ding ding ding*

That did the trick.

I wish real energy saving bulbs had the warmth of that icon though

Really. The icon should be all blue and sterile.

I'm glad the update came along when it did -- I had something wrong with my directory that I might not have caught until much later. I went to back up my system drive before running the update, and with two different backup utilities, one after a re-boot, my available disk space (on the drive Iwas backing up FROM) dwindled from 78 gb to zero over about 5 minutes. Some sort of temp file gone insane. Fortunately, I hadn't overwritten anything crucial on the backup drive, was able to boot from it, and Disk Warrior seemed to fix it up (incorrect free space in directory Desktop) so that I was able to proceed with the backup.

The install of 10.5.7 itself has been fine on two diff. G5s. I still have erratic syncing problems with MobileMe, but what's new?

[all2ofme]

I read recently (can't remember where) an interview with someone about energy efficient bulbs - the chap said something along the lines of "one of our main problems at the mo is the "alien autopsy" light they throw". I liked that

[kyles_mac]

Would anyone know why 10.5.7 wouldn't show up in Software update? I've wanted to update for quite a while, but every time I check it says I am up-to-date...which clearly, I am not.

[Simon]

You can download the update straight from Apple.

Here's the delta update and here's the combo update.

[TheZee]

I recently got 3 Apple Security Update notices via my email. I then checked Software Update via System Preference Pane. It advised my to install 10.5.7 update (449 Mb) which took close to 2 hours. I am assuming that this update came with the recent Apple Security Updates mentioned above or do I have to download & install them separately ??? Also, after installing 10.5.7 update, Safari 3.2.3 will not load. It just hangs for ever. Firefox 3.0.8 loads and works fine but not Safari 3.2.3. Any ideas on how to fix? Should I go ahead and get Safari 4 Beta? So far these are the only issues I have encountered after the update and hopefully no more will appear. It might be beneficial for us to start a thread listing and dealing with the main/most common issues that have arisen after downloading and installing 10.5.7. As always though, Apple ROCKS !!!

Peace out,

[Cold Warrior]

Originally Posted by TheZee 

I recently got 3 Apple Security Update notices via my email. I then checked Software Update via System Preference Pane. It advised my to install 10.5.7 update (449 Mb) which took close to 2 hours. I am assuming that this update came with the recent Apple Security Updates mentioned above or do I have to download & install them separately ??? Also, after installing 10.5.7 update, Safari 3.2.3 will not load. It just hangs for ever. Firefox 3.0.8 loads and works fine but not Safari 3.2.3. Any ideas on how to fix? Should I go ahead and get Safari 4 Beta? So far these are the only issues I have encountered after the update and hopefully no more will appear. It might be beneficial for us to start a thread listing and dealing with the main/most common issues that have arisen after downloading and installing 10.5.7. As always though, Apple ROCKS !!!

Peace out,

If software update doesn't show you the security updates anymore, then they were included in 10.5.7.

Yes, I'd upgrade to Safari 4 beta. If you don't like it, Safari 4's installer will uninstall it and reinstall Safari 3.

[TheZee]

Thanks for the heads up on Apple's recent security and OS X updates. I was tripping because I got the email alerts from Apple indicating the Security Updates but then when I used Software Update in the System Preferences Pane the only thing that appeared was the OS X 10.5.7 update. I went ahead and installed it, around 400 and something MBs. I wish Apple would make the email alerts for the Security Updates and what appears in the Software Update System Preference Pane match. I bet that I am not the only one who finds it sometimes a bit confusing. Anyway, all clear now thanks to you and every other Mac Addict who shares their knowledge with the world. Peace out . . .

[Pierre B.]

Originally Posted by Art Vandelay 

I've never done it and have never had any serious problems either. I will never repair permissions unless I actually have a problem that calls for it.

If you insist on repairing permissions when updating, just do it after the update. Doing it before is a total waste of time. Even if your permissions were totally borked, it won't matter. The installer runs as root and permissions have no effect on root.

I have never understood why we should repair permissions before or after system updates. The installer comes with its own permissions, right? Why revert to previous permissions settings, probably not 100% compatible with what the update needs, after having applied the update?

What I do each time before applying such an update, is to boot in single-user mode and run fsck to repair any minor hard disk issue.

[turtle777]

Originally Posted by angelmb 

I heard the installer does that itself.

I doubt this is true.
For the fun of it, I ran my Repair Permissions before installing 10.5.7.

RP took more than 15 min to finish, the Update installed in less than 5.

So, unless the Update skips repairing certain (non-critical) areas, I don't see how this is supposed to be working.

-t

[Wiskedjak]

If repairing permissions is necessary, then Apple is negligent in not informing users of it when they upgrade.

[turtle777]

I don't dispute that RP is probably not necessary; I'm disputing the statement that the installer does it.

-t

[Hal Itosis]

Originally Posted by Pierre B. 

Why revert to previous permissions settings, probably not 100% compatible with what the update needs, after having applied the update?

I do not promote or condemn repairing perms... folks can do (or not do) what the he11 they want.

But there is a (seemingly ubiquitous) misunderstanding that running a permissions repair can only enforce the original setting (10.5.0 in this case). Bzzzt... false. Somewhere around mid-Panther, Apple introduced a way to override original settings, and -- even though the method has changed in Leopard -- the ability still exists (when properly coded that is). Disk Utility can be made aware of changes, and enforce the latest wisdom from Cupertino.

Unfortunately, some shoddily configured updates have been released lately which have simply skipped over these mechanisms. [i guess all the QC folks are committed to Snow Leopard?] There may also be some glitch which is hampering its effectiveness. I.e., sometimes it doesn't work for some people.

Witness here however that it can work:

Code:
$ pkgutil -v --file-info /System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/CodeResources |tail -21

       pkgid: com.apple.pkg.update.os.10.5.6.combo
 pkg-version: 1.0.1.1191932192
install-time: Tue Dec 16 00:33:52 2008
         uid: 0 (root)
         gid: 0 (wheel)
        mode: 100644 (-rw-r--r-- )

       pkgid: com.apple.pkg.iLifeMediaBrowser_202
 pkg-version: 2.0.2.1.1220381056
install-time: Thu Mar 26 23:20:05 2009
         uid: 0 (root)
         gid: 0 (wheel)
        mode: 120755 (lrwxr-xr-x )

       pkgid: com.apple.pkg.iLifeMediaBrowser_203
 pkg-version: 2.0.3.1.1220381056
install-time: Sat Jun  6 23:30:12 2009
         uid: 0 (root)
         gid: 0 (wheel)
        mode: 120755 (lrwxr-xr-x )

There we can see how Disk Utility was made aware that the iLifeMediaBrowser.framework/Versions/A/CodeResources item (which was formerly a regular file) is now a symbolic link!!!

At least that one item got handled properly on my Mac... proving such actions are indeed possible. But something somewhere is funked up, because many other "CodeResources" items still show up in DU's report window unnecessarily, as supposedly disagreeing with expectations.

It's a bug, and that should be what people become aware of... not these other myths and misunderstandings.

[TheoCryst]

Here's something I just noticed: looks like 10.5.7 finally fixed the Spaces+Carbon Window Groups bug that's been driving me insane since 10.5.0. For those unfamiliar with the bug, see here or here for a basic idea of the bug.

I don't have CS4 to test it out on, but Office 2008 has been working fine on two different machines now. Can anyone else confirm this?

[JKT]

It has? I haven't used Office 2008 enough recently to notice, but that is one bug that was driving me up the wall, so let's hope so. However, it still hasn't fixed new Mail messages from appearing behind my Viewer window whenever I create them from other apps such as my browser; or non-modal dialogues from getting trapped behind windows making it necessary for you to force quit apps to get rid of them. Or the plethora of other issues I experience each day. Damn.