How7o
  • Home
  • Tools
  • Prank Screens
  • Learn
  • Blog
  • Contact
Reading: Fix: Terminal Won’t Open in Ubuntu on VirtualBox
Share
How7oHow7o
Font ResizerAa
  • OS
Search
  • Home
  • Tools
  • Prank Screens
  • Learn
  • Blog
  • Contact
Follow US
© 2024–2026 How7o. All rights reserved.
How7o > Free Laravel, PHP, WordPress & Server Tutorials > OS > Fix: Terminal Won’t Open in Ubuntu on VirtualBox
OS

Fix: Terminal Won’t Open in Ubuntu on VirtualBox

how7o
By how7o
Last updated: May 23, 2026
4 Min Read
Fix Ubuntu terminal not opening on VirtualBox
SHARE

If the terminal won’t open on Ubuntu 22.04+ running inside VirtualBox — the launcher name flashes in the top-left and then disappears with no terminal window — the cause is a malformed locale, usually from VirtualBox 7’s unattended installer. The quickest fix is to change the system language to a different locale and back, which regenerates the locale files.

Contents
  • Fix via the GUI
  • Fix from a TTY (if no terminal works at all)
  • Prevent it during install — skip unattended mode
  • Confirm the fix
  • Frequently asked questions
  • Related guides
  • References

Last verified: 2026-05-17 on Ubuntu 24.04 in VirtualBox 7.1. Originally published 2023-03-02, rewritten and updated 2026-05-17.

Fix via the GUI

  1. Open the Settings app in Ubuntu.
  2. Sidebar → Region & Language (older releases: Language & Region).
  3. Click the Language button and pick a different language — e.g. British English instead of American English.
  4. Apply, then change it back to your preferred language. Apply again.
  5. Reboot the VM.
  6. Open the terminal — it should launch normally now.

Toggling the language regenerates the locale files that were left incomplete during the install. Once they exist, the terminal launcher can resolve LANG and start cleanly.

Ubuntu terminal not opening in VirtualBox — toggle Region & Language, locale-gen via TTY, skip unattended install

Fix from a TTY (if no terminal works at all)

# Switch to a TTY: Ctrl+Alt+F2 (or F3/F4). Log in.
sudo locale-gen en_US.UTF-8
sudo update-locale LANG=en_US.UTF-8

# Back to the desktop with Ctrl+Alt+F1 (or F7), then reboot
sudo reboot

Pure-CLI alternative — useful when the GUI terminal launcher refuses to open and you can’t get to Settings from the desktop. The TTY (text-only console) is always available.

Prevent it during install — skip unattended mode

If you’re installing a fresh VM, untick Skip Unattended Installation‘s opposite — that is, check “Skip Unattended Installation” — in VirtualBox’s new-VM dialog. You’ll click through the regular Ubuntu installer instead of letting VirtualBox auto-fill the answers. Slightly more clicks, but the locale comes out correctly configured and you avoid the terminal-launcher bug entirely.

Confirm the fix

locale
# Should print en_US.UTF-8 (or whatever you set) on every LANG_* line,
# with no warnings about "Cannot set LC_ALL to default locale"

echo $LANG
# en_US.UTF-8

Frequently asked questions

Why does changing the language fix this?

The terminal launcher reads the locale from LANG / LC_ALL. On fresh Ubuntu installs (especially via VirtualBox’s “unattended” auto-installer), the locale can land in a half-configured state — en_US.UTF-8 is declared but the locale files weren’t generated. The terminal application errors out silently on launch when it can’t find the locale. Selecting a different language and applying it regenerates the locale files, fixing the launch.

Can I fix the locale without changing the language?

Yes — regenerate it from the terminal you can reach (e.g. Ctrl+Alt+F2 for a TTY): sudo locale-gen en_US.UTF-8 then sudo update-locale LANG=en_US.UTF-8, then reboot. Same effect as the GUI Language & Region toggle, faster if you’re comfortable with a TTY.

Why does “Skip Unattended Installation” prevent this?

VirtualBox 7’s unattended installer answers Ubuntu’s setup wizard automatically but uses a minimal locale config that triggers the bug. Skipping unattended mode lets you walk through the regular installer, which configures the locale fully. Trade-off: you have to click through the install dialog manually.

Does this affect bare-metal Ubuntu installs?

Rarely — the bug is mostly tied to VirtualBox 7’s unattended installer. Bare-metal Ubuntu installs (or other VM hypervisors) usually configure the locale correctly. If you do hit it elsewhere, the locale-gen fix is the same.

Related guides

  • How to Check Your Ubuntu Version
  • How to Check the Linux OS Name and Version from the Command Line
  • How to List Network Devices on Linux

References

Ubuntu Locale documentation: help.ubuntu.com/community/Locale. VirtualBox documentation: virtualbox.org/manual.

TAGGED:configurationLinuxUbuntuvirtualbox

Sign Up For Daily Newsletter

Be keep up! Get the latest breaking news delivered straight to your inbox.
[mc4wp_form]
By signing up, you agree to our Terms of Use and acknowledge the data practices in our Privacy Policy. You may unsubscribe at any time.
Share This Article
Facebook Copy Link Print
Previous Article Laravel Blade @foreach vs @forelse comparison Laravel Blade: Difference Between @foreach and @forelse
Next Article Set up Let's Encrypt SSL with Certbot on Ubuntu How to Set Up Let’s Encrypt SSL with Certbot on Ubuntu (Apache & Nginx)
Leave a Comment

Leave a Reply Cancel reply

You must be logged in to post a comment.

FacebookLike
XFollow
PinterestPin
InstagramFollow
Most Popular
Run Laravel queue workers with Supervisor
How to Run Laravel Queue Workers in Production with Supervisor
May 23, 2026
Nginx as a reverse proxy for a Node.js app on Ubuntu
How to Set Up Nginx as a Reverse Proxy for Node.js on Ubuntu
May 23, 2026
Install and configure Redis on Ubuntu for Laravel and WordPress
How to Install and Configure Redis on Ubuntu (for Laravel & WordPress)
May 23, 2026
Harden a fresh Ubuntu VPS with UFW, Fail2Ban, and SSH key auth
How to Harden a Fresh Ubuntu VPS: UFW + Fail2Ban + SSH Key Auth
May 23, 2026
Set up Let's Encrypt SSL with Certbot on Ubuntu
How to Set Up Let’s Encrypt SSL with Certbot on Ubuntu (Apache & Nginx)
May 23, 2026

You Might Also Like

Nginx 502 with recv() failed 104 connection reset — PHP-FPM timeout and memory tuning
Server Management

Fix Nginx ‘recv() failed (104: Connection reset by peer)’ with FastCGI

9 Min Read
aaPanel domain and Let's Encrypt SSL setup — secure the control panel
Server Management

How to Access aaPanel with a Domain and Let’s Encrypt SSL

8 Min Read
Reset the LiteSpeed WebAdmin Console password
Server Management

How to Reset the LiteSpeed WebAdmin Console Password

4 Min Read
Stop cron job output and the resulting email spam
Server Management

How to Stop Cron Output (and the Spam Emails)

5 Min Read
How7o

We provide tips, tricks, and advice for improving websites and doing better search.

Tools

  • Age Calculator
  • Word Counter
  • Image Upscaler
  • Password Generator
  • QR Code Generator
  • See all tools→

Pranks

  • Fake Blue Screen Prank
  • Hacker Typer
  • Fake iMessage Generator
  • Windows XP Crash Prank
  • Windows 11 Update Prank
  • See all prank screens →

Company

  • About Us
  • Blog
  • Contact
  • Privacy Policy
  • Terms of Service
  • Sitemap
© 2024–2026 How7o. All rights reserved.
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?