New answers tagged

0

I was having the exact same problem, try going into grub menu and switching to the "older" linux kernel (most probably it'll be 5.11.0-27-generic). switching to 5.11.0-27-generic kernel solved it for my hp-15-ba021ax(AMD) running ubuntu 20.04.3


0

the problems were solved by going to grub menu and setting 5.11.0-27-generic as the default kernel instead of 5.13.


1

Long story short: don't know exactly what the problem is but kernel 5.16 fixed it: sudo add-apt-repository ppa:tuxinvader/lts-mainline sudo apt update sudo apt-get install linux-generic-5.16 Obviously after the installation at the first reboot you will still have to hold down the power key, but once the 5.16 has been started the subsequent reboots will be ...


2

One of the ways that I've done this is by masking the systemd targets, which prevents certain actions from being performed, regardless of who enters the command. For example, to prevent the system from being shutdown, you can do this: sudo systemctl mask poweroff.target Now any attempt to shutdown the system via sudo shutdown or sudo systemctl shutdown will ...


0

I'm having the same problem only I have an Asus. Will this solution work for me or do I need to download a totally different bios?


0

I had the same problem and it was due to the Linux kernel upgrade to version 5.11.0-41. You can try and confirm if that's the problem by booting to an older kernel version (5.11.0-40) in Advanced Options of GRUB. If that is the case, you can definitely fix it by downgrading to version 5.11.0-40: sudo apt remove linux-image-5.11.0-41-generic linux-headers-5....


0

i have solved this problem, i think the problem is on driver (the i915 thing), when i revert my machine back to windows with intel uhd installed, it's perfectly usable. now i use wsl to use ubuntu but i will use native ubuntu os again when the driver support my 11 gen intel driver


1

As I wrote in EDIT 3 of my answer: From the GRUB menu, choosing Advanced options for Ubuntu, I find 4 elements (2 kernel in normal and recovery mode): Ubuntu, with Linux 5.11.0-46-generic Ubuntu, with Linux 5.11.0-46-generic (recovery mode) Ubuntu, with Linux 5.11.0-27-generic Ubuntu, with Linux 5.11.0-27-generic (recovery mode) If I choose the third option, ...


1

With the new Update to the extension, the code has changed a bit, so to do this. Turn on the option Then, using the command from @UnKNOWn answer Open the extensions extension.js file with below command gedit $HOME/.local/share/gnome-shell/extensions/BringOutSubmenuOfPowerOffLogoutButton@pratap.fastmail.fm/extension.js Reorder the menu as you wish from ...


-1

I've been having the same issue, it's extremely annoying! However I found (after days of research) a solution that may not solve the "wakeup after suspend" problem, but now my system is shutting down and restarting as it should. Even though I can't find the original post, the site I found it from was stephenwagner.com. Here is what they suggested ...


0

I've been having the same issue, it's extremely annoying! However I found (after days of research) a solution that may not solve the "wakeup after suspend" problem, but now my system is shutting down and restarting as it should. Even though I can't find the original post, the site I found it from was stephenwagner.com. Here is what they suggested ...


1

Installing kernel 5.11.0-27-generic on Ubuntu 20.04 LTS also resolves this issue.


0

Try updating the Kernel, the default kernel for ubuntu 21.10 at the time of writing should be 5.13.0-20-generic. Use the following command to check $ uname -r 5.13.0-20-generic Let’s update the system first so that all repositories are up to date. To update the system we used the following command. $ sudo apt update && sudo apt upgrade -y After the ...


1

BIOS Acer Aspire 3 A315-21-92HJ The BIOS was updated to the latest 1.25 version. It didn't solve the problem. SHUTDOWN/POWER OFF Since the problem occurs with 20.04 and 21.10, and when logged into a different user account, but does not occur when booted to a Ubuntu Live USB or Pop!_OS, the problem is confined to your Ubuntu installation on disk. Backup your ...


0

Are you running NoMachine Server? https://forums.nomachine.com/topic/other-users-are-logged-in-when-i-power-off-or-restart-centos-7 I've experienced this; stopping the NoMachine server before I shutdown resolves the problem.


10

If you just need to give the power to reboot to non-admin users, you can add an entry for them in your sudoers file for reboot (and/or systemctl reboot, depending what you want them to run). Then they will be able to run sudo reboot (and/or sudo systemctl reboot). This answer assumes that they do not otherwise have access to sudo — i.e., that they are normal,...


1

If the HP desktop that you are using is similar to the All-in-One machines that I've supported in the past, then you may need to make a slight modification to your Grub file to disable ACPI warnings, which can keep a computer active. Here's how you can do it: Open a Terminal (if it's not already open) Edit your /etc/default/grub file with sudo: sudo {editor ...


26

The most effective way to do this would be to mask the power off target like this: sudo systemctl mask poweroff.target Now it will be impossible for anyone to shut down the machine unless they hold down the power button or physically disconnect the machine from power. Rebooting is unaffected by this mask. In the event you need to shut the machine down in ...


0

From the description of the problem I'm not sure how this will help. However, these are my general tips for debugging the very early boot process. remove kernel arguments like quiet and splash. From the comments, it sounds like you are already doing this. add kernel argument debug=. This will configure casper to write a debug log to /casper.log inside the ...


0

For me I thought it was rebooting but it was just asking to decrypt so it can install updates before turning off. I could not even force it to shutdown - got lucky there :)


1

I have the same laptop and the exact same problem. Been trying to figure it out for the past week. Same results in shutdown logs. Spent some time chasing various errors in the logs (cpufreq, Disk unmount errors, LUKS, fsck, etc), but didn't make a difference. I was able to revert back to kernel 5.11.0.38-generic and everything was back to normal. That ...


0

I doubt many people will have the issue that I ultimately found. Per the comment by @AlexOnLinux, I tried stress testing the computer and that is when I was having issues. I figured it must be the PSU, but when I went to check the power connection, I noticed that when I touched the power cable, the system immediately shutdown. I then got a meter out to test ...


0

I was able to fix this (after trying lots of different fixes and progressively making this worse) by getting a fresh install of Ubuntu 20.04 LTS and choosing to use kernel 5.11.0-27-generic (which came with the install) instead of the newer 5.11.0-43-generic that is the default at the time of writing. So maybe it was a kernel problem all along and I just ...


3

This is controlled in /etc/systemd/system.conf. #DefaultTimeoutStopSec=90s is commented out: remove the comment sign and add your custom value.


0

After a "sudden shutdown", aka "system crash", and reboot, or an intentional reboot, the terminal command sudo journalctl -b -1 -e will show you the end of the previous boot's log's. If there is no hint there, suspect power/ overheating. Overheating is most likely caused by dust. Power down your system. Unblock your fans and vents, ...


Top 50 recent answers are included