Ubuntu Tips and Tricks: 6 Essential Checks and Mistakes

Most Ubuntu tips and tricks for new users are about the desktop: workspaces, themes, the Software app. Those are easy to find by clicking around. The tips below cover what new users usually find out the hard way: which release they are on and for how long it is supported, what Ubuntu Pro is, why one way of adding a user leaves the account without a home folder, and how to see what you actually installed. I checked every command on a fresh Ubuntu 26.04.1 LTS container, so the output and the errors are real.

Ubuntu tips and tricks on 26.04 LTS: useradd without a home folder, adduser, deluser needing perl, pro security-status and release upgrade check
Real lab output from Ubuntu 26.04.1 LTS.

This is the second set of Ubuntu tips and tricks on this site. The first, 8 Ubuntu tips and tricks for first-time users, covers apt update, remove vs purge, sudo rules and file permissions, so those topics are not repeated here.

Ubuntu tips and tricks 1: know your release

The first of these Ubuntu tips and tricks is the base for the rest: support dates and which guide applies to you depend on the release. The file that is always there is /etc/os-release:

$ grep -E '^(PRETTY_NAME|VERSION_CODENAME)=' /etc/os-release
PRETTY_NAME="Ubuntu 26.04.1 LTS"
VERSION_CODENAME=resolute

Many guides use lsb_release -a instead. On the minimal image it answered "lsb_release: command not found" (exit 127) until I installed the lsb-release package; then it printed "Release: 26.04" and "Codename: resolute". The codename matters when you add third-party repositories, because their instructions usually ask you to pick it.

2: Ubuntu Pro is there, and optional

Ubuntu ships the Pro client (pro). On an unattached machine pro status listed services such as esm-apps ("Expanded Security Maintenance for Applications"), esm-infra and livepatch, and ended with "This machine is not attached to an Ubuntu Pro subscription." Nothing is enabled until you attach a token, so you can ignore it at first. The more useful command is the security overview:

$ pro security-status 2>&1 | head -15
...
140 packages installed:
    140 packages from Ubuntu Main/Restricted repository

On a fresh install every package came from Main/Restricted; run it again after you add software and the report shows where the new packages come from. Both commands warn that their text output can change and point scripts to --format json or pro api; see the Ubuntu Pro client documentation for what each service does.

3: add users with adduser, not useradd

This is the one of these Ubuntu tips and tricks that saves the most confusion. Both commands exist, and they behave differently. useradd is the low-level tool:

$ useradd anna; ls -ld /home/anna; getent passwd anna
ls: cannot access '/home/anna': No such file or directory
anna:x:1001:1001::/home/anna:/bin/sh

The account points to /home/anna, but the folder was never created, and the shell is /bin/sh, not bash. Logging in as anna shows the result: "su: warning: cannot change directory to /home/anna: No such file or directory". adduser, Ubuntu's friendly wrapper, did the expected thing:

drwxr-x---+ 1 ben ben 54 Nov 18 14:06 /home/ben
ben:x:1002:1002:Ben:/home/ben:/bin/bash
.bash_logout
.bashrc
.profile

A home folder only its owner and group can enter (drwxr-x---), bash as the shell, and the default dotfiles. The adduser manual lists the options; I used --disabled-password and --comment to avoid the prompts.

Removing users had its own surprise on the minimal image:

fatal: In order to use the --remove-home, --remove-all-files, and --backup features, you need to install the `perl' package. To accomplish that, run apt-get install perl.

The account was not removed and the home folder stayed. On minimal servers and containers, check that perl is installed and check the exit status of deluser instead of assuming it worked.

4: check memory the right way

The System Monitor app answers "what is using my memory", and so does the terminal. free -h on the lab host:

               total        used        free      shared  buff/cache   available
Mem:            15Gi       9.2Gi       1.5Gi       2.3Gi       7.3Gi       6.1Gi
Swap:          8.0Gi       127Mi       7.9Gi

New users often panic at "free 1.5Gi". Read the available column instead: 6.1Gi, because most of the 7.3Gi of cache can be given back to programs at once. To find the biggest processes, sort by memory: ps -eo pid,user,%mem,rss,comm --sort=-%mem | head -5. That is one of the Ubuntu tips and tricks worth keeping in your notes, since it also works over SSH where no app can run.

5: see what you actually installed

After a few months nobody remembers why a package is there. apt-mark showmanual lists what was installed on purpose rather than as a dependency; the fresh image had 91 entries, among them coreutils-from-uutils next to gnu-coreutils. The logs give the when:

$ grep -E '^(Start-Date|Commandline)' /var/log/apt/history.log | tail -4
Start-Date: 2026-11-06  10:28:29
Commandline: apt-get --yes -oDebug::pkgDepCache::AutoInstall=yes --no-install-recommends --force-yes upgrade
Start-Date: 2026-11-18  14:06:33
Commandline: apt-get install -y -qq lsb-release ubuntu-pro-client ubuntu-release-upgrader-core procps htop

/var/log/dpkg.log has one line per package, including the dependencies apt pulled in. In my run the five packages I asked for also brought in screen. Keep these Ubuntu tips and tricks in mind before you clean up: removing something you did not install on purpose can take a needed program with it.

6: check for a new release before you upgrade

do-release-upgrade -c only checks and changes nothing:

Checking for a new Ubuntu release
There is no development version of an LTS available.
To upgrade to the latest non-LTS development release
set Prompt=normal in /etc/update-manager/release-upgrades.

The setting it mentions was Prompt=lts, so this system is only offered the next LTS release, which is what most people should want. Changing it to normal also offers you the non-LTS releases, as the message says. See the do-release-upgrade manual for the options.

More Ubuntu tips and tricks, quickly

  • Install htop for a clearer process view than top; it was 3.4.1 on 26.04.
  • Prefer the JSON output (pro status --format json) when you script Ubuntu checks.
  • Write down the codename and keep third-party repositories matched to it after an upgrade.
  • If settings go wrong, resetting Ubuntu to default settings without losing data shows how to reset them without touching your files.

None of these Ubuntu tips and tricks needs anything beyond a terminal, and all of them are safe to try: the only commands here that change the system are adduser, useradd and deluser, so try those on a test account first.

Comments

Popular posts from this blog

How to Play Minecraft Bedrock Edition on Linux: A Comprehensive Guide for Tech Professionals

Linux desktop frozen? My 5 go-to tricks to try - before forcing a hard reboot

The Ultimate Guide: How to Set Up DXVK in Wine on Linux for Enhanced Gaming Performance