-
All replies
-
Helpful answers
-
Jan 29, 2015 6:40 PM in response to vegeta777by Schwaggy,Ugh. I'm so ****** off. Not fixed for me on Early 2009 Mac Pro.
I wonder if Apple even tests against the older towers anymore. I figure they must test against any Mac that supports the OS, right?
This is annoying and is probably slowly killing my machine.
-
Jan 29, 2015 11:52 PM in response to babenesby patH72,On my 2012 MacBook Pro and recent Mac Pro 10.10.2 seems to have resolved the problem. There are still a large number of reports of discoveryd problems in the log, though.
It did introduce another problem, though. Whenever I launched an app whose icon was not already in the dock, the machine automatically mounted a remote Webdav volume. There was an alias to that volume in the dock, and removing it from the dock prevented this automatic mounting from occurring. So somehow the act of adding an icon to the dock was triggering activity with another dock icon. This is a fairly unusual problem, and it took a fair amount of time to figure out what was going on.
I think it's probably time to do another Snow Leopard, where instead of adding new features Apple just fixes all of the problems which seem to have gotten into the OS.
-
Jan 31, 2015 2:39 AM in response to James Brustby Oliver Matuschin,10.10.2 also finally solved the problem for me! On all my Macs!
-
Feb 1, 2015 6:08 AM in response to James Brustby pigo-monchi,Unfortunately this problem was not fixed by 10.10.2 on my Late 2013 iMac. Also reinstalling OS X didn't help. I also filed a bugreport for this issue now.
-
Feb 2, 2015 1:49 PM in response to pigo-monchiby Schwaggy,Well, as much as I don't think I should have had to do it.. A complete, fresh reinstall of 10.10.2 finally fixed this for me on my Mac Pro.
I used Time Machine to restore my Apps and Documents and settings so whatever was causing this, was deep in the OS.
Good Luck to All!
-
Feb 3, 2015 5:55 AM in response to Schwaggyby Aaron Stroot,I was able to successfully fix this problem, finally. I don't think it was unique to Yosemite because it was happening on my iMac long before Yosemite.
Anyways, it was either one of two things:
1) An install of 10.10.2
2) Disabling Google Chrome autoupdate. Follow the instructions via Google here. All it takes is one Terminal command.
defaults write com.google.Keystone.Agent checkInterval 0
I did both of these on two different machines and both stopped waking every couple of hours. I'm not sure which one actually fixed it, but at least that worked for me.
-
Feb 3, 2015 11:37 PM in response to James Brustby SiHancox,This is for information, it my help those with this Wake (RTC) issue or at least give hope! - running new iMac with clean install of Yosemite that has been upgraded twice through App Store to 10.10.1 then 10.10.2. I had two wake reasons only, namely RTC (Alarm) and XHC1, was not concerned with the later because it was BT related and times corresponded to when I touched the keyboard to manually wake the machine (have "Allow BT devices to wake this computer ticked). I also have canon printer connected wirelessly, WD hard drive via usb3 and internet access via wireless.
When in sleep would get RTC every hour as though the machine was looking for something, decided to look through "Preferences" to see what was enabled and found the following:
Energy Saver, Wake for network access
Enable Power Nap
iCloud, Back to My Mac
Find My Mac
I unticked all four and the machine now appears to sleep without the hourly checks - not sure which one (or combinations) was responsible but only see XHC1 now and that has always tied in with my start sessions on the machine.
Realise some may have more going on within there systems than I (different software or upgrade from prior OS), but if you have not tried the above it might be worth a go.
-
Feb 7, 2015 6:32 AM in response to mediahoundby tomihasa,I would like to get this fixed also. Without changing any system settings.
Mac Pro 8-Core (Early 2009). OS X Yosemite 10.10.2.
-
Aug 17, 2015 8:19 AM in response to Paardeslagerby Király,Try this. It should work on 10.10.4 or later. Enter the following in Terminal and then restart your Mac:
sudo defaults write /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist ProgramArguments -array-add -DisableSleepProxyClient
This command hacks a system file and may need to be re-entered if Apple issues a software update that "fixes" this hack.
-
Nov 16, 2015 11:30 AM in response to Királyby Bob4King,Tried it but it won't work. The message was "Could not write domain"
-
Feb 7, 2016 12:10 AM in response to Bob4Kingby Thierry6,Hi
Mac OS X 10.11.3
iMac late 2011
problem is there again.
-
Apr 5, 2016 9:11 AM in response to Thierry6by gellertsz,Same problem here.
Brand new Macbook pro early 2015 with 10.11.4.
-
Apr 5, 2016 10:45 AM in response to gellertszby Eric Root,Sleep - Why your Mac might not sleep or stay in sleep mode
Sleep - Won’t wake up/won’t stay in sleep
-
Jul 28, 2016 5:06 AM in response to James Brustby A.J. MACHETE,2009 white MacBook, running Mavericks, same issue. I wonder if it might have something to do with iTunes because, a time or two when I happened to catch it in time, I opened the MacBook to see an alert saying: "We could not complete your iTunes Store request. Please try gain later."
-
Jul 28, 2016 8:30 AM in response to James Brustby jamesfromflowery brench,Your. Computer is self aware now