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
Does it fix USB PCI card failure to wake from sleep. Huge annoyance for me and unacceptable that 10.5 was released with such an obvious problem.
Combo updater?
So is the 110 MB download from Apple's site, basically the combo updater, even though it doesn't say Combo?
Are they not doing Combo updaters for Leopard?
-Kevin
EDIT: Nevermind....why would there be a Combo updater.....this is the first update ?!?! Brain cramp!
So is the 110 MB download from Apple's site, basically the combo updater, even though it doesn't say Combo?
Are they not doing Combo updaters for Leopard?
-Kevin
EDIT: Nevermind....why would there be a Combo updater.....this is the first update ?!?! Brain cramp!
15/11/07 8:40:13 AM Mail[104] Exception raised on RSS thread: PSException: PubSub Foundation::NetException: (ipc/mig) server died (11,-308) during void -[PSEntry setRead:](PSEntry*, objc_selector*, BOOL)
15/11/07 8:40:13 AM com.apple.launchd[78] (com.apple.PubSub.Agent[106]) Exited abnormally: Segmentation fault
15/11/07 1:09:57 PM Mail[221] Exception raised on RSS thread: PSException: PubSub Foundation::NetException: (ipc/mig) server died (11,-308) during void -[PSEntry setRead:](PSEntry*, objc_selector*, BOOL)
15/11/07 1:09:57 PM com.apple.launchd[171] (com.apple.PubSub.Agent[224]) Exited abnormally: Segmentation fault
15/11/07 1:09:57 PM com.apple.launchd[171] (com.apple.PubSub.Agent) Throttling respawn: Will start in 5 seconds
Still getting these in Apple Mail...
15/11/07 8:40:13 AM com.apple.launchd[78] (com.apple.PubSub.Agent[106]) Exited abnormally: Segmentation fault
15/11/07 1:09:57 PM Mail[221] Exception raised on RSS thread: PSException: PubSub Foundation::NetException: (ipc/mig) server died (11,-308) during void -[PSEntry setRead:](PSEntry*, objc_selector*, BOOL)
15/11/07 1:09:57 PM com.apple.launchd[171] (com.apple.PubSub.Agent[224]) Exited abnormally: Segmentation fault
15/11/07 1:09:57 PM com.apple.launchd[171] (com.apple.PubSub.Agent) Throttling respawn: Will start in 5 seconds
Still getting these in Apple Mail...
updated on my macbook pro c2d and my mac pro...
c2d looks all fine, but the mac pro is having problems.. now i cannot change sharing preferences in the .mac preference pane without a user name and password...but..every single user name and password combination ive tried doesnt work...
also back to my mac doesnt work correctly still
the ONLY reason i went to leopard doesnt work..
c2d looks all fine, but the mac pro is having problems.. now i cannot change sharing preferences in the .mac preference pane without a user name and password...but..every single user name and password combination ive tried doesnt work...
also back to my mac doesnt work correctly still
the ONLY reason i went to leopard doesnt work..
Clarity
I apologize if this has already been explained but it's a long thread and there seems to be alot of 'permissions' confusion here.
These files basically are the update. 'Repair Permissions' compares the permissions state of the system files currently on your mac to the 'install receipts' of the files from your original Leopard Disk. That's why the 'ARDAgent' file has been popping up for a while now. It refers to the 'Apple Remote Desktop Agent' that was one of the first Leopard Software Updates, which is why the file no longer "matches" the one from your install disk.
At some point the verbosity of PRepair changed to include these types of changes and they are not anything to worry about - which is why they aren't fixed. I think Apple mostly considers PRepair to be a more tech-savvy app when put in verbose mode ('show details') and that's why the messages can seem a little opaque if you don't understand exactly how the process works.
After the update these system files changed and no longer necessarily match the ones from 10.5.0, so you see this message in detail mode.
I actually noticed this after the update and thought, 'oh neat, there's the new stuff'. Some of it anyway
So, fear not.
I apologize if this has already been explained but it's a long thread and there seems to be alot of 'permissions' confusion here.
These files basically are the update. 'Repair Permissions' compares the permissions state of the system files currently on your mac to the 'install receipts' of the files from your original Leopard Disk. That's why the 'ARDAgent' file has been popping up for a while now. It refers to the 'Apple Remote Desktop Agent' that was one of the first Leopard Software Updates, which is why the file no longer "matches" the one from your install disk.
At some point the verbosity of PRepair changed to include these types of changes and they are not anything to worry about - which is why they aren't fixed. I think Apple mostly considers PRepair to be a more tech-savvy app when put in verbose mode ('show details') and that's why the messages can seem a little opaque if you don't understand exactly how the process works.
After the update these system files changed and no longer necessarily match the ones from 10.5.0, so you see this message in detail mode.
I actually noticed this after the update and thought, 'oh neat, there's the new stuff'. Some of it anyway
So, fear not.
new update
I successfully installed the new update. I'm not use to the blue screens and the new look of the updating. It can be a little intimidating/scary, however, everything worked out fine. There is this eerie feeling & look to the new way we upgrade that you think to yourself, "something isn't going right." But it does! Maybe Apple needs to bring back the 'happy-mac' icon. (I guess we can't use bombs anymore.)
I successfully installed the new update. I'm not use to the blue screens and the new look of the updating. It can be a little intimidating/scary, however, everything worked out fine. There is this eerie feeling & look to the new way we upgrade that you think to yourself, "something isn't going right." But it does! Maybe Apple needs to bring back the 'happy-mac' icon. (I guess we can't use bombs anymore.)
also fair enough and glad that it is working for you
my frustration and anger over leopard,and I'm a huge
fan but also not blind,is that the severity of so many bugs that are in leopard are not ones that are hard to catchthis without a doubt means that
knowingly released a very bug ridden OS without caring much about the repercussions.only sales mattered it looks like,which is true for most businesses except that there is usually a balance between sales and quality.with leopard seems to have forgotten the quality part and dropped the balllike 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 athttp://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
put leopard on a mac pro with the most popular graphics card they sell out of the 3 options they offer,they would have seen this bug.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.
and deleting thousands of posts on their discussion boards to try and silence the issue?? is that reallly a company that should be given all of your 101% trust? come on people wake up.Apple isnt perfect,far from it in fact. and with all of their recent problems it appears that as a whole the level of quality at
is falling like a stone.those of you that respond to those of us that 'dare' to speak against the almighty and say that we're just whining,you are the ones that are going to get screwed at some point if
doesnt clean up their act.like i also said its nice that your install works perfectly,but don't deny that other huge issues dont exist.that is just flat out irresponsible and shows a bit of brainwashing from PR
I hate being stuck at work on a Windows PC.
Just a couple of more hours though and I shall try it out!
Just a couple of more hours though and I shall try it out!
Okay, on a hunch that maybe the update didn't apply properly I went ahead and downloaded the full size standalone updater for 10.5.1. I have an MBP so the updater that led to the above issue was the smaller, 39 MB one.
Using the full-sized update, that you can find here:
http://docs.info.apple.com/article.html?artnum=306907
All of the WARNINGS in Disk Utility -> Repair Perms are gone, except one:
Repairing permissions for Macintosh HD
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent" has been modified and will not be repaired.
Permissions repair complete
I re-ran Disk Utility -> Repair Perms on my other MBP as a sanity check and it was still getting all those warnings from the 39 MB update. So I'm going to use the full updater on it as well.
Too much work for me to figure out if the files are actually different or if it's just an issue with the meta-data.
Obviously it's for Apple to determine why the difference in behavior for these two different forms of the update...and fix it or at least issue a statement about it.
Regards,
\Leon
802.1X Secure Wireless now working...
Hi y'all.
Been a long time since I've posted.
Since upgrading to Leopard, the 802.1x wireless settings never seemed to work right for my school's secure wireless. For the life of me, I couldn't make it work. One of the steps I had to go through, according to my school, was to create a new 'location' specifically for just the secure wireless access. I mention this because one of the things I did when testing 802.1x was delete that location!
Alright, I turned off Airport from the top menu icon. I opened Network Preferences and deleted the 802.1x location I originally created (I was going to start over...). So now, I'm on "automatic" location. I select Airport and enable it. It picked up the 802.1x secure connection and asked for me to confirm the certificate. I selected "always allow" and then entered my username and password when the 802.1x login screen came up. That was it... For some reason that's all it took.
When I originally setup the 802.1x account, I had to do all sorts of junk in the 'advanced options' area of Airport in Network Preferences. Notably, I did select to enable 802.1x login in the 802.1x tab.
The network I'm connecting to uses PEAP. I'm on a SR MBPro 2.2 Ghz bought a couple weeks after it debuted (for reference). Mileage may vary.
EDIT: Oh, my "domain" setting in Network Preferences -> Airport -> Advanced -> 802.1x was set to "Login window" and my "State:" said the login window was disabled... So for shiggles I changed "domain" to "user" and entered my username/password info. Pressed OK. I cycled airport on and off, now it doesn't even ask me for login information or to 'okay' the certificate.
Cheers.
-Thomas
Hi y'all.
Been a long time since I've posted.
Since upgrading to Leopard, the 802.1x wireless settings never seemed to work right for my school's secure wireless. For the life of me, I couldn't make it work. One of the steps I had to go through, according to my school, was to create a new 'location' specifically for just the secure wireless access. I mention this because one of the things I did when testing 802.1x was delete that location!
Alright, I turned off Airport from the top menu icon. I opened Network Preferences and deleted the 802.1x location I originally created (I was going to start over...). So now, I'm on "automatic" location. I select Airport and enable it. It picked up the 802.1x secure connection and asked for me to confirm the certificate. I selected "always allow" and then entered my username and password when the 802.1x login screen came up. That was it... For some reason that's all it took.
When I originally setup the 802.1x account, I had to do all sorts of junk in the 'advanced options' area of Airport in Network Preferences. Notably, I did select to enable 802.1x login in the 802.1x tab.
The network I'm connecting to uses PEAP. I'm on a SR MBPro 2.2 Ghz bought a couple weeks after it debuted (for reference). Mileage may vary.
EDIT: Oh, my "domain" setting in Network Preferences -> Airport -> Advanced -> 802.1x was set to "Login window" and my "State:" said the login window was disabled... So for shiggles I changed "domain" to "user" and entered my username/password info. Pressed OK. I cycled airport on and off, now it doesn't even ask me for login information or to 'okay' the certificate.
Cheers.
-Thomas
Yeah Same here, Really dissapointed they haven't fixed that, but OH well perhaps next point release. Hard to understand though as in Tiger hops right on it and in no time permissions repair is completed!
My venerable PBG4 12" kernel-panicked at the first reboot after the install of 10.5.1
It seems OK after another forced reboot ...
My Powerbook g4 15" did exactly the same...i have just installed a new ram stick and thought it might be down to that? Do you have Apple Ram or have you upgraded?
On one Mac I've updated, I can't use Google through Safari after updating to 10.5.1. I type a few letters in the search field and Safari locks up.
For those that dislike the 'clear' menu bar and don't want to paint a grey stripe on all your Desktop Pictures, I like this little app:
http://www.macupdate.com/info.php/id/26081/leocolorbar
It doesn't work exactly as advertised on Leopard retail but here's the way to do it - drag your background of choice on to the app, and set the color you want the menu bar to be (I recommend using the RGB sliders in color picker and setting them all to 135, dark grey, for a real nice gradient effect that matches the rest of the new UI while remaining highly readable and contrasty), pick 'stretch, tile, center' etc. from the dropdown then click set desktop. Now go to the Desktop Background Sys Pref and you should see the picture you just created. For some reason to get it to work you have to refresh it by changing the 'stretch, tile, center' mode in the system preference pane then switching it back. Boom, background of your choice with a slick slate grey bar.
The cool thing is the app now remembers your settings and you only have to drop pictures on it and hit the button to change pictures, though you will need to do the Desktop Background sys pref refresh thing again. Quick and easy with no Photoshop.
Also, I believe the menu bar is being 'painted' by the OS now using Core UI and QuartzGL ( see http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/10 ) which is why some GPUs can't do all the required composting and whatnot in a timely and snappy manner, hence the disabled effects.
Please see: https://forums.macrumors.com/posts/4499892/
EDIT: Link fixed
http://www.macupdate.com/info.php/id/26081/leocolorbar
It doesn't work exactly as advertised on Leopard retail but here's the way to do it - drag your background of choice on to the app, and set the color you want the menu bar to be (I recommend using the RGB sliders in color picker and setting them all to 135, dark grey, for a real nice gradient effect that matches the rest of the new UI while remaining highly readable and contrasty), pick 'stretch, tile, center' etc. from the dropdown then click set desktop. Now go to the Desktop Background Sys Pref and you should see the picture you just created. For some reason to get it to work you have to refresh it by changing the 'stretch, tile, center' mode in the system preference pane then switching it back. Boom, background of your choice with a slick slate grey bar.
The cool thing is the app now remembers your settings and you only have to drop pictures on it and hit the button to change pictures, though you will need to do the Desktop Background sys pref refresh thing again. Quick and easy with no Photoshop.
Also, I believe the menu bar is being 'painted' by the OS now using Core UI and QuartzGL ( see http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/10 ) which is why some GPUs can't do all the required composting and whatnot in a timely and snappy manner, hence the disabled effects.
Please see: https://forums.macrumors.com/posts/4499892/
EDIT: Link fixed
Kernal Panic
Just had a kernal panic while working in excel ... got to love it ...
Also excel is not working properly for me now ...
At least I have numbers to fall back on.
Just had a kernal panic while working in excel ... got to love it ...
Also excel is not working properly for me now ...
At least I have numbers to fall back on.
