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.8.2 Experiences - share here
- Thread starter iOrbit
- Start date
- Sort by reaction score
No Problems
Installed a day ago 10.8.2 on my MBA 2012 i5 11": No problems at all. Too early to tell impact on battery life. Was only working for two hours on battery and still had 80%.
Installed a day ago 10.8.2 on my MBA 2012 i5 11": No problems at all. Too early to tell impact on battery life. Was only working for two hours on battery and still had 80%.
Fans are going nuts the entire time on my 2011 MBP. Didn't on 10.8.1.
Going to have to restore from backup
Going to have to restore from backup
The changelog for 10.8.2 includes the item, "Ability to pre-authenticate a FileVault protected system."
http://support.apple.com/kb/HT5460
Could someone explain exactly what that means?
http://support.apple.com/kb/HT5460
Could someone explain exactly what that means?
Updated my '11 mini and '09 iMac. Both went without a hitch, although I did have a problem on my iMac with iPhoto 9.4 crashing on launch. I was able to rectify that by deleting "com.apple.iPhoto.plist" from library/preferences.
Anyone else had freezes after installing Mountain Lion? https://forums.macrumors.com/showthread.php?p=15760069#post15760069
I noticed when time machine is doing a back up the TM icon that used to show up on my desktop is no longer there. No buggy, but I got used to seeing it and knowing that a backup was in progress because most of the time I really blank out any sounds coming from my MBP.
10.8.2 won't let me connect to an external monitor with the internal display off (clamshell mode without the clamshell
I tried re-entering the terminal command followed by a restart, but no dice..anyone else seeing this?
Have you had this fixed?
my rMBP also is not working in clamshell mode when connected to an external monitor
Facetime and Messages not working
Opening up either produces a stupie message saying
An internal <Facetime/Messages> error has occurred. It needs to quit and restart.
or something like that. Click OK and it shutsdown. I restart either program and same error.
Apple tech hasn't been able to resolve the issue and no one on this forum either.
I really don't want to do a fresh re-install and for those two programs I don't plan to, sadly.
Opening up either produces a stupie message saying
An internal <Facetime/Messages> error has occurred. It needs to quit and restart.
or something like that. Click OK and it shutsdown. I restart either program and same error.
Apple tech hasn't been able to resolve the issue and no one on this forum either.
I really don't want to do a fresh re-install and for those two programs I don't plan to, sadly.
unfortunately not, but I did find a kind of work around. On my MBP, I don't close the lid all the way, instead leaving about 1 1/2 inches of space between the palm rest and the display lid. This engages clamshell mode, turning the internal display off. It enables me to get a great wifi signal, and I'm sure the heat dissipation is better then having the display closed. One caveat is that I'm on a 13" pro, don't know if it works on the rMBP :/
Ok waited till today to try and update my Mountain Lion partition on my 2010 MB. Within about ten minutes, I started getting lockups with spinning wheels all over again. It's unusable for me. I rebooted and went back to my Lion partition. I'll try again next update.
If you guys had the option, would you wait until 10.8.3 and stay on Lion in the meantime or go ahead and download 10.8.2 even despite the faults you guys are discussing?
I'm still using 10.7 and was going to upgrade, but these issues makes me think it might be worth waiting till 10.8.3 came out and just stay on Lion. Are the pros of ML worth putting up with these bugs if someone's content with Lion for now?
I'm still using 10.7 and was going to upgrade, but these issues makes me think it might be worth waiting till 10.8.3 came out and just stay on Lion. Are the pros of ML worth putting up with these bugs if someone's content with Lion for now?
In my opinion wait until the issues are fixed in ML. At least for me I am running 10.8.2 and its seriously buggy - some examples: Xcode crashes randomly, notes crashes upon opening (cant even use it), safari has strange web page glitches and scrolling is terrible, mail stops me from shutting down (I have to force quit) AND email comes through super slow compared with my iOS devices, I also have had random complete system freezes and have had to hardware force shutdown. These are just a few that come to mind. Generally I feel the OS is unstable. I was using 10.7.4 before which came installed on my rMBP and it was stable. I regret updating, however who was to know..
Cheers.
I'm fine using Lion for however long it takes to get the ML bugs fixed. I have both Lion and ML installed in separate partitions so I can keep going back to ML with each update to try things out.
Lion reminds me of why I love Apple but ML reminds me of why I threw my last three HP laptops across the room breaking them into many pieces. I wanted to do that with a few Macs as well once or twice but the costs of each stopped me.
Same issues on my wife's new MBP. It came with Lion and I regret upgrading her to ML. She always sleeps her mac but the battery life is dismal. Sitting next to her in the same room she constantly gives me updates like, "100% an hour ago... now only 65%!.
Occasionally she'll add... "my $350 Dell was better!". She knows I get roughly 7 hours on my MBP but can't understand why her machine can't run Snow Leopard. (Says I'm lazy and lying.
)
Humma
I won't go into the things they removed from 10.8x (removal of some apache functionality for no good reason) but here's what I've found in 10.82:
-Mostly favorable: faster, seems like they focused a lot on transitions being faster or smoother.
-However, 10.82 introduced a new behavior where my machine would kernel panic (so far I believe this is the third time since 10.82 came out) whereas it never had kp'ed before 10.82.
-I also find that the CPU fan runs much faster/louder than it ever did before or disproportionately higher during medium/high cpu usage. 10.6, 10.7, 10.8-10.81 were all normal and 10.82 runs the cpu fan much faster. But not the superdrive fan or other fan in the iMac Corei7 2.8 ghz model.
I won't go into the things they removed from 10.8x (removal of some apache functionality for no good reason) but here's what I've found in 10.82:
-Mostly favorable: faster, seems like they focused a lot on transitions being faster or smoother.
-However, 10.82 introduced a new behavior where my machine would kernel panic (so far I believe this is the third time since 10.82 came out) whereas it never had kp'ed before 10.82.
-I also find that the CPU fan runs much faster/louder than it ever did before or disproportionately higher during medium/high cpu usage. 10.6, 10.7, 10.8-10.81 were all normal and 10.82 runs the cpu fan much faster. But not the superdrive fan or other fan in the iMac Corei7 2.8 ghz model.
I had an extended freeze yesterday evening. I was adding photos to a shared photostream and right in the middle of browsing photos everything except the mouse pointer froze. I was in a hurry and quickly got tired of waiting so I held the power button to reboot. I have 16 GB of 3rd party RAM in a late 2011 15.4 in hires MBP running 10.8.2.
I have not had any freezes on my mid 2010 mini (with 8 GB of third party RAM) running 10.8.2.
Interesting. I'll keep my original RAM handy in case this keeps cropping up so when I go see the Geniuses about it, I don't get asked why I didn't use Apple RAM.
I should note that when I was having frequent freezes with my 2008 MB, I took it in to a Genius Bar appointment and they rolled their eyes about the third party 4 GB of RAM I had at the time but they still plugged it in their network (it was so bad off, it couldn't even join the Apple's wide open wifi) and booted from their "known good" image to prove it was a problem with my software and or drive and not any of the other hardware on my machine. I pulled out the crappy Agility series SSD and took it back for a refund. No more freezes since then.