I think the answer should be plain:
Use any of the /etc/rc.local scripts or create a new one. Add the
following three lines:
#/bin/bash
sudo gru
halt
Here's an explanation: I use my GRUB to halt the system in its shell.
That;s what everyone said. They reboot to power their systems off. What
if w
I think the answer should be plain:
Use any of the /etc/rc.local scripts or create a new one. Add the
following three lines:
#/bin/bash
sudo grub
halt
Here's an explanation: I use my GRUB to halt the system in its shell.
That;s what everyone said. They reboot to power their systems off. What
if
Shouldn't have spent so much time in replying but sorry. I agree
acpi=force works pretty well (although you will recieve a notification
before a kernel boots that acpi=force is required to enable acpi). I
agree with all who mentioned this in their posts (sorry for the bad
citation). I suggest that
I think this should be end of this very very long thread! I was directed
here by LinuxForums.org. I faced this problem in my computer which is an
Intel i486 64 MB RAM 450 MHz. But this should work for all x86s. Hope
so! And hope that the bug is fixed in Hardy.
--
Shut Down won't power off
https:/
Public bug reported:
Binary package hint: gnome
When ever I am working in a window, such as filling a form or so, and
meanwhile I open a new window, it comes on the top and interrupts my
work. My rhythm of keystrokes and mouseclicks is affected. Like MS
Windows systems, a new window should always
