The OS you installed for the terminal hides the terminal

You install Ubuntu. Largely, let’s be honest, because you want a terminal. And then there isn’t one: nothing on the desktop, nothing pinned in the dock, and no browsable application menu of the old kind. There is a shortcut — Ctrl+Alt+T — which works perfectly and is advertised nowhere. And there’s a search box, which works perfectly too, provided you already know the word.

Search is only as good as your vocabulary

This is the part that turns an annoyance into a design failure. A search-first launcher assumes you know the name of the thing you want. For this particular thing, the name is different almost everywhere:

(.desktop files carry a Keywords= field precisely so alternative names can match, and GNOME Terminal’s does list several. How completely it covers the vocabularies above is unverified — but empirically the search did not rescue this user, and a keyword list you can’t see is still a guess you have to make.)

A browsable menu lets you find things you can’t name — you scan a list and recognise it. Search only retrieves things you can already name. Replacing browse with search silently converts “I don’t know where it is” into “I don’t know what it’s called,” which is a much worse place to be stuck.

And the irony compounds: Ubuntu’s own documentation opens roughly every instruction with “open a terminal.” The system treats it as the universal starting point while giving it no visible door.

Why it survives: obvious once you know it

Ctrl+Alt+T is a good shortcut. It’s memorable, it’s fast, and the moment you learn it the whole complaint evaporates — it feels obvious, and you stop being able to imagine not knowing it.

That’s the trap. Everyone with the power to fix this already knows the shortcut. Every maintainer, every packager, every long-time user filing bugs — for all of them the terminal is one reflex away, so the missing door isn’t visible. The only people who experience the problem are the ones with no standing to report it, and they stop experiencing it about ten minutes after they’d have written the bug.

This is the curse of knowledge doing structural damage: a defect that deletes its own witnesses. It explains a lot of what’s on this site — these aren’t hard problems, they’re problems that become invisible to anyone qualified to solve them.

The steelman

GNOME’s search-first design is genuinely fast once the vocabulary is in your head, and a deliberately sparse desktop is a defensible aesthetic — not every OS should ship a dock crammed with icons. There’s also a real argument that Ubuntu now targets people who should never need a terminal, and that putting a root-capable command line on the default desktop is a footgun for them.

But Canonical clearly knows people need it — they bound a dedicated shortcut to it. The decision wasn’t “users don’t need the terminal.” It was “users who need the terminal will already know.” That’s an assumption about prior knowledge, and it fails precisely on first contact, which is the only moment it matters.

The math

15M new Linux desktops/yr × 3 hunts × 180s = ~4 lifetimes / year

Small, because the population is small. The rate is brutal — near-universal among newcomers to a platform whose entire proposition is the command line.

The fix: no guesswork

The standard to aim at is simple — a new user should be able to open a terminal without guessing anything. Not a shortcut to memorise, not a name to recall, not a hidden second step. Three changes, in order of how much they matter:

1. Put it in the applications grid, visibly. Browsable, with an icon you can recognise without knowing its name. This is the one that actually solves it: recognition beats recall.
2. Pin it to the dock by default. One entry in the default favourites list. On a distribution whose core proposition is the command line, this is not a controversial use of a dock slot.
3. Fill out the search keywords properly — cmd, command prompt, shell, console, command line, bash, powershell. The .desktop spec has a Keywords= field for exactly this, so every vocabulary lands on the right app. It’s one line in a text file.

macOS gets this right the boring way: Cmd+Space and type, and it sits in Applications → Utilities where you can find it by looking. Two independent paths, one for people who know the name and one for people who don’t. That redundancy is the entire trick.

The principle: a shortcut is not discoverability. A keyboard binding is an accelerator for people who already know the feature exists. It can make a known path faster; it can never be how someone finds the path. Every feature needs at least one visible affordance, and “you can search for it” only counts when the user knows what it’s called.

Difficulty to fix: none

One line in the default favourites. The operating system whose great advantage is the command line should not require you to already know the command line’s name in order to find it.