You are not logged in.
Pages: 1
Since i made suspend work in my computer i have shutdown behaving strangely.
Sometimes instead of shutting down the system will shutdown and restart. Usually this happens after i suspended and resumed my machine. It doesn't happen all the time and it seems that its not happening when i don't suspend the computer.
Could this be module related? Any ideas welcome.
Offline
How do you shutdown?
sudo halt ?
dbus-send ?
click on shutdown in a DE ?
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
Everything happens from the gnome menu.
Offline
Try this command from the terminal to see what messages you receive:
dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop
Last edited by SanskritFritz (2012-07-18 12:15:26)
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
It just shutdown the computer.
Didn't notice anything unusual compared to when i shutdown with the gnome menu.
Offline
What computer model is it? I had the same with my thinkpad and a specific kernel.
Also see:
restart instead of shutdown
Wild guess https://answers.launchpad.net/ubuntu/+s … ion/168617
Offline
Thanks the thing is that it doesn't happen all the time. Suspend and resume (which works flawlessly as far as i can tell) seems to trigger it and again not always.
Its a desktop with a DZ77BH-55K mobo and a i-7 3770 processor.
Offline
Any chance you are using an Nvidia graphics card? https://bbs.archlinux.org/viewtopic.php?id=136751
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
No. AMD and open drivers.
Offline
I am bringing this back up for a question.
Any chance this could be related to network?? ie something like wake on LAN. And if yes is there a way of telling if this is the case?
Offline
Sorry for bumping but can anyone give any directions on where to look for the solution?? (modules files etc.)
Its not a big issue but its nice to know that everything works flawlessly.
Offline
Which init system are you using: initscripts or systemd? Have you tried using the other just to see if the problems persists?
Offline
Systemd since i installed it and i am not quite fond of messing it TBH. I tried suspending modules like button but the problem happened again.
The annoying/weird thing is that it doesn't happen all the time. The system might shutdown properly or might not. The only thing i know is that suspend to ram triggers it. And i don't see anything weird in the log files.
Offline
I get the same thing occasionally, but I have no idea what causes it. I don't think it's related to suspension on my system however (although suspend works without problems). I'm using initscripts.
Last time it happened, it happend twice in a row (I tried "sudo halt"-ing right after the first unwanted reboot). Then I just clicked the power switch before GRUB loaded.
Offline
Pages: 1