Hacker News Reader

Comment by city41 | Hacker News Reader

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.

View on HN

Same here: with Lion - open lid, type in password.

Mountain Lion - open lid, push first character of password, no response? keep trying again until asterisk appears, then type rest of password.

Another vote on this. Annoying "issue".

I close my lid and my MBP (last of the 17" line) never sleeps. Really frustrating.

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!

I have this problem as well; it's my most frustrating experience with Mt. Lion so far.

Where is that? I tried Spotlight searching for "automatically" and "networks" and couldn't find it.

If you just go to Network Preferences you should see it.

I noticed a simple solution: Wait for the mouse pointer to show, then you're good to log in

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 don't understand why anyone, least of all a developer, would use Safari.

Modulo the aforementioned issues, I think that the user experience is far superior to Chrome. Here are a couple examples:

    * 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

* Chrome has that.

* 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.

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.

Most of your complaints are flatly wrong. And some of them were never even accurate.

Just because you disagree with his opinion doesn't mean he is wrong.

No, several of the things he listed are literally lies or misconceptions or are factually wrong.

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.

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.

You have to press (not just tap) the touchpad. It will wake up much faster.

Reply on news.ycombinator.com