Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases First Leopard Update (10.5.1)
- Thread starter boer
- Start date
- Sort by reaction score
Let me clarify: Leopard as an OS has been rock solid. Divx WP has always been flakey - even going back to Tiger. However, it now seems more reliable under Leopard.
Crikey.... so much, for so little !
For those with problems.... How many of you had systems that were upgraded from Tiger without doing a Clean Install... I know when I installed it from my Tiger using a normal Update it ran lousy. Then I did a clean install and it runs like a champ.... I know I had issues with tiger that were minor that Leopard exaggerated. Crazy things like Photoshop couldn't update itself, Issues with waking up... But after a clean install Leopard now runs much better then Tiger ever ran. Even with the update there are some MINOR bugs like X11 on MultiScreen Displays.
Gah too many posts, oh well...
My post will get lost for sure, oh well. I noticed after installing the update, my core image issues seem to be somewhat fixed. Graphics are still not as fluid as Tiger, but they are at least 2x from what they were before. I'm talking about things like minimizing windows. Good update, but we still have a little ways to go before its like Tiger was.
Specs: PPC G5 1.6GHZ, Radeon 9600 Pro, 4 GB of RAM
My post will get lost for sure, oh well. I noticed after installing the update, my core image issues seem to be somewhat fixed. Graphics are still not as fluid as Tiger, but they are at least 2x from what they were before. I'm talking about things like minimizing windows. Good update, but we still have a little ways to go before its like Tiger was.
Specs: PPC G5 1.6GHZ, Radeon 9600 Pro, 4 GB of RAM
My system was a clean install of Leopard. AirPort disks were working fine under 10.5.0, and now under 10.5.1 all hell has broken lose. Very disappointing.
Anyone else notice that this update seems to be utilizing less RAM?
It looks like, from what I have running, around half a gig less.
Maybe 10.5.1 made Leopard less of a RAM hog?
/if this has been mentioned before, my apologies. I didn't have time to read through all of the 21 pages of comments
It looks like, from what I have running, around half a gig less.
Maybe 10.5.1 made Leopard less of a RAM hog?
/if this has been mentioned before, my apologies. I didn't have time to read through all of the 21 pages of comments
Nah... I don't know... I did a regular upgrade and (apart from a few minor incidents, like Netscape Navigator 9.0.1 crashing, and some unknown plug-in(s) for Indesign CS2 causing Indesign to crash) it has worked like a charm...
Great update This DOESN'T fix Time Machine, Spotlight, or Disk Utility repair permissions. Awesome!
This DOESN'T fix Time Machine, Spotlight, or Disk Utility repair permissions. Awesome!
Everyting installed just fine on my MBP and I did not notice a long reboot period. I can comfortably say that nothing seems snappier. Everything is running as smooth as silk just as before the update. I do firmly believe that those who say things seem faster just don't reboot their machines enough.
Mac Pro and ATI card graphics issues?
Umm.... I have a Mac Pro (dual 2.66Ghz) with ATI x1900XT video card, purchased shortly after the machine was first released. I leave it on all the time and use it daily, and I've never seen this issue.
It sure looks like some type of memory timing or overheating issue to me though, by the screen captures you linked to. I've seen similar dithering problems before on Windows PCs and other, older Macs - and bad video memory or a bad cooling fan on a video card were common culprits.
I even had a long-standing issue with a G4 tower where I'd occasionally get green dithering like that, which would come out of nowhere and ghost across the screen for a while. I *finally* learned it was a defective Apple 22" Cinema Display (with ADC connector) causing the whole problem, when I moved the display to a new Mac and the problem followed it.
For whatever it's worth though, have you ever tried opening up your Mac Pro, pulling out the ATI card, and blowing the dust out of it? I remember a number of complaints of video "artifacts" while playing 3D games and the like on Mac Pros with ATI X1900XT cards, over on xlr8yourmac.com. Many were resolved when people discovered a layer of dust built up in and around the heatsink and fan assembly on the video card, causing it to run too hot.
Umm.... I have a Mac Pro (dual 2.66Ghz) with ATI x1900XT video card, purchased shortly after the machine was first released. I leave it on all the time and use it daily, and I've never seen this issue.
It sure looks like some type of memory timing or overheating issue to me though, by the screen captures you linked to. I've seen similar dithering problems before on Windows PCs and other, older Macs - and bad video memory or a bad cooling fan on a video card were common culprits.
I even had a long-standing issue with a G4 tower where I'd occasionally get green dithering like that, which would come out of nowhere and ghost across the screen for a while. I *finally* learned it was a defective Apple 22" Cinema Display (with ADC connector) causing the whole problem, when I moved the display to a new Mac and the problem followed it.
For whatever it's worth though, have you ever tried opening up your Mac Pro, pulling out the ATI card, and blowing the dust out of it? I remember a number of complaints of video "artifacts" while playing 3D games and the like on Mac Pros with ATI X1900XT cards, over on xlr8yourmac.com. Many were resolved when people discovered a layer of dust built up in and around the heatsink and fan assembly on the video card, causing it to run too hot.
......like the graphics problems that plague most mac pros with x1900s,which is also what most mac using professionals use,the bug isnt hard to track down and notice. in our main office we have 6 mac pros with the radeon x1900s. 6/6 are affected. at home i have a mac pro with x1900 and macbook pro. my mac pro has the same problems. of my friends that have mac pros with the x1900,all i've talked to so far which is at least 10 have the bug showing constantly also.
the bugs with this configuration,again i think probably's top selling pro config make the system unusable for almost anything.like i said there are thousands of similar screenshots on the net but just so you get an idea of what i mean look at
http://www.dganimation.com/CIMG3574.jpg
http://att.macrumors.com/attachment.php?attachmentid=89577&stc=1&d=1193810876
these little lines are shown all over the display,constantly with no way to fix it.the colors and shapes also appear covering up everything on screen under them continuously while using leopard. if it happened just once in a while or was not common and some oddity or rare bug that'd be one thing.But its not. if
which even fuels my frustration further because there is NO doubt that they saw this major bug and still went ahead and sold the OS at retail and up until right this moment they havent even officially said it exists.
re: wifi problems
Ron, I've had that happen before after doing one of the Tiger updates. What finally fixed it for me was deleting all of my saved networks from the "preferred" list and forcing OS X to re-detect my wi-fi network as though it was the first time it ever saw it. When I did that and keyed in my password, telling it to save it in the keychain, it remembered it fine afterwards.
Ron, I've had that happen before after doing one of the Tiger updates. What finally fixed it for me was deleting all of my saved networks from the "preferred" list and forcing OS X to re-detect my wi-fi network as though it was the first time it ever saw it. When I did that and keyed in my password, telling it to save it in the keychain, it remembered it fine afterwards.
I've done that for (at least) up to three days, and around that time, things seem to get glitchy...
Check out this hint for spring loaded folders and stacks in the Dock in Leopard:
http://www.macosxhints.com/article.php?story=20071027195419540&query=spring+load+dock
I only reboot my Mac (whether it was my iBook G3, G4, and now MacBook) maybe once a week. I don't know why I do it- maybe because it just seems strange to leave something powered on for longer than that. There is no rationality to my doing it. It isn't due to any loss in functionality or speed (or the new word of the year 'snappiness')
I've never experienced any glitchiness- am I the only one? Is it just luck?
"I can't help it if I'm lucky." -Bob Dylan (stolen by Hootie)
I've never experienced any glitchiness- am I the only one? Is it just luck?
"I can't help it if I'm lucky." -Bob Dylan (stolen by Hootie)
I got these too, but my permissions did finish repairing and my Macbook runs fine.
Black Macbook C2D 2.0 GHz.
I've gotten something like that. Had it before, and still have it with 10.5.1. The tones and trash emptying sound effects seem to crash often and only a reboot fixes it.
Soon after updating to 10.5.1 this morning, I noticed the fan in my MBP (2.4Ghz, 4Gb RAM) go crazy. Checking the running processes in Activity Monitor, I saw that the "syslogd" daemon was hogging 100% of my CPU virtually continuously.
Checking the Apple Support Discussions, I found that after the update a process called "mDNSReporter" constantly tries to contact Apple's .Mac server via (in my case) port 5450. Since my corporate firewall has that port blocked, syslogd went doolally.
Cutting to the chase, it seems that I have to turn "Back To My Mac" services off to keep syslogd under control. However, even now syslogd occasionally takes 100% of my CPU for a second or so, before dropping back down (it's also taking nearly 600Mb of virtual memory, can that be right...?)
So my question is: Is anyone here using Back To My Mac with 10.5.1 without problems? Also: Any Mac/UNIX geeks out there with an idea as to how to fix my issue?
(I did a complete disk reformat and fresh Leopard install when I first put 10.5 on my Mac, BTW)
Checking the Apple Support Discussions, I found that after the update a process called "mDNSReporter" constantly tries to contact Apple's .Mac server via (in my case) port 5450. Since my corporate firewall has that port blocked, syslogd went doolally.
Cutting to the chase, it seems that I have to turn "Back To My Mac" services off to keep syslogd under control. However, even now syslogd occasionally takes 100% of my CPU for a second or so, before dropping back down (it's also taking nearly 600Mb of virtual memory, can that be right...?)
So my question is: Is anyone here using Back To My Mac with 10.5.1 without problems? Also: Any Mac/UNIX geeks out there with an idea as to how to fix my issue?
(I did a complete disk reformat and fresh Leopard install when I first put 10.5 on my Mac, BTW)
Anyone else notice that this update seems to be utilizing less RAM?
It looks like, from what I have running, around half a gig less.
Maybe 10.5.1 made Leopard less of a RAM hog?
/if this has been mentioned before, my apologies. I didn't have time to read through all of the 21 pages of comments
Yes, looking at my Activity Monitor, my PB is definitely using less RAM.
The first update is always relatively small in size, the main idea is to get the big important fixes out, then gradually work down the triage. By the time 10.4.11 rolls around its normally down to fixing annoying bugs rather than potential show stoppers.
I've not really posted my issues, but the generally unstable nature of Leopard (iMac G5, 1.8 GHZ) caused me to reinstall Tiger after only 6 days.
I was getting Kernal Panics literally 2 to 3 times a day, and nothing I did could isolate the issue. I unplugged all USB and FireWire peripherals and it still happened. Occasionally it would happen immediately when opening an app (primarily iPhoto and iCal), sometimes when sending an email through Mail, and more often than not completely randomly.
Here was the worst part, the last KP I had was when opening Time Machine. After that it wouldn't boot, it would stick on the Apple logo screen literally for hours. Whatever happened in that last panic corrupted my Time Machine disc to the point where I couldn't use it as a restore point using the 10.5 install discs.
I panicked - my iPhoto library is 6 GB, and my iTunes is 137 GB. My backup plan (Time Machine) failed. The only way I solved it? I installed Tiger on a FireWire external HD, booted from it, and was able to see my internal HD from there (but couldn't boot from it). I copied over my iLife media to the external, then cloned THAT drive back to my internal HD. I've been happily running Tiger again the last 2 weeks with no problems whatsoever.
I'm hopeful that 10.5.1 will fix whatever the hell was wrong, but am more than a little scared to try. FWIW I've had ZERO problems with Leopard on my CD MacBook. It's been absolutely perfect.
I was getting Kernal Panics literally 2 to 3 times a day, and nothing I did could isolate the issue. I unplugged all USB and FireWire peripherals and it still happened. Occasionally it would happen immediately when opening an app (primarily iPhoto and iCal), sometimes when sending an email through Mail, and more often than not completely randomly.
Here was the worst part, the last KP I had was when opening Time Machine. After that it wouldn't boot, it would stick on the Apple logo screen literally for hours. Whatever happened in that last panic corrupted my Time Machine disc to the point where I couldn't use it as a restore point using the 10.5 install discs.
I panicked - my iPhoto library is 6 GB, and my iTunes is 137 GB. My backup plan (Time Machine) failed. The only way I solved it? I installed Tiger on a FireWire external HD, booted from it, and was able to see my internal HD from there (but couldn't boot from it). I copied over my iLife media to the external, then cloned THAT drive back to my internal HD. I've been happily running Tiger again the last 2 weeks with no problems whatsoever.
I'm hopeful that 10.5.1 will fix whatever the hell was wrong, but am more than a little scared to try. FWIW I've had ZERO problems with Leopard on my CD MacBook. It's been absolutely perfect.
Not better than Tiger IMHO, but pretty damn decently considering.
I'm just waiting for someone to chime in and say the reason the 12" PB doesn't have the transparent menubar is because its graphics card isn't up to it.
Meh, you're not missing out on anything; it isn't as though its a key important feature.
ps. Just had a look at your signature, your wife is a core duo MacBook?
What I would love to know is what popped in their head which made them think they needed to change it? sure, Finder needs fixing up but the bar at the top and the dock at the bottom were very minor.