System freezes are an occasional occurrence across all operating systems, and Linux distributions are not exempt. In this discussion,
we’ll explore four methods to address a frozen Linux system before resorting to drastic measures like unplugging the power cable or forcefully holding down the power button.
Common Signs of a Frozen GUI:
Implementing the following methods can potentially resolve the issue and restore normal system operation.
Freezing or hanging in Linux can stem from various causes, either related to software or hardware. These encompass challenges such as system resource depletion, compatibility problems with applications, sluggish hardware performance, slow network connections, device or application configurations, and extended uninterrupted computations.
Primarily, the leading concern often revolves around resource exhaustion, commonly resulting in a deadlock. With this in mind, let’s explore five actionable steps to take when encountering a frozen GUI in your Linux system.
Read: How to speed up Linux
Encountering a frozen Linux desktop GUI can be a challenging situation, but there are effective steps you can take to resolve the issue:
This swift action allows you to selectively close problematic applications and regain control of your desktop environment.
To close an unresponsive application, follow these steps:
If you encounter difficulties launching the terminal, you can employ key combinations as an alternative. Follow these steps:
This method proves effective when your graphical user interface (GUI) is frozen, but your mouse remains responsive, allowing you to initiate mouse clicks. However, in situations where even the mouse is unresponsive and cursor movement is impossible, you may need to resort to the second method outlined below.
Read: Guide to Linux Config Files
If you are dealing with a program running in the terminal, stopping it is straightforward. Follow these steps:
To kill a process, refer to our detailed guide here.
Read: Processes in Linux – Guide for beginners
If the previous methods, including terminal commands, prove ineffective, you can switch to Console mode. Follow these steps:
Press Ctrl + Alt + F3 to transition to Console mode. This action will replace your
graphical interface with a Virtual Terminal.
If you need to exit the console and return to the Graphical User Interface (GUI), simply press Ctrl + Alt + F2.
Similar to the Terminal, the console provides various commands and utilities to halt running processes.
In addition to performing tasks locally, you can manage your system remotely using PuTTY, executing commands seamlessly. For remote access, ensure that an SSH server is running and properly configured on your target system. To address issues and halt a process on a remote Ubuntu server, follow these steps using PuTTY for remote access.
To install PuTTY, execute the appropriate command based on your Linux distribution:
For Ubuntu/Debian:
sudo apt-get install putty
For CentOS, Red Hat, and Fedora:
sudo dnf install putty
or
sudo yum install putty
Read: How to use scp command in Linux to transfer files securely using ssh
To start putty, type the target machine’s Ip-address in the section marked in the image. Then, press “Open”. Use the command ifconfig to find the Ip-address of any Linux machine.
If the target PC has a private address, you must be on the same network to access it remotely.
Enter your username and password to log in.
After you connect to the system, you can begin to fix any problems. A common method is to use process utilities to see all the processes running on the system, such as the TOP command.
The post What to do when Ubuntu freezes appeared first on net2.
Microsoft Edge is now available for Ubuntu. In this guide, I’ll walk you through the…
Our latest Canonical website rebrand did not just bring the new Vanilla-based frontend, it also…
At Canonical, the work of our teams is strongly embedded in the open source principles…
Welcome to the Ubuntu Weekly Newsletter, Issue 873 for the week of December 29, 2024…
Have WiFi troubles on your Ubuntu 24.04 system? Don’t worry, you’re not alone. WiFi problems…
The following is a post from Mark Shuttleworth on the Ubuntu Discourse instance. For more…