Mac OS X 10.6.2 Build 10C531 Seeded to Developers

[monti]

Dock
- Resolve a crash in Dock

Does this solve the extremely annoying Dock related Spaces bug? I really hope so!

 

[NSMonkey]

Massive losses? Hardly.

The discs should be pulled because they are dangerous, and any respectable company would be horrified about leaving copies of their product in circulation that can destroy a customers data.

So your only argument is with the particular adjective I chose to describe the cost of recalling 10.6.0 disks? Not with any of the actual substance of my post about the bug only affecting a few people, being trivially and reliably avoided and being fixed already? Well, I guess the issue is settled then.

Video game companies have recalled their entire product runs for much less.

Cite an example, please -- an example of a video game bug that only affected a few people, was easily avoided and where every console could reasonably be expected to be connected to the internet where the customer could easily download a free patch. Let me save you some time: there is no such example.

Apple has a lot to learn about the toy business.

Funny, I never heard anyone call Unix a "toy" before, but you must be a mainframe guy.

With Windows, you can take an install disc, and apply any combination of service packs, updates, hotfixes, etc., and then burn it back to a new disc. When you install from the new disc, all the items you 'slipstreamed' are already installed. It is very convenient for businesses that want to have certain drivers or patches already installed.

And with every copy of Windows, you are exposed to the myriad viruses that have cost businesses hundreds of billions of dollars that MS has never "taken responsibility" for by pulling all of their discs from store shelves. Nice description of slipstreaming, though.

 

[norwaypianoman]

I have an idea:

If everyone start their posts about updates like this with a sentence f.ex.

I have 10.6.2, and I am a developer.

I have 10.6.1

or
I am a developer, I tried this

or I am only commenting.

It will be very interesting to read the comments from those who actually installed this, a bit more organized...

 

[beg_ne]

Meh, do you guys really think the update will be out as early as tomorrow? Is it even reasonable to expect that, since the latest seed only got seeded to developers today?

It's possible. Apple may want to push it out simply to have something in the headlines to go against the Windows 7 launch. Since there are no 'know issues' listed in the seed notes this release could basically be a final release candidate and if no developer reported any show stopping issues they may just push it out on Thursday. Basically these updates can come out at anytime, I believe one or a few for Leopard even came out on the weekend.

 

[wizard]

Interesting.

According to those with issue in the link that I posted, it has been been sent to apple several times, but with inconsistent reproducibility as one might assume. The fact is that my drives work pristinely on Leopard, so I am lead to believe that Snow Leopard is the cause. Of course, the issue may be in the hands of WD and certain compatibility issues, but not just their drives are part of the group experiencing problems. In any case, none of the fixes they have come up with at the apple forum have helped me, unfortunately. It's always good to see the response from other people though, because this may still be something wrong on my end, though I feel I've exhausted every avenue short of getting my mac checked.

I'm not sure if this will help but I'm running an early 2008 MBP with a WD Firewire drive connected to the FireWire 800 port. I've yet to have problems. I'm wndering how old your FireWire drives are?


Dave

 

[gorjan]

Cite an example, please -- an example of a video game bug that only affected a few people, was easily avoided and where every console could reasonably be expected to be connected to the internet where the customer could easily download a free patch. Let me save you some time: there is no such example.

PS3, upgrade to FW3.0 broke Uncharted 1 for some people. Easy upgrading to FW3.01 over the internet fixed the problem. There you have it...

I havn't had any problems/bugs in SL but for the record, if MS had made the same bug (guest account deleting all your data), you would have screamed your lungs out.

 

[Full of Win]

I think the need to bring back Sherlock from 10.4, so he can solve the Case of the Missing Dock.

 

[wizard]

I don't buy your point of view.

Both ways of what? I'm afraid I don't see your point here. How does interest in technical data on the bug relate to Mac users not being technically oriented? Does Mac OSX run on fairy dust?

There is a conflict in what you are saying. You are demanding technical data then a moment later you say Mac users can't understand such materials.

The OS also shouldn't delete their data. Customers do have a reasonable expectation that their system software isn't working against them.

Users are also advised to BACKUP their data when doing an OS upgrade or installation. If they can't do that or won't I have no pity for them.

These is completely a situation where you can REALLY blame Apple. If it isn't, I'd love to hear your example case.

The bug is certainly an issue of Apples, properly prepping for a system update is a system's owner responsibility.

You would have us believe that Apple has no responsibility for anything, because they can just issue a software update. If the update isn't installed or not available(like right now), too bad for the customer?

Yep, now you understand.

I have an issue with a company that charges for security updates.

I have an issue with companies going out of business, which by the way is a huge security issue.

There should be an expectation that a billion dollar company doesn't ship software that deletes all the customers data. NO EXCUSE.

Well considering Microsoft/Danger has a vastly larger screw up on their hands I don't think company size has anything to do with this problem. As far as BSD goes they had a bug that was in the code for 25 years that was just corrected recently. Does a 25 year old bug fix relieve the user of the need to backup? As to Apple do you believe Mac OS/X will be 100% reliable after this update?

The fact is people have been loosing data on PCs since they where invented. The way to avoid that is to back up your data. This won't be the last time a slip up causes a system failure and the size of the company has no impact on this happening or not.

As long as Apple fixes the problem I don't see where the users can have much to say. The users might not be happy but reasonable people realize that there is no such thing as a 100% reliable computer.

Dave

 

[nmv1973]

Back to Leopard 10.5.8

After lots of attempts and fresh instals of Snow Leopard, i decided to go back to the "keep it stupid and simple" Leopard (last buid) for two weeks now.

Follow up - no issues what so ever, everthing just works.

Faster Boot
Faster App access
no Crashes

Quick time 7 Pro ( Perfect )

So... Until there is a positive trend in this all new seed and bug fixes i´ll wait paciently.

Regards, to all of you

--------------------------------------------------------------------------------------
Macbook Pro UNB 2,53 Late 2008
4 GB DDR3 Ram
128 GB SSD Falcon

 

[RED™]

I only hope they bring back the old Expose with this update. If not, then I'm downgrading; I can't stand weird window arrangements/resizing much longer.

Why in the world should Apple do that? Dock Exposé is one of the biggest advertised feature of Snow Leopard. I'm sure they are not killing it with a software update - ever.

I assume you knew about that feature before upgrading, didn't you?

 

[Fulgham]

Mail
Safari
Go to this site.... http://radar.weather.gov/Conus/full_loop.php
Loading will take 12 seconds plus to complete
Animation will take nearly 2 minutes to happen
User input will be delayed about a second from real time
CPU usage will spike to 50% plus
MBP fans will hit 6,000 rpm

Both problems have existed for a couple of years.

Jim

This does not happen on my MBP

 

[mcarling]

I'm running 10.6.1 and I'm a former developer.

My view is somewhere between that of wizard and Amdahl.

I see five possible choices for Apple to take:

a) Continue producing and shipping 10.6.0 disks to retailers.

b) Stop producing 10.6.0 disks and start producing and shipping to retailers 10.6.2 disks. Direct the retailers to continue selling the 10.6.0 disks until stocks run out before selling 10.6.2 disks.

c) Stop producing 10.6.0 disks and start producing and shipping to retailers 10.6.2 disks. Direct the retailers to sell 10.6.0 disks only if they are temporarily out of stock of 10.6.2 (or later) disks.

d) Stop producing 10.6.0 disks and start producing and shipping to retailers 10.6.2 disks. Direct the retailers to send back any unsold 10.6.0 disks after they receive the 10.6.2 disks.

e) Immediately direct retailers to send back all their 10.6.0 disks and tell customers to be patient until 10.6.2 disks become available.

In my opinion, options a) and e) are completely unreasonable.

 

[cjmillsnun]

You seem to be missing the entire point on this particular case. The thing is, you CANNOT apply the 10.6.2 patch without having to install the Snow Leopard 10.6.0 first, since 10.6.0 is on the retail DVD.

The issue with the data loss is when a user upgrades from 10.5 LEOPARD to 10.6 SNOW LEOPARD, the data loss may occur. If you've only got a 10.6.0 Install DVD, you have no choice BUT to use that version, as there is no physical way to put the 10.6.2 patch on before.

I am all for keeping a system updated, and I have all my home & work systems patched and updated at all times. This is a case where being proactive with updates does not apply.

As long as you don't log in as a guest before you update then you will not experience data loss. Therefore there is no need to recall 10.6.0 media.

 

[revs]

Even if you do login as a guest you wont just lose your data - its a specific bug with specific circumstances!

I have been logging in and out as guest with 10.6.1 for weeks... everything fine. Then again, I have backups.

I have yet to read any reports of a single person being affected by this bug.

If it was that widespread/serious there would be a massive whining thread here on MR.

 

[Shuttleworth]

I'm not sure if this will help but I'm running an early 2008 MBP with a WD Firewire drive connected to the FireWire 800 port. I've yet to have problems. I'm wndering how old your FireWire drives are?


Dave

Mines about 6 months old, it's an external FW400 enclosure with a JMicron controller, one of these:

http://www.storagedepot.co.uk/Hard-Drive-Cases/sc884/p216.aspx

It worked fine with 10.5, it has our Aperture Library on it. On updating to 10.6 Aperture got really slow, importing took forever, as did closing the app. Initially I assumed it was an Aperture problem, but then I tried using finder to copy to and from the drive, and it was taking forever to move very small files, like an hour to move a dozen JPEGs.

I reconnected the drive using the USB (thank goodness that was an option) and the dive works as it should.

 

[SmugMac]

Interesting, so 10.6.2 is clearly a major update - not like 10.6.1, great.

Hope the update is released by Friday

 

[skate71290]

I hope it clears up the problems I'm having with my Magic Mouse

really problems with magic mouse? is that sarcasm cant really see it in text lol, on a side note is it a big improvement?

 

[fhall1]

Mail
Select Preferences
Select Rules
Select Create Rules
Select Conditions
Create 25 conditions plus
Conditions Window will extend off the bottom of the screen... taking button Cancel and OK off screen.
Click Condition Window resize and Rules Window, one level below, will resize.

Safari
Go to this site.... http://radar.weather.gov/Conus/full_loop.php
Loading will take 12 seconds plus to complete
Animation will take nearly 2 minutes to happen
User input will be delayed about a second from real time
CPU usage will spike to 50% plus
MBP fans will hit 6,000 rpm

Both problems have existed for a couple of years.

Jim

Hopefully you've reported these to Apple and not just posted them on forum boards?

 

[aardwolf]

I love how they say "no documented issues" when I have several outstanding issues that I logged in the original Snow Leopard beta that remain unresolved to this issue.

So, it doens't count as a bug if they pretend there's no open active ticket???

 

[JavierP]

I love how they say "no documented issues" when I have several outstanding issues that I logged in the original Snow Leopard beta that remain unresolved to this issue.

So, it doens't count as a bug if they pretend there's no open active ticket???

No known issues == we fixed all the 10.6.2 target bugs + there are no regression bugs that we know

It doesnt mean that they have fixed all the bugs that they know to exist

 

[Jacquesass]

I have an idea:

If everyone start their posts about updates like this with a sentence f.ex.

I have 10.6.2, and I am a developer.

I have 10.6.1

or
I am a developer, I tried this

or I am only commenting.

It will be very interesting to read the comments from those who actually installed this, a bit more organized...

I agree 100%. Each of these threads goes hundreds of posts - but nobody has even tried the new build.

Along the same lines, I think it would be VERY helpful if people stop posting their random pet bug without detailing HOW they installed SL. Did they upgrade or clean install?

I installed the hard way, repairing permissions, then backing up to two drives, then clean installing on the main drive, then moving over relevant portions of my user account, then reinstalling what programs I actually used (and waiting to install SL versions if at all possible). Not only did I regain >40GB of disk space, I haven't had a single problem. Given that most people with bizarre bugs solve their problems after a clean install, I'm suspicious how many people with issues just popped in the disk and hit "Install"...

 

[Shuttleworth]

Given that most people with bizarre bugs solve their problems after a clean install, I'm suspicious how many people with issues just popped in the disk and hit "Install"...

It should just work no matter how you install it, either that or give a big warning when doing it as an upgrade. I'm sure the official Apple line would be that there is no difference either way.

 

[macintoshtoffy]

I'm hoping that some of the GPU performance regressions have been fixed with this update. I'm also experiencing degraded FireWire hard drive performance, although I suppose that I should be thankful that my hard drive works at all since I know that some are experiencing issues on that front.

Agreed. I'm sitting here with an Intel GPU and I hope that the new 64bit driver included with 10.6.2 has also resulted in a revamping of the driver to improve the performance. Hopefully the improvement in the shared components will wind their way back to driver performance.

I can't wait till it is released; hopefully iWork '10 is released soon and it has an integrated bibliography function

 

[HiVolt]

Alright. I ignored your first few ignorant rants, but now I've had enough of your ridiculous FUD. Everything I've read about this bug says that it's only reproducible under *very* specific circumstances. You have to log into a guest account and then log back into your regular account, with some kind of preexisting corruption or permissions issue.

So a 100% reliable method of avoiding it during an upgrade is already known: don't log into a guest account and back into your regular account *during an upgrade from 10.6.0 to 10.6.2* for some totally bizarre reason. If you want to play it extra safe, make sure guest accounts are disabled until 10.6.2 is installed.

Yeah, it's a nasty bug for the handful of people who experienced it. Fixing it obviously needs to be a top priority. Apple acknowledged that about 10 days ago and a fix is coming in a few more days.

But no, that's not good enough for you. Even though you have no rational explanation of why Apple should incur massive losses by pulling *all* 10.6.0 retail disks, you won't be happy unless they do.

You need to take a deep breath and get a little perspective on this. No one is dying or in any physical danger here. A few people have suffered catastrophic data loss, and that sucks. But now we all know exactly how to avoid it: don't do something you would probably never do anyway. Hardly sounds like a crisis to me.

And if you know something I don't and you believe this bug is more widespread and/or not specifically triggered by using guest accounts, please post a link so we can all learn more about it.

LOL, I was not the one that suggested any recall of the discs. Read the thread. I am not spreading any FUD. Get off your high horse and put down the spiked kool-aid.

 

[aardwolf]

No known issues == we fixed all the 10.6.2 target bugs + there are no regression bugs that we know

It doesnt mean that they have fixed all the bugs that they know to exist

The bugs I've logged are in fact regression bugs, and they certainly know about them.