Linux Mint: The First Hour After Install
Last tested on:
- Linux Mint 22.3 (XFCE — steps are identical on Cinnamon and MATE)
- Hardware: HP 15-bs0xx (Pentium N3710) & ASUS VivoBook X509UA (i3-7020U)
You installed Linux Mint. GRUB works, Windows still boots, and the desktop is waiting. This is the first hour: five tasks, in the order they should happen. Mirrors come first, because every update you will ever pull travels through them. Software installation comes before updates, because you need to know what a package is before the numbers start disagreeing. TimeShift comes before anything risky, because an undo button you configure afterward is no undo button at all. Tethering comes last, because it's the backdoor you hope never to need.
Every step stands alone. The failure recoveries live in collapsibles; the four field reports behind them — two incident reports, one drill, one field note — sit in the Appendix, each linked from the step that spawned it. Skip them all and lose nothing.
Haven't installed yet? Start with the installation guide: How to Install Linux Mint (All Editions) on a Windows 11 Laptop.
Step 1: Optimize Your Software Mirrors {#step-1-mirrors}
Mirrors are the software servers that host Linux Mint's packages. Picking a fast one speeds up every download and update for the life of the install — this takes about two minutes.
1. Open the menu and launch Software Sources.
2. Click Main repository (the default, e.g. zena). Mint runs a speed test against every available mirror — about a minute.
3. Pick the fastest one (top speed in KB/s or MB/s). It doesn't have to be geographically close to you.
4. Click Apply.
5. Repeat for the Base repository, then Apply.
6. Click the green refresh icon to update the cache. Give it a few minutes.
Figure 1: The two screens that bracket the operation. The speed test ranks mirrors by how fast they answer — Liquid Telecom on top here, cloud.mu unreachable — and once both repositories are Applied, the green button is what kicks off the cache refresh in step 6.
Note: The speed test ranks mirrors by how fast they answer, not how long they can carry a download. The top pick is usually right — but if a refresh ever stalls, the fix is simply taking the next mirror down the list.
On a bad network day, that final cache refresh can lock up — sometimes for half an hour at a stretch. If it happens to you:
🚨 The cache refresh froze — or the shield went red
A stalled mirror fetch does not mean your system is broken. It means the connection somewhere stopped delivering mid-download, and Mint's GUI is holding the line open — politely, forever. It's rare, but on unreliable networks it happens. The recovery path below goes from least to most invasive. Stop the moment the GUI frees.
The frozen window: controls greyed, the cache bar stretched, no error and no timeout. This is the state the recovery path below assumes — a fetch that stopped delivering while the GUI holds the line open.
1. Read the red shield correctly.
If the Update Manager shield turned red, you saw this:
"Could not refresh the list of updates — Your APT configuration is corrupt. Do not install or update anything — doing so could break your operating system! To switch to a different Linux Mint mirror and solve this problem, click OK."
Translation: This is Mint's standard reaction to a failed mirror fetch. It clears the moment a refresh succeeds. It is not a verdict on your system.
The notification itself: alarming wording, harmless meaning. Mint is reporting a failed fetch, not a broken system — and the line that matters is the last one, which is the actual fix.
2. Wait before touching anything.
Freezes often resolve on their own — in my testing they cleared in 2–6 minutes, and the longest ran 23 minutes. One freeze outlasted 30 and I ended it with a shutdown; that story's in the incident report.
3. Identify before you kill.
Open a terminal and run:
ps aux | grep apt Read what's actually listed. The holder's name depends on the door: on Mint 22.3 the GUI's fetch runs through a Python script named aptk (/usr/sbin/aptk); a terminal update runs through apt-get. Kill what ps shows — not what you remember. Ignore the tourists: grep matches substrings, so unrelated lines like --adaptive will appear in the output too.
The anatomy, live: one holder (aptk), four workers, and the tourists that match on substring rather than on being apt. Read this before you kill anything — the frame is the lesson, and it is the same output the prose walks through line for line.
4. Kill the holder.
In every capture taken for this guide, the GUI's holder answered to aptk — so:
sudo killall aptk Safety line: this only holds for a cache refresh — no package transaction is in flight, so there's nothing half-installed to damage; the refresh restarts the moment you click the icon again. Mid-install is different — see the Installing Software step's lock note before killing anything. Killing the wrong name changes nothing. Target what step 3 showed you. (This is the documented recovery path — my freezes released before I needed to fire it in sequence. And a confession: my own first draft of this step named the holder aptd, from memory. The capture in step 3 says aptk. The rule caught me too.)
5. Clear the lock, if the error persists.
If you now get "Could not get lock /var/lib/apt/lists/lock": confirm nothing's alive with ps aux | grep apt, then remove the lock your error names:
sudo rm /var/lib/apt/lists/lock The other usual suspects are /var/cache/apt/archives/lock and /var/lib/dpkg/lock-frontend. Remove only the one named in your error. Locks are protection, not obstacles — but when the holder dies mid-fetch, the lock outlives it and blocks the next attempt.
6. Reselect and verify.
Back in Software Sources, take the next mirror down the list — not the one that stalled. Apply, then hit the green refresh icon. The shield returning to normal is the exam passed.
Fixed it — or just curious why the GUI froze solid while a terminal sudo apt install kept working on the same machine at the same time? The full teardown — two laptops, one 23-minute freeze, one forced shutdown, and what ps was actually showing — lives in Incident Report: The Mirror Cache Freeze at the end of this guide. It's a read for the curious. Skip it, and you lose nothing.
Step 2: Installing Software on Linux {#step-2-installing-software}
Linux organizes software differently than Windows. There's no single .exe to download from a website — instead, software arrives as packages from repositories (curated software libraries your system trusts). Mint uses two package systems side by side, and understanding the difference between them will save you a lot of confusion later, especially when you run your first system update.
The two systems:
- System packages (
.deb) — the native Linux format, maintained and vetted by Mint and Ubuntu developers. They're tightly integrated with your system, relatively small, and updated through the distro's own release cycle. When you runaptin the terminal, this is what you're working with. - Flatpaks — sandboxed packages that bundle their own dependencies, distributed through Flathub. They're isolated from your system (a security advantage), but larger on disk because they carry their own libraries instead of sharing the system's. They update independently of Mint's cycle. The terminal command for these is
flatpak, notapt.
Neither system is "better." Most users end up with a mix of both, and Mint's tools handle them together so you don't have to think about the distinction most of the time. But when the numbers don't add up during an update — and they will — this is why.
Method 1: The Software Manager (GUI)
1. Open Software Manager from the menu.
2. The first time you open it — or after changing mirrors — the search may sit empty for two or three minutes while the catalog indexes. It's working, not hung.
3. Type the name of the app you want in the search bar.
4. Expect a flood of results. Searching vlc returns the player itself plus a dozen entries with hyphenated suffixes: -plugin-, -backend-, -bin, -bindings. These are parts of the program, not the program. The one you want has the plain name, a human-readable description, and usually a star rating.
5. Click on it. On the detail page, look at the top right, just under the Install button:
- "System Package" chip = a native
.deb. - Cube icon + "Flathub" badge = a Flatpak.
- Some apps appear twice — one of each. Search
firefoxand you'll see both. A green check on one of them means it's already installed. 6. Click Install, enter your password, let it run.
Figure 2: The flood, on screen. The tile you want is the plain name with a human description and a star rating — top-left here. Everything around it (-plugin-, -backend-, -bin, -bindings) is a component other programs depend on, not the program itself.
Figure 3: The twins. Same app, two package systems. The green check marks the installed native .deb; the cube plus Flathub badge marks the sandboxed Flatpak. Some apps appear twice exactly like this — firefox being the obvious one.
Figure 4: The chip, in place. System Package beneath the Install button means a native .deb; a cube plus Flathub badge here would mean a Flatpak. Note the size line — 19 MB to download, 83 MB of disk — the same figure the blockquote below unpacks, and the plugin list echoing the flood from Figure 2.
Two numbers on the detail page: "19 MB to download, 83 MB of disk space required." Not a contradiction — the download is the compressed package traveling over the wire; the disk size is what it occupies once unpacked and installed. Same program, measured before and after the squeeze.
Method 2: The Terminal (apt)
1. Refresh the package index:
sudo apt update Enter your password when prompted. This doesn't install anything — it just downloads the latest catalog of what's available.
2. Install a package:
sudo apt install <package-name> Read the output before confirming. It tells you exactly what will be downloaded, how much disk space it will use, and whether any additional dependencies will be pulled in.
3. Type Y + Enter to confirm.
4. To remove a package later:
sudo apt remove <package-name> 5. To clean up leftover dependencies nothing needs anymore:
sudo apt autoremove
autoremoveis not a kernel pruner. On both test machines — before and after a fresh kernel install — it swept nothing. Old kernels pile up quietly, and the deliberate tool for trimming them is Update Manager's Linux Kernels window. Removing kernels is the one housekeeping act that can strand your boot path; leave it alone until you know what you're cutting.Package names are case-sensitive and must be exact.
sudo apt install Firefoxwill fail.sudo apt install firefoxwill work. If you're unsure of the exact name, search for it first withapt search <keyword>or check the Software Manager.
Key Differences to Remember
- The Software Manager shows everything —
.debpackages, Flatpaks, and third-party repo packages — all in one list. The terminal'saptcommands only see.debpackages. If an app is Flatpak-only,apt installwon't find it. Useflatpak install flathub <name>instead, or just use the GUI. - The search flood is normal. Those hyphenated plugin entries are real packages — they're just components that other programs depend on. You almost never install them directly.
- Not every app is in Mint's repositories. Some software isn't packaged for Linux at all, and some exists only as a Flatpak or a manual download. If the Software Manager and
apt searchboth come up empty, the app's official website is your next stop.
When You Can't Find a Package Anywhere
Sometimes the app you need isn't in the Software Manager or apt. This usually means one of three things:
1. It's a Flatpak you need to install manually.
Some apps are only distributed through Flathub. The terminal command is:
flatpak install flathub You can find the exact app ID by searching on flathub.org.
2. It's a standalone .deb from the developer's website.
Some projects (like VS Code, Google Chrome, or Discord) provide a .deb file for download. Once you have it:
sudo apt install ./path-to-file.deb Using apt install instead of dpkg -i is important — apt will automatically fetch any missing dependencies, while dpkg will just fail and leave you to chase them manually.
3. It needs a PPA (Personal Package Archive).
Some developers maintain their own Ubuntu/Mint repositories. Adding one typically looks like:
sudo add-apt-repository ppa:<developer>/<project> sudo apt update sudo apt install <package-name> PPAs are not vetted by Mint. Only add them from developers you trust, and read the project's official installation instructions before running anything.
🧱 A tutorial told you to snap install — and Mint refuses
Plenty of internet tutorials start with snap install something. On Mint, that door is welded shut on purpose:
$ sudo apt install snapd E: Package 'snapd' has no installation candidate Nothing is broken — not the repository, not your setup. That line is distro policy speaking through apt's mouth: Mint chose Flatpak as its sandboxed format and dropped snap entirely. The refusal is the feature working.
The whole session behind the fence's two lines. snap is missing, the system points you at snapd to fetch it, and snapd itself has no candidate — the red line is the fence's excerpt, shown here inside the chain that produced it. The door is welded shut from both sides.
What to do instead: skip the snap install step and look the app up in the Software Manager — cube icon + Flathub badge means it's there in Mint's sanctioned sandbox. If it's genuinely not listed anywhere, the Flathub site is the authoritative source for what exists.
🧱 "Waiting for cache lock" — apt is standing in line, not broken
Run an apt command while the Software Manager or Update Manager is mid-download and you'll see this wall scroll past:
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 6205 (aptk) This wall, scroll past, made literal: the same line repeated twenty times, the same holder — 6205 (aptk) — every time. Read the first word, not the count: Waiting. apt is queuing behind the GUI, not refusing.
Read the first word: Waiting. apt isn't refusing — it's queuing behind the GUI and resumes the moment the line moves. On our bench it waited 142 seconds, then carried on by itself. Beginners who've seen this wall have been panicking at a queue this whole time.
So the correct move is: wait. This is the exact opposite of the mirror freeze. There, the holder was a stalled fetch with no package work in flight. Here, the holder is mid-install — real package work. Killing an installer mid-transaction is how you actually damage package state. Let the queue resolve.
If the wait truly never ends (many minutes, nothing moving anywhere): confirm the holder is actually dead first — ps aux | grep apt shows nothing alive — then choose by what it was doing:
- It was installing (a progress bar was moving): repair any half-finished state, then retry:
sudo dpkg --configure -a - It was only refreshing the cache (the Mirrors freeze): no package state was in flight — use the Mirrors step's lock-clearing path.
A Note on Drivers
Linux Mint includes a Driver Manager (Menu → Driver Manager) for proprietary hardware drivers — most commonly Nvidia graphics cards, some Broadcom Wi-Fi chips, and certain printers or scanners.
Neither laptop used for this guide ever showed anything in Driver Manager, on a fresh install or on any later check: "No drivers needed — Your computer does not need any additional drivers." That's not a malfunction — it almost always means your hardware is already fully supported by Mint's default, open-source drivers, which is the common case for most mainstream laptop hardware. An empty Driver Manager is a good sign, not a missing step.
The good sign, on screen: an empty Driver Manager is not a malfunction. For most mainstream hardware — both laptops here included — the default open-source drivers already cover everything, so this blank window is the correct result. The populated case (an Nvidia card listing an Install option) is the one state I never saw on either machine, which is why the section points you to the official docs for it instead of guessing at a flow I didn't run.
If you do have hardware that needs a proprietary driver — an Nvidia GPU is the most common case — Driver Manager will list it with a clear "Install" option. I haven't personally walked through that flow on either test machine, so rather than guess at steps I've never run, here's where to go instead:
- Linux Mint User Guide — official documentation
- Your hardware manufacturer's official Linux driver page, if one exists
This is one of the only places in this guide where I'm pointing you elsewhere instead of walking you through it myself — and that's deliberate. I'd rather tell you honestly that I haven't tested it than hand you a confident-sounding process I made up.
Step 3: TimeShift: Your System's Undo Button {#step-3-timeshift}
Timeshift is Mint's built-in rollback tool — not a personal backup app. If an update or experiment breaks your system, Timeshift restores it to an earlier working state. It does not protect your documents, photos, or downloads — /home is excluded by design. That's a separate job, for a separate tool.
Setup — one-time, under two minutes:
1. Open Timeshift from the menu. The setup wizard launches automatically on first run.
2. Snapshot Type: Leave it on RSYNC — on an ext4 system it's the only available mode, not a recommendation. (The BTRFS option only activates on systems actually running BTRFS — on ext4, RSYNC is the only door.)
3. Snapshot Location: Your Linux root partition is pre-selected and is the only valid target — the wizard blocks NTFS/FAT outright. A dual-booter physically cannot point a snapshot at the Windows drive, even by accident.
4. Schedule: Daily, keep 5 is the default. On a smaller SSD (256GB or less), trim this to 3 to curb space creep over time.
5. Home Directories: Leave Exclude All checked, for both your user folder and root. This keeps Timeshift doing exactly one job — system state, not personal files.
6. Click Finish.
7. Back in the main window, click Create to trigger your first snapshot now. Don't wait for the schedule — you want a baseline sitting there before you ever need one.
Figure 5: the four wizard decisions, on screen. RSYNC is the only live option because this is ext4; the location panel lists no Windows partition because the wizard blocks NTFS outright; Daily/Keep 5 is the default schedule; and both root and the user home are excluded — which is the whole point, Timeshift guards system state, not your files.
The armed tool, before the first snapshot: zero entries, rsync active, Create and Restore waiting in the toolbar. This is the state at the end of setup — configured, forgotten, still working — and the only view that shows where Restore lives for the restore flow below.
Restoring a snapshot, if you ever need to:
1. Open Timeshift and select a snapshot from the list.
2. Click Restore.
3. Review the Confirm Actions screen before confirming anything — it lists every file Timeshift is about to create, restore, or delete, in advance.
4. Confirm. The system restores the files and reboots automatically.
Figure 6: the read-before-confirm screen. The very first line is the wound Timeshift found and named — Create /etc/motd — and everything under it is the drift a restore rolls back alongside it: firmware metadata, network state, disk logs, timer stamps. None of it is /home; the exclusion held. This is why you review this list before you click, not after.
Know the limits before you rely on it: snapshots live on the same disk they protect — if the drive fails, the snapshots fail with it. Restoring rolls back everything since that snapshot, not just the one thing you're trying to undo, so you'll lose any updates or changes made in between. Snapshot before you experiment, not after something breaks.
The numbers in the Timeshift window can look alarming on their own — a single snapshot claiming several gigabytes, times five scheduled copies, on a drive that doesn't have that much room to spare. It's not what it looks like. Here's how to check it yourself.
🤔 The misconception about Timeshift's disk usage
Run a size check on a single snapshot folder and you'll see a number that looks like a full copy of your OS — several gigabytes, easily. Multiply that by five scheduled snapshots and the math looks like Timeshift is about to eat your entire drive. It isn't. Here's how to verify that yourself instead of taking my word for it.
What the disk actually holds (ground truth):
df -h / This is your root partition's real, total usage — snapshots included, nothing hidden.
What each snapshot actually costs:
sudo du -sh /timeshift/snapshots/* Run against all your snapshots in one command, and the sizes come back small. RSYNC mode doesn't copy unchanged files between snapshots — it hardlinks to data already on disk. A snapshot only costs you new space for files that actually changed since the last one.
What one snapshot actually contains:
sudo du -sh /timeshift/snapshots/<folder-name> Run it alone, pointed at a single snapshot folder, and the number jumps — because now you're measuring every file it points to, shared or not. That's not what it cost you. That's what it contains.
Run it yourself and the rule becomes visible: df tells you what the disk holds, du across all snapshots tells you what each one cost, du on a single snapshot tells you what it contains. The combined figures stay small because RSYNC hardlinks unchanged files; the solo figures balloon because now you are counting shared data too. Neither number is wrong — they answer different questions.
The rule: df -h / tells you what your disk actually holds. du across all snapshots tells you what each one cost. du on one snapshot alone tells you what it contains. Three different numbers, all true — pick the one that answers the question you're actually asking.
Care to see how I put this to the test — deleted a system file on purpose, restored it through the GUI, and nearly misread my own proof twice? The full drill — the wound, the restore, two self-caught misdiagnoses, and the metadata that settled it — is in the TimeShift Drill Report at the end of this guide. Fixed or just curious, you lose nothing by stopping here.
Step 4: Keeping Your System Updated {#step-4-updates}
Updates patch security holes and keep your kernel and drivers current. Two equivalent paths — pick whichever fits your flow.
Method 1: The GUI (Update Manager)
1. Click the shield icon on the panel bar — or search for Update Manager in the menu.
2. A list of available updates appears.
3. Install Updates applies everything, or untick anything you want to skip — the checkboxes are yours.
4. Enter your password.
5. Let it run.
6. When it's done, the shield reads "Your system is up to date."
Figure 7: the two states the GUI walks you through. The list appears at step 2 — three logical rows here, each a ticked checkbox you can untick — and the shield closes at step 6 once the batch is applied. The footer's 3 updates / 886 KB is the GUI's own tally; the terminal counts the same work differently, and that gap is the field note's subject, not this step's.
Method 2: The Terminal
sudo apt update Refreshes the package index. When it finishes, it reports how many packages are upgradable.
apt list --upgradable Shows exactly what's pending — every package, listed individually. Read-only, no password needed. The GUI shows the same packages grouped into fewer rows, which is exactly why its counts and size quotes differ from the terminal's — the Field Note has the numbers.
sudo apt upgrade Starts the update. Type Y + Enter when prompted, and let it complete.
flatpak update Updates your Flatpaks. apt can't see them (see the Installing Software step), so a terminal-only routine needs both commands. The Update Manager handles both kinds in one list — one reason its totals rarely match the terminal's.
Note: The terminal has no checkbox screen —
sudo apt upgradeupdates everything by default. To update a single package without touching the rest, usesudo apt install --only-upgrade <package>. It may bring tightly tied companions along — upgradingfirefoxalso upgradedfirefox-locale-enon the test machine — but everything else stays exactly where it was.
The GUI said 893 KB once. The terminal said 216 MB for the exact same update. Neither was wrong — they just don't use the same ruler. The full breakdown — two machines, two kinds of mismatch, one shared cause — is in the Field Note at the end of this guide. Purely optional.
Step 5: USB Tethering — The Wi-Fi Backdoor {#step-5-usb-tethering}
Sometimes Wi-Fi just dies — a bad driver, a kernel update, a fight with your wireless card that you didn't start and can't immediately win. When that happens, you still need a way online to search for a fix, download a driver, or roll back a kernel. USB tethering turns your phone into a wired lifeline: plug it in, and your laptop treats it like an ethernet connection.
Android:
1. Connect your phone to the laptop with a USB data cable (not a charge-only cable).
2. Turn mobile data on
3. Enable USB Tethering — usually in the notification shade, or under Settings → Network & Internet → Hotspot & Tethering (on Samsung phones: Settings → Connections → Mobile Hotspot and Tethering).
The Android door, open. USB tethering is one option in this list — not the selected one yet (file-transfer is lit here), so this is the screen where you choose it. The lesson is in the words, not the pixels: pick USB tethering from this list after mobile data is on, and Mint takes it from there.
4. Linux Mint detects it automatically as a wired connection. No terminal, no setup. If your phone has mobile data, you're online.
iPhone:
1. Turn mobile data on
2. Go to Settings → Personal Hotspot and switch it on (The hotspot shares the phone's mobile connection over the cable — with data off the link forms but no internet flows, and Mint's wired icon won't finish the handshake.)
Where the hotspot lives on iOS — the Personal Hotspot row in the first Settings group. Switch it on here, after mobile data, and the cable handshake completes on its own; Mint ships the iPhone driver, so there is no terminal step waiting behind this screen.
3. Connect the iPhone to the laptop with a USB cable.
4. The phone will prompt "Trust This Computer?" — tap Trust, and enter your passcode if asked.
The gate, on screen. Tap Trust and enter your passcode; declining it is the most common way tethering fails silently on your own laptop. The dialog is the whole instruction — there is no confirmation screen after it, just the wired icon in Mint's tray once the link forms.
5. Check the network icon in the Mint taskbar — it switches to a wired/ethernet icon once connected.
Always tap Trust. There's no reason to decline it on your own laptop, and skipping it is the most likely way this fails silently.
This isn't a permanent fix — it's a bridge to get you online long enough to actually solve the Wi-Fi problem. Speaking of which:
🧯 Wi-Fi suddenly dead? Try the previous kernel first
If Wi-Fi was working fine and then vanished right after a routine update, the new kernel is the prime suspect — not your hardware. Kernel updates occasionally ship without full driver support...



















