New answers tagged

2

You may use sleep command. It accepts postfix m to numbers, which stands for minutes. I.e. you can execute sleep 60m && someCommand Now, here's a little problem that sudo after a time limit requires to enter the password again, and if you'd execute sudo sleep 60m && sudo somecommand, the someCommand wouldn't do in time. To workaround it, ...


0

Something has clearly gone wrong. If you have important data on that disk get a new disk and take an image of the original disk using dd or dd-rescue. Do not try to recover data before you got that image, as the recovery atempt might destroy your data. Get help from your local linux user group, if you are not shure what to do, but do that disk image first. ...


2

Is it possible that shutting down and then unplugging my external hard drive could have broken a path? No. And if it did it would not kill the contents of the disk. I have noticed that Ubuntu shuts down almost instantly ... We do not probe for an update as Windows does. whereas Windows takes much longer and often pauses on closing 1 application ...


0

I found that the inability to shutdown only occurred when a suspend/resume had been performed during the session. However, ps aux | grep suspend did not give any results. It appears that the shutdown issue was related to another issue in 16.04 LTS whereby the swap partition encryption is not working. I filed the details in Launchpad Ubuntu Bug #1594035. ...


0

I see it too. The problem started after allowing nvidia updates. While I backtrack on that, I will tell you the only solution I've found Run ps aux | grep suspend you should see a root-owned suspend process. Then kill that process: sudo kill -9 xxxx where xxxx is the number of the job. Warning: the PC will suspend immediately when you do this, and ...


0

I had the same issue with the shutdown on Ubuntu (15.10 and 16.10). With debug enabled in GRUB I could see that the laptop crashed right after 'Reached target Shutdown' GRUB_CMDLINE_LINUX_DEFAULT="debug" I also tried various GRUB options and even to create a service that powers off the USB. If you have USB 3.0 you could try to disable them from BIOS (I ...


0

try sudo shutdown OR sudo reboot if you want to restart, in a terminal. if you cannot access terminal for some reason, then press Ctrl+Alt+F1 then login using your user name and password, then use sudo shutdown again. if you want to return back to your desktop screen press Ctrl+Alt+F7


1

The accepted answer sudo init 0 doesn't work for me in Xubuntu based in Ubuntu 16.04. While waiting for a patch this is how I can shutdown my laptop: Using poweroff sudo poweroff -f -f to force the computer to shutdown without contacting the init system. Detecting the process that prevents the computer to shutdown In my case there is always the tty ...


1

On 16.04 no need of sudo To shutdown : poweroff To Reboot : reboot


1

I know about this bug. This often happens with me, when I had a long session with my phone and especially when there were many progress with the Unity 8 gui e.g. switching between staged and windowed mode. In these cases the display server seems to work optically properly, but for real it runs laggy. You sometimes reconize it by failing updates and ...


0

If you hit F8 on your splash screen logout, watch for the verbose logout, especially any line that says something related to 'plymouthd has been excluded from killing...". If you see this, then the protected state of plymouthd is most-likely causing your harddrive to be prevented from re-mounting in read-only state for the logout. If this is the case, this ...


0

If you look at your shutdown log, you will most-likely see a line which says "plymouthd has been excluded from killing..." Redhat already has a note on this function in their bugs report. It appears related to Fedora. Everyone is offering band-aids to this, at this time, but even if you take ownership from root for plymouthd or go to a non-splash shutdown, ...


0

man shutdown would have been of use to you. sudo shutdown -P now will power down the system now. the -h switch only halts the system and doesn't power it down.


0

Who knows when/if this problem: "systemd-shutdown: Failed to finalize DM devices. ignoring." will ever be fixed on this old platform - nothing I've read would suggest it'll be anytime soon. In the meantime, this work-around allows me to reboot my server without physically power cycling the machine. All the following commands are under sudo: Put these ...


1

This is definitely a graphics card issue. "Nouveau" is the open-source nvidia driver. Check your GPU fan and cooling. Remove dust.


1

This thread may be helpful to you: How to use lm-sensors? Reading up on some of these sensor apps, some can help you control the fan.


0

I would recommend pulling out your fan first of all. I have fixed numerous computers that had junk in the fan or the heatsink, especially if it is on the floor. After that, if you can replicate it I would run top and watch what is using the CPU the most, leading up to a shutdown.


1

Seems like heat sink on top of CPU is either not functioning well or thermal paste on top of CPU and under the heat sink fan needs refill. Hope it solves it.


0

And why is upstart working? Or is it? […] I'm still confused why upstart is working at all. systemd is running as the system-wide service manager. upstart is running as a per-session service manager. Further reading http://askubuntu.com/a/613814/43344 "Boot and service management". Upstart version 15 release notes. 2015-04-24. Ubuntu. "...


1

Maybe shut down and take a nap. Suspend will still keep some software in RAM memory, thus eating some battery. Probably not much, but enough to make a difference in some situations. That's for laptops. If you're planning to take notes on an Ubuntu tablet or convertible, i see no reason to shut down. God, i wish i'd have a Galaxy tablet with Ubuntu on it!


0

Similar question in Manjaro Forum by a Manjaro user: https://forum.manjaro.org/t/bios-uefi-kernel-bug-i-cant-turn-off-my-pc-reboot-power-down/2369/21


1

Credit to this posted answer First, I don't know why upstart works at all since Ubuntu 15.10 should be using systemd instead. So I used systemd to solve my problem. I create a systemd "unit" called backup.service [Unit] Description=Backup script DefaultDependencies=no RequiresMountsFor=/mnt/D21EF5DA1EF5B795 /home /media/external Before=shutdown.target ...


0

It is likely a permissions issue. Both .conf files need to be executable. Do: chmod a+x ~/.config/upstart/shutdown.conf


0

Having a physical access to the keyboard can simply use the Ctrl+Alt+Delete key combination to reboot the server without having to logged on, But we can prevent the use of this key combination on a production server for an accidental reboots. - See more at: http://www.tecgeeks.com/ubuntu/how-to-disable-ctrl-alt-delete-in-ubuntu/



Top 50 recent answers are included