Fix No Match for Argument: screen on AlmaLinux 8 (2026)

Skip the fluff. You’re on AlmaLinux 8, you just ran dnf install screen, and dnf came back with No match for argument: screen. Been there, done that. This isn’t a broken system and it isn’t a missing package — it’s a missing repository entry, and it takes about five minutes to fix.

Here’s the shortest path to a working screen command. Follow the steps in order, test as you go, and you’ll be back to business before your coffee gets cold.

Let me be real with you: every time I’ve seen this error, the story is almost identical. Someone is prepping a cPanel install, they run dnf install epel-release nano, and dnf prints a warning that basically says many EPEL packages require the CodeReady Builder (CRB) repository and you should enable it. That warning gets ignored. Then they swap the default repos for a local mirror to speed up downloads: back up /etc/yum.repos.d, create a fresh one, import the GPG keys, write a manual almalinux.repo file with baseos, appstream, and extras. Everything looks clean. Then they try to install screen so the long install session survives a dropped SSH connection — and boom, No match for argument: screen.

So what’s actually happening under the hood? On AlmaLinux 8, the screen package doesn’t live in BaseOS, AppStream, or Extras. It lives in a separate repository called CRB (CodeReady Builder), which early AlmaLinux 8 releases still called PowerTools. If your repo configuration was written by hand and only lists the three main repos, CRB simply isn’t registered. dnf has no idea the package exists, so it reports No match for argument: screen and Error: Unable to find a match: screen.

Here’s the part that makes this a two-layer trap. The custom mirror I was using hadn’t renamed its directories yet — the CRB content was still sitting under the old PowerTools folder. So even after I added the [crb] section with the right URL pattern, the baseurl pointed at a path that didn’t exist, and my curl validation came back 404. Two small mistakes stacked on top of each other: a missing repo section, and a wrong folder path. Both easy to fix once you know where to look.

Why dnf Can’t Find screen on AlmaLinux 8

Think of it like your grocery list. You know three stores in your neighborhood and you buy everything there. One day you need a specialty item, and it turns out only a fourth store — the one you’ve never added to your list — carries it. No matter how many times you walk through the first three stores, the item won’t appear. dnf and CRB work exactly like that.

The EPEL warning is the giveaway. When dnf tells you to run /usr/bin/crb enable, it’s not being chatty — it’s flagging that a whole family of packages will be unreachable until CRB is registered. I covered the deeper background in enabling the CRB repository on AlmaLinux 8, and it’s worth a read before you hit the next wall.

Fixing No Match for Argument: screen — Five Steps, In Order

Work through these one at a time. Don’t skip the validation step — it’s the one that saves you the most grief.

Step 1. Inspect the Current Repo File

Confirm whether the [crb] section is missing in the first place:

cat /etc/yum.repos.d/almalinux.repo

If you only see [baseos], [appstream], and [extras], you found the gap. If [crb] is already there, jump straight to step 5 and refresh the cache.

Step 2. Add the [crb] Section

Append the section to the end of the file with a here-doc:

cat >> /etc/yum.repos.d/almalinux.repo << 'EOF'
[crb]
name=AlmaLinux $releasever - CRB
baseurl=https://cermin.rumahweb.id/almalinux/$releasever/CRB/$basearch/os/
enabled=1
gpgcheck=1
countme=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
EOF

Swap the baseurl for whatever mirror or official repo you use. The rest of the options are standard: enabled=1 activates the repo, gpgcheck=1 verifies package signatures, countme=1 keeps dnf's usage stats accurate, and gpgkey must point to the key you imported earlier.

Step 3. Validate the Base URL Before Installing

This step is cheap and catches most of the pain. Check whether the repomd.xml file actually exists at the path you wrote:

curl -I https://cermin.rumahweb.id/almalinux/8/CRB/x86_64/os/repodata/repomd.xml

You want a 200 OK. If you get 404, list the mirror root to see the real folder names:

curl https://cermin.rumahweb.id/almalinux/8/

In my case, the mirror was still serving the old PowerTools directory instead of CRB. That's your clue for step 4.

Step 4. Fix the baseurl Path

sed -i 's#/CRB/#/PowerTools/#' /etc/yum.repos.d/almalinux.repo

This replaces every /CRB/ with /PowerTools/ across the repo file. Keep the [crb] section name as-is — it's just an internal label for dnf. What has to match is the folder path in baseurl, because that's the actual directory the mirror serves.

Step 5. Refresh Metadata and Install

dnf clean all
dnf makecache
dnf install screen

That's it. screen installs clean, and you can keep the install session alive with screen -S 'install_cpanel'. For the full picture on why that matters during a long setup, check out how to prepare a cPanel installation on a VPS.

Troubleshooting Reference

Symptom	Cause	Fix
No match for argument: screen	The repository holding the package (CRB/PowerTools) isn't registered	Add the [crb] section, then dnf makecache
curl returns 404 on the baseurl	Mirror folder name differs (CRB vs PowerTools)	Align the baseurl path with the mirror layout
Package still not found after adding the repo	dnf metadata cache is stale	dnf clean all then dnf makecache
GPG key errors during install	Key not imported or the gpgkey line is wrong	Import the key and match gpgkey to the repo file

Quick Notes From the Trenches

• Never skip the EPEL warning about CRB. It's not decoration — EPEL packages regularly depend on CRB libraries.
• Validate every baseurl with curl -I before dnf makecache. One HTTP call beats twenty minutes of head-scratching.
• When you switch to a local mirror, list its root directory first. Mirror maintainers are humans too, and folder names drift.
• Keep a backup of your original repo files. A bad edit is a one-line restore away.

If you're also thinking about a faster mirror setup, I wrote up switching AlmaLinux repos to a local mirror. And once screen is up, you'll want to compare it with tmux in screen vs tmux for long-running sessions.

FAQ

Before you close this out, run the three-second checklist: 1) the [crb] section exists in your repo file, 2) the baseurl returns 200 when you hit it with curl, 3) dnf makecache completed without errors. If all three pass, dnf install screen will work. Done.