Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
No freeze

I've tried to replicate the freeze issue and have been unable to get my iMac 11 3.4 to freeze up.
Others that have stated that Lion should have never been released, well they're never going to know ALL of the issues until it's released to the public, and no OS upgrade is going to be free of all issues at release, if ever.
 
For those who installed it within hours / days of release, well it's just a little naive to expect everything to "just work" as it most certainly won't.

Your reticence to install at version x.0 is clearly a very sensible and pragmatic approach. As someone who works for a software company supplying enterprise solutions, I'm well aware of the "n-1" approach to software deployment in mission-critical environments. But such a view does not excuse those errors when they occur.

Furthermore, I don't consider it at all naive to have installed a heavily-promoted OS release on a piece of hardware purchased just two months ago. I consider it even less naive for the customers that purchased the hardware with Lion pre-installed (which, don't forget, is the same hardware I have).

Apple demonstrably failed to QA this one, and they should be held to account for doing so. Taking an apologists stance on this helps no one and I find it curious why any rational paying customer would.
 
@Danp, did you get Lion upgraded for free?

I paid for Lion through the App Store initially.

Those purchase costs are being fully refunded by Apple as a result of the sleep/wake bug that is impacting 2011 model iMacs.

As Apple have not indicated that I'm required to uninstall or downgrade my OS, I have in effect been upgraded for free.

I must admit I'm personally very satisfied with the response I've had from Apple on this issue. I am a little surprised they went ahead with the refund rather than just acknowledging the issue and providing an estimated fix date, however...
 
I've tried to replicate the freeze issue and have been unable to get my iMac 11 3.4 to freeze up.
Others that have stated that Lion should have never been released, well they're never going to know ALL of the issues until it's released to the public, and no OS upgrade is going to be free of all issues at release, if ever.

Suggesting that it isn't ready for release is a wild exaggeration and sounds grossly reactionary.

At worst, this bug calls in to question Apples pre-release testing, what with this impacting current shipping hardware and all. All pointers suggest that Apple knew about this issue throughout the development builds and didn't get around to fixing it.

I expect a few test managers have been hauled over the coals on this one!
 
Your reticence to install at version x.0 is clearly a very sensible and pragmatic approach. As someone who works for a software company supplying enterprise solutions, I'm well aware of the "n-1" approach to software deployment in mission-critical environments. But such a view does not excuse those errors when they occur.

Furthermore, I don't consider it at all naive to have installed a heavily-promoted OS release on a piece of hardware purchased just two months ago. I consider it even less naive for the customers that purchased the hardware with Lion pre-installed (which, don't forget, is the same hardware I have).

Apple demonstrably failed to QA this one, and they should be held to account for doing so. Taking an apologists stance on this helps no one and I find it curious why any rational paying customer would.

For those who got a Mac pre-installed with Lion - then perfectly understandable for them to feel let down. For those that immediately installed on release I still maintain they're some what naive. On the first day of release I got my Free Mac Up-To-Date Lion code but have just chosen to hold off for a while. It's common knowledge that a first release will be buggy so why jump ship so quickly? I agree one hopes that software releases are more solid when first released and TBH for the greater part Lion is working to an acceptable level, however the reality is that a few "major" bugs will initially be present before revision 1 and 2 are pushed out.
 
It's common knowledge that a first release will be buggy so why jump ship so quickly?.

Personally, for two reasons:

1. Implied minimal risk. Apple ship my hardware as new running Lion so I think it's reasonable to expect it will be a well tested combination.

2. I'm sufficiently technically competent to resolve or workaround any issues I might encounter (as I have).

But I don't wish to sound too negative here. Any grievance I had went away as soon as I got the refund. I await some official acknowledgment from Apple and the delivery of the fix and trust other users are not unduly impacted by this issue.
 
Personally, for two reasons:

1. Implied minimal risk. Apple ship my hardware as new running Lion so I think it's reasonable to expect it will be a well tested combination.

2. I'm sufficiently technically competent to resolve or workaround any issues I might encounter (as I have).

But I don't wish to sound too negative here. Any grievance I had went away as soon as I got the refund. I await some official acknowledgment from Apple and the delivery of the fix and trust other users are not unduly impacted by this issue.

Still, I maintain if your machine was running a stable OS, as in Snow Leopard, why jeopardise that by installing a first release of a new OS, as in Lion. Early adopters always bear the brunt of all the un-ironed out bugs which will eventually (sooner, rather than later one hopes) be sorted out. It's a reality check - people shouldn't be so eager to upgrade if they cannot accept that there will be inevitable issues.

Our IT guys at work are part of the Developers programme so have had Snow Leopard throughout all the Beta release yet they would never install it as there sole OS. Even now it's nicely partitioned off away from there day-to-day OS Snow Leopard installation.
 
Still, I maintain if your machine was running a stable OS, as in Snow Leopard, why jeopardise that by installing a first release of a new OS, as in Lion.

The impetus was for the upgrade was the well publicised 250+ new features offered by Lion, paired with the cheap purchase price and a curiosity to see it all in action.

I very justifiably had no sense of potential jeopardy in undertaking the upgrade because of the points I mentioned before. I mean, if Apple are selling the hardware/software combo new right this moment, then it's reasonable to assume it works and I don't need to wait.

In any event, neither you nor I are required to agree on this topic and I'm sure we both have more productive ways to be spending our time. If you don't, I certainly do :p
 
The impetus was for the upgrade was the well publicised 250+ new features offered by Lion, paired with the cheap purchase price and a curiosity to see it all in action.

I very justifiably had no sense of potential jeopardy in undertaking the upgrade because of the points I mentioned before. I mean, if Apple are selling the hardware/software combo new right this moment, then it's reasonable to assume it works and I don't need to wait.

Guess that's a lesson in "Don't Believe The Hype". 250+ New features and such like basically translates into marketing speak that one would expect with a new product launch - they're hardly going to tell you the downsides. Just for the record I'm keen to upgrade to Lion, just waiting for major bugs to be ironed out.

In any event, neither you nor I are required to agree on this topic and I'm sure we both have more productive ways to be spending our time. If you don't, I certainly do :p

This is all just harmless banter - no great shakes and no disrespect intended, just an exchange of views conducted in a adult fashion - I've enjoyed it even if you haven't.;)
 
Having the same exact problems with my 2011 iMac. No problems with my 2011 MBP, however. Both are running Lion. Sure the next update will take care of the problem.
 
I paid for Lion through the App Store initially.

"... the sleep/wake bug that is impacting 2011 model iMacs."

Like many of these issues, it only affects some. I have not had any problems of any sort with 2011 iMac that came with Lion installed.
 
I paid for Lion through the App Store initially.

"... the sleep/wake bug that is impacting 2011 model iMacs."

Like many of these issues, it only affects some. I have not had any problems of any sort with 2011 iMac that came with Lion installed.


It seems to particularly affect 2011 iMacs that came with Snow Leopard and then who upgraded to Lion. It may not be an issue with iMacs that come preinstalled with Lions.
 
This particular problem seems to afflict 2011 iMacs. Previous iMacs seem unaffected.


Not true.

My home imac is experiencing this same problem. A 2010 27 2.93 with SSD. All my imacs as well as my Mac Pro's and Mac Books, all have the same problem. Drops the connection. I own quite a few 20+. I have two 2011 imacs at my business and both experience the same behavior.

So I don't think it's just a 2011 imac problem. I think it's a Lion Problem.
 
This problem seems to have completely gone away for me since .1 update. How about you guys?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.