November 12, 2009 11:47 AM PST
Snow Leopard slow to sleep
For users experiencing this issue, you can narrow down the cause of the slow shut down using a simple Terminal command. Open Terminal and enter:
pmset -g logThe "Signature" with the longest "Response Time" (in ms) should be the first program to look at. Users should be sure they have updated all their third party applications and plug-ins, especially after updating to Snow Leopard 10.6.2, to ensure the best compatibility.
Several users report that the GoogleTalk plug-in for Firefox or Safari was their culprit for the longest response time when attempting to put their Mac to sleep. Several other users also found that they had an outstanding print job in their printer queue.
Be sure to check us out on Twitter and the CNET Mac forums.
Do you have questions, issues, or stories you would like to see on MacFixIt? Email Us.
Joe is a seasoned Mac veteran with years of experience on the platform. He reports on Macs, iPods, iPhones and anything else Apple sells. Before joining CNET, he even worked in Apple's retail stores. He's also a creative professional who knows how to use a Mac to get the job done.
MacFixIt is a site that highlights issues that users report and provides solutions and suggestions when available. True, most systems do not experience most of these issues. My own machine, a MacBook Pro running Leopard has yet to experience any of these issues either.
But, the point of this site is to be a usable archive for Mac users that do have these problems. Whether the issue is entirely small or extremely significant (like when we reported on the Guest Login bug), our value is as a resource, not as a daily source of Apple fanboy trumpeting. Don't get me wrong, we love Apple and all their stuff and that is a huge reason why we choose to write for MacFixIt, but this is a troubleshooting site, which means we have to talk about "trouble". We, in no way, attempt to make anything we write about a "trend". In fact, many of the lesser "threats" we write about are noted as such.
If you have a bigger story you feel like we should be reporting on, feel free to contact us via the methods at the conclusion of each article we write. Thanks much!
You must be some kind of newby because MacfFxit has been the resource that many in the Mac community depend on for many years!
The tone of your comments is repugnant and ill informed.
I maintain one machine with the sleep issue. Apple would not acknowledge it. A few posters on Apple Forums began to complain about it, but MacFixit confirmed what Apple would not.
Count yourself lucky for not needing MacFixit!
2. Which Mac Pro?
3. Which display?
4. Did you try pressing the power button on the display? Check System Preferences>Displays>Options. It may be the computer is on but the display is not. I had to change my setting to ? Does nothing. [Even then, it may go to sleep and require more than moving the mouse to wake it - but that's a different matter.]
5. Have you talked to AppleCare?
-
by
December 4, 2009 7:14 PM PST
- After reading a lot of posts on different sites about this sleep problem, I ran across this advice to run the command
-
Like this
Reply to this comment
-
(12 Comments)pmset -g log | applicationresponse.timedout
in the terminal. This looks for processes that are stuck.
If you don't find anything with that, try:
pmset -g log | applicationresponse.slowresponse
That is similar but find some that are not totally timed out. Anything with more than a few thousand ms (milliseconds) listed there is suspect.
I found a timed out process related to "cups" which is the unix printing daemon.
I when into my Preferences, went to Printers & Fax, and found an "extra" printer named "_" ... I think that it got created when I installed Snow Leopard, and tried to print before I'd installed the upgraded HP printer drivers...
Anyway, once I deleted that printer, my sleep went from at least 20 seconds to almost instant.
I think a lot of people might want to check their Printer setups, and maybe their printer Queues for old printers and stuck jobs.
PS -- messing with the hibernationmode didn't do anything for me, so I put it back to "3", so I'll get the new hibernation sleep with everything saved to disk... that has saved my butt many times.