I have posted seen this on the Ubuntu forums (http://ubuntuforums.org/showthread.php?t=2175057), but its not drawing a solution there so I am posting here.
Problem is when I shutdown my computer it restarts.
This ONLY happens if I have put the computer into suspend at some point since the last boot. This means that once the computer reboots once, I can shut it down fine, as long as I don't put it into suspend again.
Shutting down from the command line, or GUI makes no difference.
Whether I activate suspend via lid close or from the GUI makes no difference.
Problem is on a Thinkpadx31e (Intel) and has persisted across 12.04, 12.10, 13.04, 13.10.
Any ideas on what I do to fix this annoying bug?
@terdon: Some people have mentioned problems with networking/wifi cards. On this point, perhaps it is useful to also point out that I was having problems with my Broadcom BCM43228 chip, as the proprietary driver was causing the system to freeze when on battery power. I changed to an intel Centrino wireless chip and that solved the problem of freezing. The reboot problem on shutdown, after suspend, persisted across the different chips.
@terdon: I see two potential problems in var/log/pm-suspend.log. One pertains to failed connections and gives the following:
Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend:
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
/usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend: success.
The other pertains to a suspend not being applicable:
Running hook /usr/lib/pm-utils/sleep.d/95hdparm-apm suspend suspend:
/usr/lib/pm-utils/sleep.d/95hdparm-apm suspend suspend: not applicable.
This second error has a different file causing the problem in different instances: eg.
/usr/.../sleep.d/75modules
/usr/.../sleep.d/90clock
/usr/.../sleep.d/95anacron
/usr/.../sleep.d/95hdparm-apm
Do you need to know all of the different ones?
/var/log/pm-suspend.log
? Have you perhaps made any changes to the files in/etc/pm/sleep.d/
or/etc/pm/power.d/
? Also check those in/etc/acpi/
. The thing is that this is incredibly hard to debug from a distance. I'm just throwing files at you hoping one of them might stick. – terdon Mar 27 '14 at 13:53/var/log
are logs so any errors might be logged there. Those will be the easiest to sift through. – terdon Mar 27 '14 at 14:47