As an alternative to forcing shitdown, you may want to try laxatives.
this post was submitted on 27 Mar 2026
44 points (100.0% liked)
Linux
64146 readers
344 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
And make sure to drink plenty of water.
Yes, i heard it is not good to force
There are a couple of things you can do. If it is frozen then try pressing ctrl+alt+1/2/3/4 to swith to a different terminal this will let you either restart your DE or reboot the system safely.
As far as debugging it I would typically start with looking at journal logs journalctl -b-1 should show you logs from the last boot.
Even with a frozen system you can often still ensure data is written to inspect on the next boot. You may have a key labeled SysRq which likely needs an Alt modifier to trigger.
Alt+Shift+SysRq+s to sync data to disk. Alt+Shift+SysRq+u to unmount the disks. Alt+Shift+SysRq+b to reboot the system.
Execute them in that order.
This can help ensure the data about the mishap is written to disk so it can be inspected after the forced reboot. I also check the logs in /var/log but I suppose all of those are in journalctl too these days.
You just reminded me ... Before I really got into IT in my career I was at a job that still had a messenger for the internal staff. I set my status message in it to "Raising Skinny Elephants Is Utterly Boring."
I got chastised and made to change it, because the message might offend ... Skinny elephants, I guess? I never got clarification on that.
(The manager had no clue what it meant.)
Seems weird that you'd sync before terminating and killing processes. I prefer "Raising Elephants Is So Utterly Boring". Although some distros only enable the S, U, B/O anyway.
Couldn't say - I've never had the chance to use it. In fact, I'm not sure I ever had the SysRq key on a keyboard I've used.
I have had a Pause/Break key and used to think they were the same thing, but now I'm not so sure.
Its the same as the Print Screen key.
I'm not sure that I would recommend a newer user use sysrq. It is a very powerful tool that you definitely should not be blindly following from a random internet post without knowing what each command does.
In a truly frozen system then it can be good, but only as a final last resort. If the system can be unfrozen by other methods then that should be preferred instead.
Totally switch to a terminal first like you suggested and see if you can work your way from there. My suggestion goes after yours. Always try to fix the running system first.
It's probably wise to check man pages and other introductory documentation for most system administration tasks. Even though they're super low-level, they are in my opinion better to send than just pulling the power plug.
You need to have a look at the logs using journalctl.
Type journalctl —help, have a look at the options (I think —since may be what you want) and post the logs if you want to.
ctrl alt del used to do a graphics reset which often was all that was needed. ctrl alt f2 should put you in a terminal. If you had not done that I would give it a try and see if the whole system had crashed which would cause the terminal to not be responsive or if its just the grahics in which case you can login and reset the graphics.
There is https://en.wikipedia.org/wiki/Magic_SysRq_key but I've had some hit and miss success in actually getting it to work.
Normally I first try see if it is only the graphical interface that has crashed by pushing ctrl+alt+F1 or F2 or F3 to try and switch to another terminal. If I can switch, I log in and reboot or restart the window manager.
I also try SSH into the machine if I have another of around.
If I do reboot, then I use 'journalctl -b-1 -e' to see what happened at the time the system froze.
A lot of distros disable the functions of the magic sysrq key for security reasons. If it's enabled, it should work as long as the system is still capable of reading keyboard inputs.