Fix “Oh No, Something Has Gone Wrong” on Ubuntu

The “Oh no! Something has gone wrong” screen on Ubuntu usually means the GNOME desktop session crashed or could not start correctly; it does not necessarily mean your files are damaged. Restart the computer, then use the recovery steps below to check graphics, disk space, and recent software changes if the message returns.

What the error means

This message is associated with GNOME, Ubuntu’s default graphical desktop. It can appear after the desktop shell or session encounters a fatal problem. The login screen may remain usable, or Ubuntu may show the error after login and fail to display the normal desktop.

Possible causes include a graphics driver or display-server problem, a failed system update, an incompatible GNOME extension, insufficient free disk space, or damaged configuration files. The message itself does not identify which cause applies. Avoid assuming that Ubuntu must be reinstalled: many cases can be diagnosed from a text console without removing personal files.

1. Restart once and check whether the problem repeats

If the message appeared only once, restart from the power menu if it responds. If the desktop is frozen, try switching to a text console by pressing Ctrl+Alt+F3 (on some laptops, also hold Fn). Sign in with your Ubuntu username and password; the password will not appear as you type. To restart from the console, run:

sudo reboot

Use this as a first check, not as a diagnosis. If the desktop works after restarting, save your work and monitor it. If the error returns, note whether it began after a system update, driver change, extension installation, or an abrupt power loss; that timing can help narrow the cause.

2. Check free disk space and complete pending updates

A nearly full system partition can prevent applications and desktop components from writing temporary files or updating. From a text console, check available space with:

df -h

Look at the filesystem mounted at /. If it is full or nearly full, remove files you recognize, such as unneeded downloads, rather than deleting system directories. You can clear downloaded package files with:

sudo apt clean

Once there is adequate space and a working internet connection, refresh package information and finish configuring packages:

sudo apt update
sudo dpkg --configure -a
sudo apt --fix-broken install
sudo apt upgrade

Read the proposed changes before confirming. Do not interrupt an upgrade while it is running. If package commands report errors, keep the exact text; it is more useful for diagnosis than repeatedly running the same commands.

3. Test whether a GNOME extension is responsible

Extensions can change GNOME Shell behavior, and an extension may stop working after a desktop update. If you can reach a terminal in your graphical session, disable user extensions temporarily:

gnome-extensions disable --all

Then log out and back in, or restart the computer. If the desktop becomes stable, re-enable extensions one at a time and check after each change. Remove or update the extension that brings the problem back. If the command is unavailable or the graphical session cannot start, skip this test rather than installing extra tools from an unfamiliar source.

Disabling extensions is reversible and does not normally remove personal documents. It is a useful test because it separates a desktop add-on problem from a broader system or graphics problem.

4. Check graphics and login-session options

Graphics problems can arise after a driver or kernel update, or when the system has trouble starting its current display session. At the login screen, select your username and look for the gear icon before entering your password. If another session option is offered, try it once and see whether the desktop loads. The options available vary by Ubuntu installation and hardware; do not assume every computer offers the same choices.

If you recently installed a proprietary graphics driver, use Ubuntu’s Software & Updates application, when accessible, and its Additional Drivers tab to review available drivers. Alternatively, start in recovery mode from the GRUB menu if the normal desktop will not load. Recovery options and driver steps depend on the hardware, so avoid copying commands intended for a different graphics card or Ubuntu release.

If the error began immediately after a kernel update, the GRUB menu may let you select an earlier installed kernel under Advanced options for Ubuntu. This is a diagnostic test; it does not repair the newer kernel. If an older kernel works, finish system updates and consult Ubuntu’s documentation or support channels for the relevant hardware before removing kernels or changing driver packages.

5. Use a fresh user account to isolate settings

A problem limited to one account may come from that account’s GNOME settings rather than the system-wide installation. If you can access Settings > System > Users (wording can vary), create a temporary test user and sign in to it. If the new account opens normally, the cause is more likely to be user-specific configuration or an extension.

Do not delete or overwrite the original account to test this. Back up important files before changing configuration. Resetting GNOME settings can alter preferences such as panels, shortcuts, and appearance, so first record any settings you want to preserve. A new account that shows the same error suggests a system-wide issue instead.

When to use recovery or get more help

If the system will not reach a usable login screen, restart and open the GRUB menu. On many systems, holding Shift during startup or tapping Esc may reveal it, but timing and firmware behavior differ. Choose Advanced options for Ubuntu, then a recovery entry if one is available. Recovery mode can provide basic repair options, but changing packages or filesystem settings without understanding the prompt can make matters worse.

Before attempting major repairs, back up data if possible. Seek Ubuntu community or hardware-specific support if the disk reports errors, the computer repeatedly freezes, package repair fails, or the issue began after a driver change and persists across user accounts. Include your Ubuntu release, computer or graphics hardware, when the error began, and relevant command output. Do not post passwords, private keys, or other secrets.

Frequently Asked Questions

Does this error mean Ubuntu has deleted my files?
No. The message indicates a desktop-session problem, not by itself that personal files were erased. Still, back up important data before attempting substantial repairs, especially if the disk may be failing.

Can I fix it without reinstalling Ubuntu?
Often, yes. Restarting, freeing disk space, completing package repairs, disabling extensions, or testing another session can resolve or isolate the cause. Reinstallation should not be the first step.

Why does the message return after I log in?
The desktop session may be crashing repeatedly because of an extension, graphics issue, incomplete update, full filesystem, or user-specific setting. The timing of the failure and whether another account works are useful clues.

How do I open a terminal if the desktop is frozen?
Try Ctrl+Alt+F3 to switch to a text console, sign in, and run diagnostic commands. Use Ctrl+Alt+F2 or another function key to return to the graphical session on some systems; the exact console mapping can vary.

Is it safe to run “sudo apt –fix-broken install”?
It is a standard package-repair command, but read the changes it proposes before accepting. If it wants to remove important desktop or system packages, cancel and investigate the package error instead of confirming blindly.

Related

• VN Video Editor on PC: How to Install and Use It
• Fix Windows 10 Bluetooth Problems: A Practical Guide
• Microsoft Designer Tips and Tricks for Better Designs