Mac OS X 10.8.1 is out.
support.apple.com
support.apple.com
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.
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.
"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
Mountain Lion - open lid, push first character of password, no response? keep trying again until asterisk appears, then type rest of password.
Where is that? I tried Spotlight searching for "automatically" and "networks" and couldn't find it.
I also get a lot of graphical glitches (mostly in Safari).
* iOS-like pinch/zoom
* Quick access to bookmark bar bookmarks with Cmd-[0-9]
* iCloud tabs (w/ Mobile Safari)
* Reader
* Better feedback on page back/forward gestures* I don't really see the usefulness. I prefer Cmd-[0-9] for tab access.
* Chrome syncs between my three computers, phone, tablet. It's not just bookmarks. It's everything
* Doesn't Safari not have a reader anymore?
* I guess it's a matter of preference but I get a nice arrow indicator for page forward and backward. The Safari effect is a bit much in my opinion.
* 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.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.
I don't know why he prefers the things he does, but I don't dispute that he may well feel that way, nor do I care that he does.
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 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.
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).
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.
But connection drops intermittently with me, not when waking from sleep.
And now I have this weird flickering cursor while typing in Mail.app
God I miss Snow Leopard.
7" - maybe you should invest in an ethernet cable...
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...
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".
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.
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.
Safari is crashing way more frequently than it used to.
Chrome is just too much better to even bother with Safari.
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.
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.
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.
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.
Definitely noticed the artifacts at 10.8 - haven't seen any during work today after updating to 10.8.1 though FC
OS X 10.8.1Also, 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.
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? OK.