Still no fix for dropped Wi-Fi after waking up from sleep... I spent 15 minutes (really, I timed it) this evening closing and opening my MBP's lid until I could finally connect to my wireless router (which is literally 7 inches to the right of my MBP).
If you don't know what I'm talking about, read this: http://osxdaily.com/2011/11/06/lion-wi-fi-problems-solution-... - About 300 people have posted on that topic, it's really widespread yet it hasn't been fixed after 15 months. You can also google "lion wireless problems" to see literally thousands of post on online forums about this problem.
And a good news to all fellow iOS users: This "feature" (read "cancer") has spread to iOS 6 betas as well.
I have found ever since upgrading to Mountain Lion that waking up is iffy in general. The login screen displays, but it can take anywhere from 10 seconds to several minutes before I can type in my password. Sometimes it takes so long I just force the machine down and reboot instead.
I had the same issue on my iMac and it was really annoying. I found that un-checking the box that reads "automatically connect to networks" (or something to that order) helped fix my issue. It may work for you too!
If the cause of this on your machine is the same as on mine, I know why it happens and a (fairly awkward) workaround.
My MacBook does this whenever some process runs away with all the CPU cycles, sometimes it takes ages to properly wake up and log in and sometimes it doesn't manage it at all.
The work-around is to SSH in from another machine and kill the process that's hogging the CPU. Your MacBook will spring back to life! (Assuming, as I said, that we are experiencing the same issue - I only know for sure that we are experiencing the same symptoms)
If this does prove to be the cause, if you know or suspect a process is going to use a lot of CPU, to keep the system stable and perky you can either launch it from the command-line with "nice", e.g.
$ nice ./some_beastly_script.pl
Or if the process is already running, you can "renice" it:
$ renice $PID
Both of these will give that process lower CPU priority, stopping it bogging down other things.
I've mean meaning to look into the possibility of making essential things like the screensaver / unlock / core OS bits have higher priority than anything else, I'll write it up if I figure anything out.
I'm getting the same on my new rMBP. It shipped with Mountain Lion and an SSD installed, so I expected waking up to be almost instant, but it takes at least 5+ seconds for the screen to update (battery/clock display old info) or I can input my password.
I also get a lot of graphical glitches (mostly in Safari).
Safari 6 is awful. I find that I have to close all of my tabs, quit it, and reopen at least three times a day. Never had this problem with 5.x. Also, the developer tools are so unusable for me that I've started doing my web design work in Chrome just to get a sane, tolerable HTML/CSS editing experience.
I like Cmd-[0-9] to map to my bookmarks, I like Safari Reader, I like iOS-like zoom (chrome only fakes it, and does so not very well), I like the rendered text on Safari a million times better (it's not anti-aliased on Chrome on most pages - at least that's the miserable state Chrome was till v19 I think), I like iCloud tabs and I like Safari's UI much better.
That's why I use Safari. I couldn't possibly live with Chrome even if Safari was worse that it - I absolutely hate the stupid download bar, or "Downloads/Preferences" not being standard windows but silly webpages. And don't get me started on custom contextual menus Chrome team thought were cooler than standard OS X menus (even if they were cooler, they're at least 5 times slower. So what's the point of them?)
That said, it all comes down to what your personal preferences are. The difference between browsers are not huge. Some like Safari, some like Chrome, and some like Lynx.
* Chrome changes the font size; it doesn't zoom the page. At least in v22.
* I don't see the usefulness in tab access. To each their own.
* Chrome on iOS doesn't have access to Nitro.
* Come again? Reader is the Safari feature adapted from Arc90's Readability bookmarklet.
* Right.
I've got this too. And strange problems with the Finder/Dock. Stuff like clicking a folder or the trash can not opening it, not being able to empty the trash, and programs that are running not showing up in the cmd-tab switcher. No show stoppers like the WiFi bug, but it's still disappointing.
Strange- this issue dates back to at least snow leopard for me. I remember thinking it was tied to my setting the screen saver to lock the screen/slow disk. I live with it but would love to see it fixed.
For me this is a new MBP with an SSD. With Lion I could open the lid, immediately type in my password, and be back on wifi instantly. It was probably my favorite thing about the machine. Now waking up has become rather frustrating. I'm considering going back to Lion until this is fixed.
I 'fixed' this: create a shell script that pings your router every 30 seconds and add it to your launchagents. It forces the wifi to stay alive. Let me know if you'd like me to post more on how to do this. I've had this problem since Lion and my wifi hasn't dropped for months now.
I have bluetooth off on my Air and it still has this wifi issue. Its some race condition because it doesn't happen all the time and for it only happens when waking up from a deep sleep(ram persisted to disk).
There was a similar issue with Snow Leopard and I would not doubt others had it with Lion. What irked me in my case was my first year i5 iMac (the i5 in twenty seven inch form) was perfectly fine until I upgraded. Then suddenly wireless may or may not work upon waking from sleep. The odd part was, it might work for a few seconds after waking before I would have to manually end it and connect again. It was talking to the Airport Extreme just fine, it could not get beyond it.
The kicker, the copy of windows which I ran through Parallels could connect. I could surf sites and VPN through Windows in a VM while OS X applications could not, until I bounced the wireless connection.
There was definitely some wifi drivers problem in the original Lion. I wrote a fairly popular blog post summarizing reported solutions to the wifi problem in Lion and what solved it for me: http://thoughts.maayank.com/2011/08/wireless-problems-with-m...
I wrote it a long time ago, but maybe it will still give you (or others) leads to a solution. FWIW I haven't had any major wifi problems since the first or second Lion update.
That matches my experience, too. I had dropping problems when I got my MBA (mid-2011) and it magically fixed itself sometime after Lion shipped. I have no problems now.
It was a major disappointment for me at the time as after years with Linux I bought a Mac exactly because I wanted to focus on my work and not on solving fringe kernel issues. Luckily, no major problems since then.
Resetting the SMC [1] on my Macbook Air (late 2010) seems to have fixed the wifi issue. Obviously, no guarantee that'll fix it on yours...
Unfortunately, I've had all sorts of other, less intermittent issues with Mountain Lion. Finder is extremely sluggish (beachballing a LOT), sleep can be iffy, and will cut in while a Time Machine volume on network share is mounted, leaving it in an unclean state and wanting to delete all my backups (!!!) and start over. (I've thus far worked around it with a full fsck and deleting only the most recent snapshot and updating the plist file to reflect this, but that's not really a solution as it takes a few hours at a time to do the fsck over the network)
I'm also getting far worse battery life than before, as the system has 5-10% CPU utilisation when idle for no apparent reason.
I'm hoping these have improved with 10.8.1, otherwise I'll revert to Lion and think about switching back to Linux in the medium term...
"To fix this, I removed all the remembered locations and then in Configure Network Prefrences -> TCP/IP changed Configure IPV6 to Link-local only."
EDIT: It did seem to make things better for me, where after waking up from sleep it at least automatically reconnects, but it is still not same as Lion I think.d
I had no issues in Snow Leopard, but had the dropped Wi-Fi after wake up from sleep on all Lion with my iMac/Atheros chipset and Cisco wireless n router. Had tried downgrading to 10.6.4 Atheros driver, etc, etc, etc, from the apple forums, and nothing worked.
I decided to try something I shouldn't have had to and bought an Airport Extreme.
No more issues. I've since sold the Cisco N router -- that had worked perfectly with every other wifi device in the house, including this same computer before Lion.
I bet people will continue to give this suggestion as an attempted fix to random problems long after all memory of what it was actually for will be lost (i.e. classic environment screwing with HFS+ extensions introduced by OS X).
To be fair, munged permissions are a real problem; Just the other day, Parallels released an advisory document[1] about an issue their users had been seeing related directly to filesystem permissions.
I believe that "fix permissions" scans the installed package receipts and corrects the file permissions where necessary. In a world where any errant package install can mangle modes and ownership, fix permissions will not go derelict.
What it's actually for is the fixing of mangled permissions.
Are you on Mountain Lion? I couldn't use Mail.app on Lion as it was incredibly slow. The I realized it wasn't Mail.app's fault, but GPGMail's, and now that GPGMail has stopped working in ML my Mail.app feels as snappy as ever.
Turning Airport off and on doesn't seem to fix the problem for me, so I have to close the lid. My father's MacBook on the other hand only gets fixed when you turn off/on the Airport from the menu bar.
I truly love my MacBook Pro from late 2008: "pry-it-from-my-cold-dead-hands-unless-I-get-a-new-machine" love. But I still get that anxious knot in my gut when thinking about upgrading OS X, for one reason: when problems are discovered and reported, Apple will simply hang you out to dry.
Specifically, that machine had known issues with the GPU and dual boot was spotty because the fans would not run in Windows unless you manually started them in OS X. For YEARS, users begged for help and got nothing from Apple, and in some cases, Apple even actively FOUGHT them (e.g. http://www.macrumors.com/2012/04/19/blogger-victorious-over-...). All this to avoid looking like they were anything less than perfect.
I know - waaaaa!. It's still an awesome machine (and OS - I love and hate all platforms in one way or another), but it's a shame that Apple has earned the reputation that Jobs so famously put a face on when he felt personally challenged over these complaints: it's not broken, you are using it wrong, get over it - it's just a machine. It's a tough position to put the consumer in when you are a company that expects that customer to cede so much control in the name of "trust our authority".
I feel the same way about my early 2009 Macbook Pro. One reason I love it is because I have easy access to the battery should I need to replace it, and I even have easy access to the hard drive bay.
I just upgraded ~30 minutes ago, still at 98%. It's a good sign, but I was worried when there was nothing about it in the notes. Will report back when it's closer to 50% or so (I've been getting ~4-5hrs after a typical 8-9).
Edit: So far with half brightness and daily apps open (Mail, Safari, iTunes, Terminal > vim, TextMate) OS estimates 7:39. It feels like it's still going a little quick, but I could be wrong as I don't always leave iTunes or Safari to do their business.
Mid-day followup: original post at 1pm, had been running for ~30m.
Current time... 4:05... close TextMate, open InDesign. 56%, est. 2:22 remaining (obv. due to InDesign, even with a small file). No change in brightness.
I've found Safari to be much MORE reliable, if for no other reason than playing HTML5 video made Safari crash reliably in Lion, which doesn't happen in Mountain Lion.
Specifically, HTML5 video via the YouTube5 extension was fine. Also, HTML5 video that YouTube and Vimeo voluntarily showed me was fine. HTML5 video on The Escapist was not fine, and would crash somewhere between immediately and 30 seconds in (sometimes, but rarely, longer, but never so long as a minute).
This made AllThingsD especially frustrating to deal with, because they have HTML5 video straight on their front page, and while it doesn't auto play, it would cause the webview process to go into a crash loop until I closed that tab between crashes. I felt especially bad for my laptop (and the web server) when I opened a new tab to AllThingsD and went to get some water and it crashed 15-20 times in a row.
Now? Everything works great. Faster, smoother, less crashy.
That's interesting. I just moved back to Safari because ever since Lion, Chrome has been totally unusable for me.
The Flash/Shockwave that they bundle in consistently pegged my CPU after a few minutes of use. The whole desktop would get laggy and sluggish, to the point that I could barely operate the Finder enough to do a Force Quit. After a year of trying all kinds of things to fix/mitigate it, I just gave up and went back to Safari. Weird, since I rarely hear complaints from others about Chrome, but for me it was unusable. Even tried a fresh OS install to no effect.
As a user of the OS, in my experience it's absolutely a bug. Now whether or no Apple is going to own up to it or just insist "No it's a feature!" and declare victory is another story. Right now it's looks like they're going with the unfortunate fingers-in-the-ears, 'lalalala I can't hear you' response. Not their finest moment.
Obviously the functionality of it is terrible, I don't get it at all. But how something so large would be overlooked is near impossible. Not a single developer/tester had a dual monitor setup? Unlikely.
Just because you don't like how it works, doesn't mean it's a bug.
>Just because you don't like how it works, doesn't mean it's a bug.
OTOH just because Apple closes the bug 'as designed' doesn't make it a non-bug. Five seconds with Google tells you that it's a bug in the eyes of a vast number of users.
With multimonitor setup the apps are allowed to use those extra monitors while in full screen. You're supposed to be able to drag pieces of the apps into them if the app supports it.
It actually seems like there's a way around this on an app level-- I downgraded iTerm2 from the current 1.0.2.whatever to the 1.0.0 stable, and Full Screen properly takes up one screen on 10.8 instead of filling my other monitor with felt.
No... the new APIs take over all monitors. When you use the fullscreen apis, you can then target your windows for the other monitors. No body does so you see crosshatch pattern on them. If you download final cut on MAS and fullscreen it will use both monitors.
The problem is that fullscreen gives developers all monitors because the feature is supposed to encompasses the user entirely in one app experience, throwing out the multitasking concepts. It's like distraction free mode in many editors and follows the iOS concept of one App at a time. Apple allows the developer to use all the monitors when in fullscreen the way they want in the app but less than 5% of the fullscreening apps actually do anything with the other monitor. This unfortunately isn't the pattern that many users want especially when less than 5% of the fullscreening apps do anything with the second monitor mostly using the full screen mode to help 11 inch MBPAir users effectively use space.
Given that, fullscreening windows without the Apple API (as was done in older Mac versions) will still work but it's tricky and many apps didn't behave perfectly. The new API while not perfect is simple and just works for most devs, so they use it.
Without a doubt, 1.0.0 stable came out (I think) before 10.7. That said, it's my preferred functionality, so I'll gladly take it if it means it doesn't consume my second monitor like some sort of vermicious knid.
Upgraded the day it was released, last few days I feel that you could cook an egg on my MBP after 2 hours of working (nothing fancy, IDE and browsers open - no heavy GPU usage). Do more people feel that 10.8.x overheats the machine?
This has been a huge issue on my mid-2010 MBP and others have reported the same on Apple forums. My MBP has been overheating, throwing up artifacts all over the screen and freezing requiring a hard reboot. So far so good though... fingers crossed.
I'd completely forgotten that they'd changed the name. As someone who grew up with 'System 6' and 'System 7', it feels weird to chop off so much of the name all of a sudden.
Also, saying 'OS Ten' out loud just seems generic.
> Also, saying 'OS Ten' out loud just seems generic.
I've long wondered when Apple would bump "OS X" to something like "OS 11" or just make OS "Ex" the official pronunciation. I figured they would "pull a Solaris" and claim "OS 11" just meant "OS X 10.11.0". Now it seems like it will become "iOS" everywhere.
I never had this problem when I was using Snow Leopard, but since I've updgraded to Mountain Lion, every time I wake up my computer, the Wifi freezes. What are developers doing to fix this problem. I'm getting tired of force rebooting in order to connect.
Does anyone know if this fixes missing icons? My MBP 2011 will come up with the wifi or other random icons hidden (I can still click on where they 'would' be and it'll show me the wifi networks, for instance)...
It does not. OS updates are still delivered via Software Update, not through the App Store; ML simply integrates the SU GUI into the App Store app. For instance, I updated my 3 ML Macs to 10.8.1 this afternoon with the softwareupdate command-line tool, pulling the update from a local Software Update server, neither of which would have worked had the update only been available through the App Store.
Note that there's also a distinct 10.8.1 update to "Install OS X Mountain Lion.app", and that this is only distributed through the App Store — but this just slipstreams the Mountain Lion installer, and is neither necessary, nor even useful, for updating existing 10.8 systems to 10.8.1 (unless, of course, you choose to "update" by reinstalling the whole OS!).
Nope, I just installed the OS update on a machine that has not been linked to an apple id. The app store also has updates for the preinstalled versions of iphoto and imovie, but those do require an apple id.
If you don't know what I'm talking about, read this: http://osxdaily.com/2011/11/06/lion-wi-fi-problems-solution-... - About 300 people have posted on that topic, it's really widespread yet it hasn't been fixed after 15 months. You can also google "lion wireless problems" to see literally thousands of post on online forums about this problem.
And a good news to all fellow iOS users: This "feature" (read "cancer") has spread to iOS 6 betas as well.