Why Ubuntu Keeps Crashing Back to the Login Screen: Understanding the OOM-Killer and How to Disable It

If you're using Ubuntu and have experienced the frustration of your system crashing back to the login screen—only to find that all your open apps have disappeared—you’re not alone. This issue, often referred to as a "desktop crash," can be incredibly disruptive. You might think your system is overloaded or something is wrong with the hardware, but even machines with 8GB or 16GB of RAM running modern versions of Ubuntu can suffer from this problem.

In many cases, the culprit is Ubuntu's OOM-Killer (Out Of Memory Killer), a system process that terminates applications when the operating system detects low memory. While this is intended to protect your system, it can sometimes lead to over-aggressive app termination, even when it seems like there’s plenty of RAM available. Fortunately, there’s a workaround for this issue—masking the OOM-Killer can effectively stop these crashes.

In this blog, we’ll explore why this happens and walk you through a simple solution: disabling the OOM-Killer. Don't worry; this is a beginner-friendly guide with step-by-step instructions.

Why Does Ubuntu Crash Back to the Login Screen?

Ubuntu is designed to manage system resources like memory (RAM) efficiently. When your system runs low on memory, the OOM-Killer steps in and forcibly closes applications to free up RAM. This is typically a good thing, as it prevents the system from freezing or becoming unresponsive. However, in some cases, the OOM-Killer is too eager to terminate processes, and it ends up closing the desktop environment itself, which brings you back to the login screen and kills all your open apps in the process.

Here are some reasons this might happen:

• Resource-Intensive Applications: Running many applications simultaneously (or memory-hungry ones like video editors) can trigger the OOM-Killer, even if you have a decent amount of RAM.
• Background Processes: Sometimes, background services consume more memory than expected.
• Kernel Mismanagement: The kernel might incorrectly calculate the system's memory usage, causing the OOM-Killer to be triggered unnecessarily.

Even with 8GB or 16GB of RAM, users have reported frequent desktop crashes where they are suddenly logged out, losing all unsaved work. The problem seems especially prevalent in recent Ubuntu releases.

The Solution: Masking the OOM-Killer

A proven solution to stop these crashes is to mask (disable) the OOM-Killer from running. Masking a process in Linux effectively disables it, and in this case, it stops the OOM-Killer from terminating your desktop environment.

After masking the OOM-Killer, users have reported that their Ubuntu machines continue to run for days without issues—no crashes, no sudden logouts, and no loss of apps.

However, note that disabling the OOM-Killer comes with a warning: in some cases, Ubuntu may attempt to kill the desktop environment, but instead of crashing, the system will continue to work and display an error report.

How to Disable the OOM-Killer: A Step-by-Step Guide

If you want to give this solution a try, follow these simple steps. Remember, this change is reversible, so if it doesn’t work for your system, you can always undo it.

Step 1: Open the Terminal

First, open your terminal by pressing Ctrl + Alt + T, or you can find it by searching "Terminal" in the Ubuntu menu.

Step 2: Mask the OOM-Killer

In the terminal, type the following command and press Enter:

sudo systemctl mask systemd-oomd

This command masks (disables) the OOM-Killer service, preventing it from running.

Step 3: Reboot Your System

After masking the OOM-Killer, you could restart your system but we found it unnecessary. You can reboot your system with this command:

sudo reboot

Once your system restarts, the OOM-Killer will no longer terminate applications, including your desktop environment.

What If This Doesn't Solve the Problem?

If masking the OOM-Killer doesn't fix your issue, it's easy to undo the change and return to the default settings. Here's how:

Step 1: Unmask the OOM-Killer

To re-enable the OOM-Killer, type the following command in your terminal and press Enter:

sudo systemctl unmask systemd-oomd

Step 2: Reboot Again

As before, you may need to reboot your system to apply the changes:

sudo reboot

Is It Safe to Disable the OOM-Killer?

Disabling the OOM-Killer generally solves the problem of Ubuntu crashing to the login screen, but it comes with some trade-offs. Without the OOM-Killer, your system might run into low-memory situations without automatically terminating apps, which can lead to a sluggish system. However, most modern systems have enough memory (especially with 8GB or more) to handle typical workloads without running into severe memory issues.

If your system shows a significant error when memory runs low, you might need to manually close some applications to free up resources.

Final Thoughts

Crashing back to the login screen on Ubuntu can be a huge headache, especially when you lose all your open applications. Fortunately, for many users, masking the OOM-Killer provides a reliable fix. This solution is quick and reversible, making it a great troubleshooting step if you're experiencing desktop crashes.

Remember, while this might not solve every crash issue, it's an easy and effective first step. If it doesn’t work, you can always unmask the OOM-Killer and explore other potential causes for your system instability.

Give it a try, and hopefully, you'll be able to enjoy a more stable Ubuntu experience!