Community-driven coverage of elementary OS — news, guides & forums
Dark abstract low-poly geometric landscape with layered triangular facets in deep navy, charcoal, and muted teal, illuminated by a soft electric-blue glow near the horizon

News roundups, tutorials, application guides, and forums — built by users, for users of the elegant Linux distribution.

elementary weekly
#20
Latest roundup · 18 Apr 2015
Freya Release
Final
Covered in weekly #19 & #20
Forum Topics
Active
Installation, customization & more

Checking and installing elementary OS updates manually

elementary OS makes routine maintenance approachable through its desktop tools, but checking and installing updates manually gives you more control over timing and visibility. The job has two main streams: operating-system packages handled by the updater and application updates handled through AppCenter or Flatpak. Recognising those streams prevents a successful app refresh from being mistaken for a fully updated system.

The graphical route remains the quickest choice for most people. Manual commands are useful when the desktop check is unclear, an update has stalled, or you want to review changes before installation. Whichever route you choose, work in a deliberate window, keep backups current, and allow enough time for downloads, configuration and a possible restart.

Choose the right update path

Start by identifying what needs attention. The operating system, its drivers and core libraries live in APT repositories, while many graphical applications arrive as Flatpaks or other packaged formats. AppCenter can display more than one format in its interface. The system updater and AppCenter may therefore show different pending items even when both appear to say that updates are available.

Update stream Usual interface Manual action Key distinction
Operating-system packages Software updater sudo apt update Refreshes indexes; packages are installed separately
Flatpak applications AppCenter flatpak update Uses configured Flatpak remotes
Debian packages installed separately AppCenter or Terminal apt list --upgradable Shows candidates after indexes are refreshed
Snap packages, if present Snap tools snap refresh Applies only to installed Snap packages

These package systems do not update one another. sudo apt update refreshes APT’s package indexes but changes no installed software. flatpak update updates Flatpak applications from their configured remotes. If you installed a Snap, snap refresh is a separate operation. Use the method belonging to the source, and check pending work in each relevant place instead of assuming one refresh covers everything.

Check for updates in the desktop

Open the applications menu and search for Software & Updates or the update utility supplied with your elementary OS release. Labels can differ slightly between versions, but the function is the same: connect to the configured repositories, compare versions and present a list. Keep an eye on the source of each repository as well; a third-party source should be one you deliberately added and still trust.

Choose the check option and allow the refresh to finish. A quiet window is not proof of failure, because package lists may be downloading quietly. Once the list appears, read the descriptions and look for a restart warning, a major desktop change or a security update. Those details are more useful than the number of packages, since one library update can affect many applications.

Choose one local update window and keep to it. A breakfast-time check suits many Perth users, while Sydney and Melbourne users might choose mid-morning. Brisbane keeps Australian Eastern Standard Time, and the south-eastern states shift for daylight saving, so clock changes and logs can differ. Schedule against the computer’s local time rather than a reminder created for another time zone.

Install operating system updates

For a manual installation, open Terminal with Ctrl+Alt+T and begin with sudo apt update. This downloads current package indexes from the configured repositories without installing the new versions. Follow it with apt list --upgradable to inspect candidates. Pay particular attention to packages from outside the standard Ubuntu repositories, because those maintainers can set their own release schedules.

sudo apt upgrade installs the eligible updates. If it reports that new packages are needed or leaves packages held back, sudo apt full-upgrade can apply the dependency changes required for a consistent result. The second command may install additional packages, so read its summary before confirming. Moving between elementary OS releases is a separate upgrade and should follow the release documentation rather than these routine commands.

Let the package manager finish before restarting. It may need to unpack files and run configuration steps that appear to pause, and a second updater will usually wait for the package lock. This is a good point to consider the connection: many metropolitan homes use NBN or another fixed broadband service, while regional users may rely on fixed wireless, 4G or 5G. A wired, stable connection is preferable for a large update.

Keep applications current

Open AppCenter and refresh its list, then review the application updates individually or as a group. AppCenter may combine Flatpak and Debian packages, so an icon does not always reveal the underlying format. Closing an application is sometimes required before its replacement can be installed. Save open documents first, especially when the application holds unsaved work or synchronised files.

Flatpak applications can be updated with flatpak update, while Snap packages use snap refresh if Snap is installed on the machine. A standalone .deb file is an APT package; install a local file with sudo apt install ./package.deb, then let the normal APT updater maintain it. Two copies of the same program can sit under different formats without either updater noticing the other. flatpak list and apt list --installed help reveal duplicates before you decide what to remove.

Do not uninstall a duplicate casually. Some applications store settings and documents inside their own sandbox, so removing one copy may discard data that the other never had. Back up anything important, check which copy owns your files, and keep the format you use regularly. The aim is a predictable update path, not simply the newest version visible in the centre.

Update notices can be difficult to read with a busy display or weak contrast. If you rely on visual assistance, the guide to magnifier and contrast explains how those elementary OS display controls can be arranged before you approve changes or read small release notes.

Handle prompts and restarts

Permission prompts, application warnings and restart requests are normal parts of maintenance, but each deserves a quick check. Confirm that the requesting application belongs to your system and that the wording matches the action you initiated. Avoid pasting commands copied from an unknown forum post or message. If a prompt appears while you are not running an update, cancel it and investigate rather than granting broad access.

Plan the restart around your work. Save documents, close sensitive applications and reconnect external drives before rebooting. A suitable slot might be a quiet tea break or early evening rather than an arvo meeting, when you can respond to a restart request without rushing. Long weekends and school holidays are common Australian downtime, which can be useful for updates that need a longer, uninterrupted window.

Keep a laptop connected to mains power and maintain a reasonable battery charge during a substantial installation. A brief loss of power while packages are being unpacked can leave the system needing repair. This matters for a mixed household hardware base, from newer laptops sold through Australian retailers to older desktops kept for years, because recovery may require more time than the original update.

Troubleshoot common update problems

Read the first error rather than repeatedly clicking Install. A failure to fetch usually points to connectivity, DNS or an authentication portal. Check the network with another service, then retry. A hash mismatch suggests a corrupted download or mirror problem, while a 404 can mean that a third-party repository has removed a package. In the last case, inspect the repository rather than disabling security updates or changing distribution sources blindly.

Lock messages and permission errors often mean another package process is active, including an unattended security update. Wait for it to finish, and do not delete Debian’s lock files by hand. If APT reports broken dependencies, sudo apt --fix-broken install can propose a repair after you inspect the plan. Share the exact error when seeking community help; a generic description of “updates not working” hides the useful detail.

Storage failures are common when a partition is nearly full. Check free space with df -h, then clear downloaded package archives with sudo apt clean if necessary. That command does not remove installed applications or personal files. If a release upgrade was the intended task, return to the documented release procedure; the ordinary update tools are not designed to move the whole distribution forward.

When an update window depends on a regional trip, regional travel planning can help coordinate where you will have time and a dependable connection. Finish sensitive authentication on a trusted network rather than an open public hotspot. If bandwidth is limited, sudo apt upgrade --download-only can stage downloads for later installation.

Make manual updating a calm routine

A workable routine has three parts: check, install and verify. Check the system updater and AppCenter on a regular weekly schedule, note any restart requirement and reserve a longer block for larger releases. A monthly review of application updates catches browser and productivity tools that can sit idle while the operating system itself reports no changes.

Before installing, check free disk space, save your work, plug a laptop into power and confirm that the connection is stable. After installation, restart if requested, reopen AppCenter and run another check. Verification matters because a package may download successfully yet still be waiting for configuration, a reboot or a decision about a held dependency.

The release number shown in the About panel may remain unchanged during ordinary patch updates, so it is not a reliable progress indicator. An empty upgrade list and no pending Flatpak work are more useful confirmation. Keep a short record of major version changes and successful restarts; that history makes a future support question much easier to diagnose.

The practical takeaway is to check first, update in one uninterrupted window and reboot only when required; this small routine keeps elementary OS predictable without turning maintenance into guesswork.

Browse the News Archive
Latest Updates

From the elementary weekly series

Low-poly faceted abstract render in dark charcoal and electric blue tones, suggesting a news bulletin or announcement
elementary news

elementary weekly #20

The first week with the final Freya release — community reactions, tips, and early impressions gathered in one roundup.

Abstract low-poly geometric scene in midnight blue and soft cyan, conveying a live broadcast or event atmosphere
elementary news

elementary SPECIAL

A live Hangouts event with the elementary OS founders, held on 11 April 2015, discussing the Freya final release.

Low-poly faceted render in deep navy and muted teal with subtle amber highlights, suggesting a tutorial or guide
Tips and Tricks

Timeshift Guide

How to use Timeshift — the intuitive system restore utility for elementary OS — to recover from configuration mishaps.

Explore

Topics & Resources

Dive into guides, application recommendations, and community discussions covering every aspect of elementary OS.