Automatic Startup

I don't know which .plist file includes your wakeup settings, but someone might.
I believe it's a matter of trashing the appropriate .plist file which may be corrupted or mis-linked.
I have done this with other apps that were not working properly. The system creates a new .plist for those functions or apps and makes all the settings default. You have to reset them as appropriate.
I see several .plist files for Preferences but no one specific for the Energy Saver, so I can't help beyond what I wrote, but I do think it might be the solution.

You might also check this post
http://daringfireball.net/2004/05/energy_saver

Message was edited by: nerowolfe

nerowolfe wrote:
I don't know which .plist file includes your wakeup settings, but someone might.

I'm not sure yet, but I believe the file may be /Library/Preferences/SystemConfiguration/com.apple.PowerManagement

This one won't be easy to remove with the Finder -- it is owned by system & even admin users have read only access.

R C-R wrote:

nerowolfe wrote:
I don't know which .plist file includes your wakeup settings, but someone might.

I'm not sure yet, but I believe the file may be /Library/Preferences/SystemConfiguration/com.apple.PowerManagement

This one won't be easy to remove with the Finder -- it is owned by system & even admin users have read only access.

Well thanks, that's probably the one. That's in the main Library, not a local user's Library which is why it has that ownership.
I am sure that's the bad file.

For what it's worth, here is a copy of mine for comparison:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ActivePowerProfiles</key>
<dict>
<key>AC Power</key>
<integer>-1</integer>
<key>Battery Power</key>
<integer>1</integer>
</dict>
<key>Custom Profile</key>
<dict>
<key>AC Power</key>
<dict>
<key>Automatic Restart On Power Loss</key>
<integer>0</integer>
<key>Disk Sleep Timer</key>
<integer>10</integer>
<key>Display Sleep Timer</key>
<integer>20</integer>
<key>Display Sleep Uses Dim</key>
<integer>1</integer>
<key>Hibernate File</key>
<string>/var/vm/sleepimage</string>
<key>Hibernate Mode</key>
<integer>3</integer>
<key>Mobile Motion Module</key>
<integer>1</integer>
<key>System Sleep Timer</key>
<integer>30</integer>
<key>Wake On AC Change</key>
<integer>0</integer>
<key>Wake On Clamshell Open</key>
<integer>1</integer>
<key>Wake On LAN</key>
<integer>0</integer>
</dict>
<key>Battery Power</key>
<dict>
<key>Disk Sleep Timer</key>
<integer>5</integer>
<key>Display Sleep Timer</key>
<integer>5</integer>
<key>Display Sleep Uses Dim</key>
<integer>1</integer>
<key>Hibernate File</key>
<string>/var/vm/sleepimage</string>
<key>Hibernate Mode</key>
<integer>3</integer>
<key>Mobile Motion Module</key>
<integer>1</integer>
<key>ReduceBrightness</key>
<integer>1</integer>
<key>System Sleep Timer</key>
<integer>5</integer>
<key>Wake On AC Change</key>
<integer>0</integer>
<key>Wake On Clamshell Open</key>
<integer>1</integer>
</dict>
</dict>
</dict>
</plist>

I have never used or set any wakeup. I did turn off the wakeup on LAN recently.
This file may be the one and if anyone with the wakeup problem has different entries, we might be able to find a way to modify the file without deleting it and creating another one.

I'm one of the guys with this issue, and your file looks about the same as mine. There are some values that are a bit different, like the time required before putting the computer to sleep automatically, but that is to be expected.

In my opinion, this file is NOT the culprit. I tried the RAM suggestion mentioned above, and I will report back if this method did or did not work.

I have always had my system set to sleep automatically - used to be set at 23:59, so I don't believe this is cause of my system waking at 1am

Have you noticed that all the systems affected here wake at exactly the same time 12am GMT, 1am CET & 8pm EST, be interesting to see if the US system starts waking at 7pm EST after they change their clocks at the weekend

I never had the option to turn on or shut off the computer automatically. Also, the RAM solution did not fix the issue for me. Also, my computer wakes from sleep within an hour of sleeping - NOT on the hour. So, it can wake up at 1:23 am, for instance, or 3:21 pm, as long as it is within an hour of sleeping.

Are we having different problems or the same one?

I have a half solution to the problem, i set my auto wakeup to only Mondays, and therefore it didnt switch on last night. Of course, this is not a cure, but it does mean it only happens once a week

P.S I called apple, and they were no help at all.

I you could set it for February 29 that would really be a long-term fix. 🙂
As an idea, you can find which file is causing the problem by checking the date stamps immediately after changing it, as you did. Look for a .plist file with the exact time that you changed the wakeup.
If you have a complete backup of your system, you might then trash that file and see what happens. But only if you have a complete backup.
On the other hand, if you make or have a bootable backup, you could trash the file on that one just to see what happens.
If this is not a common problem, a fix/patch is probably going to be a long time coming, so anything you find should be posted here.

I would like to let everyone know that the RAM fix that someone suggested above did NOT solve the problem for me.

Well, I'm glad to see that I am not alone, My MAC Mini has been doing the same thing since the upgrade to leopard. I turn the machine off when I leave. I have turned off every option having to do with scheduled start up's and shutdowns, wake up on administrator lan access and I fine my machine asleep in the morning when I get to the office.

My next experiment is to disconnect the LAN cable.

Maybe a ghost of tiger is affecting this! 🙂

This has to be some obscure bug in Leopard.

I guess we will have a solution here in the future.

MV

Message was edited by: Mike Vidal

I'm starting to think that maybe I have a different problem from everyone else in this thread, because I solved my problem by going to the Bluetooth preferences panel, selecting 'Advanced...' and unchecking 'Allow Bluetooth devices to wake up this computer.'

My Bluetooth mouse must have been causing the problem because it might have moved by a little bit and then turned on the computer.

GaryKing wrote:
I'm starting to think that maybe I have a different problem from everyone else in this thread, because I solved my problem by going to the Bluetooth preferences panel, selecting 'Advanced...' and unchecking 'Allow Bluetooth devices to wake up this computer.'

My Bluetooth mouse must have been causing the problem because it might have moved by a little bit and then turned on the computer.

Great, one down, a few to go.
As I noted, external EMPs can affect a computer. Most Microwave ovens and some older cordless phones use the same frequency band as BlueTooth, so it might not have been the mouse but some other electronic device in your area.
Or, as you point out, a truck or some other vibration might have jiggled the mouse suffiiently to activate the computer.
Live and learn 🙂

Update:

I turned off every lan option to wake from lan, pulled the definitions from my router for the mini out, and pulled the cable. Machine stayed shut off over the weekend.

Now I will leave the lan cable plugged in and see what happens tomorrow morning.

MV