I haven't had an issue with 10.5.2, it works great - snappy, stable as a rock, Bluetooth seems a lot better, and AirPort is nicely improved. 🙂
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.
10.5.2.... worst update ever?
- Thread starter Vitek
- Start date
- Sort by reaction score
well, i don't know if 10.5.2 update improve the wireless or not ... maybe some people feel that the Wireless improve, some people maybe not since there is a lot of Wireless device models, type or brand.
my experience with 10.5.2, i did test on some hotspot (i test it on Public hotspot, Cafe, Restaurant) which previously i can't connect, now can connect smoothly, for me the Wireless improve a bit.
my experience with 10.5.2, i did test on some hotspot (i test it on Public hotspot, Cafe, Restaurant) which previously i can't connect, now can connect smoothly, for me the Wireless improve a bit.
it gets better...
It only gets better, I would advise switchers to repair permissions after any update or repair permissions before, learn how to diagnose your system, there are plenty of basic tools to assist you in this and you don't have to be a technician to understand its data, for example the Console logs provide a lot of good basic info, the Terminal app is great to and all you have to do is learn a couple of commands, also do not be afraid of researching your issue here on these forums and on the Apple site, I cannot believe that I will be posting the "sleep"issue yet again on these forums (which is to disconnect the battery from your laptop or disconnect your desktop, press the powerbutton for about ten seconds then reconnect,restart, other wise known as the PMU reset!) I was racing against this update to solve the connectivity issue and I did before the update was issued, the update was good. no known issues, works well on my mini and powerbook g4. There was a user in the Apple site that kept posting the same B.S on a thread about the connectivity issue and claimed that he did not need to try any hints or research any fixes since it is Apple's responsibility too keep his machine stable, "he demands the update now" silly Chamcox got the thread locked-out, he did not try any of the hints and I think hes still struggling, so avoid being like Chamcox an acute passive user, learn how to do basic trouble-shoot and do try the hints and fixes and learn in the meanwhile a new thing or two. Expect things to get bad once in a while with some update as well, but remember you have very good Mac users here in Macrumors willing to help.
It only gets better, I would advise switchers to repair permissions after any update or repair permissions before, learn how to diagnose your system, there are plenty of basic tools to assist you in this and you don't have to be a technician to understand its data, for example the Console logs provide a lot of good basic info, the Terminal app is great to and all you have to do is learn a couple of commands, also do not be afraid of researching your issue here on these forums and on the Apple site, I cannot believe that I will be posting the "sleep"issue yet again on these forums (which is to disconnect the battery from your laptop or disconnect your desktop, press the powerbutton for about ten seconds then reconnect,restart, other wise known as the PMU reset!) I was racing against this update to solve the connectivity issue and I did before the update was issued, the update was good. no known issues, works well on my mini and powerbook g4. There was a user in the Apple site that kept posting the same B.S on a thread about the connectivity issue and claimed that he did not need to try any hints or research any fixes since it is Apple's responsibility too keep his machine stable, "he demands the update now" silly Chamcox got the thread locked-out, he did not try any of the hints and I think hes still struggling, so avoid being like Chamcox an acute passive user, learn how to do basic trouble-shoot and do try the hints and fixes and learn in the meanwhile a new thing or two. Expect things to get bad once in a while with some update as well, but remember you have very good Mac users here in Macrumors willing to help.
Attachments
FF_productions
macrumors 68030
My Wireless connection drops every so often for a few seconds.
Apple's gotta lay off the iPhone and start making Leopard work!
Apple's gotta lay off the iPhone and start making Leopard work!
Had some initial problems in 802.11n mode with my DIR-635 (which was only draft-n 1.0)... Upgraded that to a DIR-655 (draft-n 2.0 certified) and problems went away.
Now, after repairing permissions and doing a PRAM reset, the system's up and happy. One of my main gripes, HSDPA over bluetooth with a Windows Mobile 6 device, has also been fixed.
Now, after repairing permissions and doing a PRAM reset, the system's up and happy. One of my main gripes, HSDPA over bluetooth with a Windows Mobile 6 device, has also been fixed.
Eraserhead
macrumors G4
Don't you mean: 10.5.2 best update ever, transparent menu and stacks were made to work.
Killyp
macrumors 68040
There's always one of these threads every time a new update comes out...
You can't expect them to fix 'everything' for EVERY Macintosh. I've actually found 10.5.2 to be a big improvement (especially AirPort, which used to make the whole machine lock up for a second or so).
You can't expect them to fix 'everything' for EVERY Macintosh. I've actually found 10.5.2 to be a big improvement (especially AirPort, which used to make the whole machine lock up for a second or so).
clevin
macrumors G3
indeed, just don't know how large a percentage of users still have problems.
Macs only have so much limited hardware combinations, apple shouldn't have too much problems fixing things.
no I don't mean that, I can't stay online for more than 5 minutes with this update! Everything was fine with 10.5.1
When you install an update, you do this as root. This is why the installer asks for your password. As root, the installer will ignore any user assigned permissions and overwrite them. There is, therefore, no earthly point in "repairing" permissions before an update. Ever. But hey, if it makes you feel better, knock yourself out.
As for problems, for me they arose with 10.5.1. I suddenly found myself unable to connect to wireless after sleep. Added to this, I started to experience dropouts during the day where Airport would seem to scan and scan and scan and yet be unable to connect to any of the signals it picked up. 10.5.2 has not fixed a thing.
This is not a hardware issue as it did not crop up under Tiger and not even with stock Leopard.
did you check you network keychain?...
In the Keychain Access Control tab you should see the following elements in your wireless or network keychain:
the systemuiserver.app
I had to delete all the plist files because it did not re-connect after I awoke the computer from sleep, so I threw away the system configuration folder, all airport plists files and the keychain, upon restarting the keychain showed the files I was looking for which is the systemUIserver and the airport deamon, (in the keychain lists as: airport) I added the System prefs and the apple80211agent. I think this stabilizes yet again the network.
In the Keychain Access Control tab you should see the following elements in your wireless or network keychain:
the systemuiserver.app
I had to delete all the plist files because it did not re-connect after I awoke the computer from sleep, so I threw away the system configuration folder, all airport plists files and the keychain, upon restarting the keychain showed the files I was looking for which is the systemUIserver and the airport deamon, (in the keychain lists as: airport) I added the System prefs and the apple80211agent. I think this stabilizes yet again the network.
Attachments
the update does work...
in 10.5.1 the airportd (airport daemon) was located in /usr/bin/libexec, after the update it was relocated to Groups:// I do not know where this last section is but it may explain some of the initial glitches regarding connectivity, some users had achieved good wireless connectivity with some of the hints posted during 10.5.1, but after the update people started to wonder if the update ruined it, after some inspection I saw that the wireless or network keychain was altered after the update, the System preferences icon was missing from the allowed list in the control access tab, so I added it plus the Apple80211Agent, and I have not had a drop-out since.
the Apple80211Agent is located System>library>coreservices.
In the pic it shows the Airportd icon but its actually a small hack that I did but Im not sure it works as it should.
<NEW EVENT> the network was dropping yet again, so threw away the keychain and plists files and restarted, when I registered the network these new files appeared in the new wireless keychain which are the ones I think helped maintain stability or achieve connection as in 10.5.1
in 10.5.1 the airportd (airport daemon) was located in /usr/bin/libexec, after the update it was relocated to Groups:// I do not know where this last section is but it may explain some of the initial glitches regarding connectivity, some users had achieved good wireless connectivity with some of the hints posted during 10.5.1, but after the update people started to wonder if the update ruined it, after some inspection I saw that the wireless or network keychain was altered after the update, the System preferences icon was missing from the allowed list in the control access tab, so I added it plus the Apple80211Agent, and I have not had a drop-out since.
the Apple80211Agent is located System>library>coreservices.
In the pic it shows the Airportd icon but its actually a small hack that I did but Im not sure it works as it should.
<NEW EVENT> the network was dropping yet again, so threw away the keychain and plists files and restarted, when I registered the network these new files appeared in the new wireless keychain which are the ones I think helped maintain stability or achieve connection as in 10.5.1
Eraserhead
macrumors G4
Not true, this is really a myth, the problem is that consumers generally buy such cheap machines that are unreliable and don't fully meet the hardware specs for Windows. These problems never occur under Windows with decent quality hardware, which is why business still uses Windows.
Virtually all bugs that occur on a lot of computers are software bugs and are caused by bad programming rather than hardware issues. But then they should occur on all machines, or at least all machines in a certain class (i.e. Intel/PPC or 32/64 bit).
Tried repairing permissions and reinstalling the update. If not, have you tried re-installing Leopard.
Update to 10.5.2 affected my login to Windows Server 2003
All in all, the update to 10.5.2 has gone on without a hitch. The one thing that has come up and was not an issue earlier but was a pleasant welcome in Leopard was the ability to log into the Company Server which runs Windows Server 2003 for Small Business.
Under 10.5.2, I can still log in using SMB but then a time lag develop when working on virturally any document that is on the server. Everything from typing input delays to saving the document. Somewhere on the posts, a user mentioned binding to the Active Directory. If I was able to login before without any issues, what would binding do. Is this a workaround or was I just lucky to log in via SMB earlier and just have to complete a couple extra steps.
Any help would be appreciated as to this obviously impedes on any productivity. I figured I would ask versus reinstalling 10.5.1 which would be a royal pain to do. Thanks.
All in all, the update to 10.5.2 has gone on without a hitch. The one thing that has come up and was not an issue earlier but was a pleasant welcome in Leopard was the ability to log into the Company Server which runs Windows Server 2003 for Small Business.
Under 10.5.2, I can still log in using SMB but then a time lag develop when working on virturally any document that is on the server. Everything from typing input delays to saving the document. Somewhere on the posts, a user mentioned binding to the Active Directory. If I was able to login before without any issues, what would binding do. Is this a workaround or was I just lucky to log in via SMB earlier and just have to complete a couple extra steps.
Any help would be appreciated as to this obviously impedes on any productivity. I figured I would ask versus reinstalling 10.5.1 which would be a royal pain to do. Thanks.
Eraserhead
macrumors G4
try this benign hint...
you may try and delete the following plist files: hd>library>preferences>com.apple.windowserver.plist, Appleshareclient.plist, and in the System Configuration folder within the preferences folder there are some possible files relating to your issue and in the Directory Service (same preference folder) folder as well. try some of these and it may reset your ability to connect to that server.
you may try and delete the following plist files: hd>library>preferences>com.apple.windowserver.plist, Appleshareclient.plist, and in the System Configuration folder within the preferences folder there are some possible files relating to your issue and in the Directory Service (same preference folder) folder as well. try some of these and it may reset your ability to connect to that server.
Mr Black
macrumors member
I also have a 2wire router and was having that issue, but I figured it out. Here are 2 possible fixes.
1. Connect an ethernet cable from your router to your mac, then turn on airport, once it connects and in the network preference pane it says you have an Ip address for airport, then disconnect the ethernet and the problem should be permanently solved.
or
2. Delete all instances of your wireless password from your keychain (open keychain access -> login keychain) and when you turn airport on re-enter all your wireless network info and that should sort you out if Solution 1 didnt.
If after trying these your still having issues reply back to me with what model your 2wire is and any relevant info on how you have it configured for wireless.
DesignerOnMac
macrumors 6502a
The update has worked fine for me, including the graphics card update afterwards. Only issue is with Skype and sound, (have the latest version also).
Yes - worst update ever. I've never heard of an update (apple or MS) that actually makes the OS unusable while fixing nothing.
Yeah. This point was driven home for me the the other day when the Apple"Care" lady was told me for the 5th time on the same call to reapply the 10.5.2 update, when I'd just told her for the 10th time that I couldn't SEE the update because my Finder wouldn't fully load (I have the missing desktop/no Finder bar issue many others have reported). Eventually realizing the futility of trying to get through to her I asked if there was a way to do it from Terminal (I used to know my way around the DOS command line pretty well, but I've only been using Macs for five years and haven't messed much with Terminal): she replied, "probably...", and then said, "let me check with some other people." She put me on hold for 10 minutes, then came back and said, "do an archive & install; that should solve your problems". Yep, that's the kind of advice I bought Apple"Care" for.