Tag Info

New answers tagged

0

Open the console with pressing the "Ctrl" + "t" In the console write this code: sudo reboot now! then enter your password, with this code you should reboot your system, or you can shutdown with: sudo shutdown now If the console not open with "Ctrl" + "t", you can open a "tty" with "ctrl"+"alt"+"F1" Hope this will help you.


0

It's not a definitve solution, but it works whenever this happens: On command line sudo init 6 to restart and sudo init 0 to shutdown Regards


0

Disconnecting the battery and charger may help, otherwise holding down on the power button may do the trick


0

I saw this problem on different machines after upgrading from 12.04 to 14.04. To fix I had to issue sudo pam-auth-update --force Relevant bug: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1240336


0

There are no difference between halt command and shutdown in terms of the user intention. The thin difference is that in halt you have to conveniently push the power button to shutdown the system whereas in shutdown command it will automatically instruct the Advanced Configuration Power Interface (ACPI) to sent a signal to the power unit to turn off the ...


0

Thank you for this delay solution. I confirm it works on Dell Inspiron E1405, Ubuntu 14.04, with the lowest possible value of 3, which I assume is three seconds. If I go down to 2 seconds, it hijacks the shutdown options. Once again, thanks a bunch!


4

You can make a conditional to relaunch the script as root if it's launched as a normal user. To shutdown the computer: #!/bin/bash if [[ $USER == "eka" ]]; then # If the script is ran as "eka": sudo $0 # Relaunch it as "root". exit 0 # Once it finishes, exit gracefully. elif [[ $USER != ...


0

I had this same problem with 100% reproducibility, the first power off after a wake-on-lan power on would result in an immediate and undesired re-power on. But only one. I tried lots of suggestions, even using Realtek's own kernel driver, but nothing worked. Finally I upgraded my motherboard's bios and the problem was fixed. I have a P8Z77-V-LK ASUS ...


1

I have upgraded to Gnome 3.16.1 and I am no longer having this problem. I'm guessing it was fixed by this change: ======================================== gtk+ ======================================== Overview of changes in GTK+ 3.16.2 ================================== * Bug fixes: [...] 747689 [...] GtkApplication: Prevent more crashes ...


1

Instead, you could use at command. Install it with sudo apt-get install at And run sudo echo "shutdown -h now"|at now + 30 min


2

This script controls the shutdown timer using sleep and a loop. #!/bin/bash # Read Password read -s -p "Password: " password echo # Send messages for i in {0..5} do echo "Shutdown in" $((30- i * 5)) "minutes" sleep 300 done echo "Shutdown now" | wall # shutdown and screensaver Command echo "$password" | sudo -kS shutdown -h +30 & ...


2

When you have two commands on two separate lines of a shell script, the second will only run when the first has finished. To avoid this, you need to add a & to the end of the first command to have it run in the background: #!/bin/bash sudo shutdown -h +30 & gnome-screensaver-command -a As for not asking for the password, you'll need to tell sudo ...


6

Solution to problem 1 and 2: You need to edit your /etc/sudoers (sudo visudo) file to add the relevant entry to grant the passwordless sudo permission for the user to run this script (not the shutdown command) : foo spamegg = (root) NOPASSWD: /path/to/script.sh Here foo is the username, spamegg is the hostname, replace the /path/to/script.sh ...


2

Thanks for all the hints and tips on here. Like other's, I've had issues on my Zenbook UX21E for years, while it was running Windows 7. I never upgraded the OS for years, other than the traditional MS updates. Under windows, the issue was confined to sudden shutdowns while pulling the AC power. (Honestly, I just thought it was a short in the power connector, ...


1

You are using the wrong commands, Try one of below:- sudo shutdown -h now sudo poweroff sudo halt -p sudo init 0 sudo shutdown -p now For forced poweroff (not shutdown):- sudo poweroff -f


1

1.Try to reinstall NotifyOSD sudo apt-get --reinstall install libnotify-bin notify-osd Then restart. 2.Installing Battstat Applet gives you a warning on top of all windows like this:- http://techrax.tk/wp-content/uploads/2015/05/critical_message.png To install it, do:- add-apt-repository ppa:iaz/battery-status apt-get update apt-get install ...


1

It didn't work for me. Instead of GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off" I used GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force" and it works. :-)


0

Sorry for bad English:) Had same issue on my Lenovo laptop (intel hd video card) - had a freeze on restart/shutdown/sleep with Kubuntu 15.04. Same issue was reproduced with Ubuntu 14.04. In my case I even was unable to switch to tty. On my laptop i had no fglrx, tried to modify grub config with all found "solutions" as reboot=bios & etc. - nothing ...


0

I recently solved a similar problem, see http://askubuntu.com/a/617395/368069 adapted to your questions the answer would be: Create a file /etc/pm/sleep.d/00-check-rsnapshot. In this file check if a rsnapshot currently is active. If yes, just abort the script using exit 1. That's it. Suspend will be aborted. Might work for shutdown, too.


0

For me removing all parameters from GRUB_CMDLINE_LINUX_DEFAULT line causes stop system boot. I have encrypted disk and LVM. In this line I have some parameters that show kernel which partition is encrypted. If you want to show all kernel messages during boot time edit /etc/grub.d/10_linux file and find line vt_handoff="1" Change it to vt_handoff="0" ...


0

Just install laptop-mode-tools to solve shutdown freeze problem: sudo apt-get install laptop-mode-tools If you have tlp installed on your system, you must remove it because it's conflicting with laptop-mode-tools: sudo apt-get remove --purge tlp tlp-rdw


0

It usually happens due to overheating. Maybe something is wrong with the temperature sensors. Lets try to check this out: Install the program lm-sensors (run in terminal). sudo apt-get install lm-sensors Detect all sensors (run in terminal): sudo sensors-detect Get temperature data (run in terminal): sensors


0

try insert in grub command line (etc/default/grub) the "restart=acpi halt=acpi poweroff=acpi" commands, update in terminal (sudo update-grub) if work then install 64 bit version and update it when install done.


0

It happened to me also with Plasma 5.3. I had to go back to Plasma 5.2 to be able of shutting down from the gui menu.


1

Try disabling hibernation completely by running powercfg /h off as administrator in windows. Happy that this solved the issue for you!


0

I have the same problem, and what I do is to "reboot" windows, and then choose ubuntu from the grub menu. Then I can mount windows partitions with no problem. My theory is that windows hibernates when you choose "shut down". Another one of those misleading/lying windows actions. Now I just never "shut down" windows, I always reboot into a linux distro, and ...


0

Found a really easy solution! Create a file /etc/pm/sleep.d/70-check-recordings. In this file check if a recording currently is active. If yes, just return exit 1. That's it. Suspend will be aborted. My script looks like this, it is based on https://tvheadend.org/projects/tvheadend/wiki/Wakeup $ cat /etc/pm/sleep.d/00-check-recordings #!/bin/bash # # ...



Top 50 recent answers are included