How to Update WPS Office from Terminal on Ubuntu

To update WPS Office from the terminal on Ubuntu, first identify whether you installed a Deb package or a Snap package. A Deb from the official WPS Linux page does not register a vendor APT repository, so sudo apt upgrade usually will not move WPS forward. The reliable Deb update is to download the newer official Deb and install that exact local file over the existing package. If you installed via Snap, use Snap refresh instead.

Ask Ubuntu’s “How do I update WPS Office to the latest version?” reports the exact confusion people still hit: they look for a Windows-style Check for Updates control, cannot find it, and assume they are stuck. Missing that button is not a dead end—it means you update through the packaging channel you originally used. Success means the installed version string increases and Writer still opens after the update.

Why “Check for Updates” Searches Lead People Astray

Windows help articles often show an in-app updater. On Linux builds, that control may be missing or incomplete. Community answers therefore split into two correct camps: Snap users should refresh the snap; Deb users should install a newer .deb with APT’s local-file form. Mixing those answers—running snap refresh when you only have a Deb, or waiting for apt upgrade when no WPS repository exists—is why people conclude “terminal update does nothing.”

In the Ubuntu 18.04 update thread, one answer correctly routes Snap users to sudo snap refresh wps-office, while another shows the Deb pattern sudo apt install ./package_name.deb after downloading a package. Both can be right—on different machines. Your job in the terminal is not to memorize every answer; it is to detect which packaging world you are in, then apply only that world’s update command.

Map Your Install History Before You Upgrade

Think through how WPS arrived on the computer. Did you click Deb Package on the official Linux page and double-click or APT-install a file from Downloads? Did Software / Snap Store install a snap? Did an older tutorial tell you to wget a versioned URL and run dpkg -i? Each path leaves different evidence:

• Deb path: dpkg -l wps-office shows ii, and you may still have a .deb in Downloads
• Snap path: snap list shows a WPS-related snap, and snap connections may list plugs
• Broken leftover path: APT complains about reinstall archives, or both Deb and Snap traces exist

If your history is unclear, run the detection commands in the next section and trust those outputs over memory. Updating the wrong channel cannot raise the version string you care about.

Detect the Channel Before You Type Upgrade Commands

dpkg -l wps-office
snap list 2>/dev/null | grep -i wps
command -v wps
command -v wps-office

Interpret the signals carefully. An ii row for wps-office means Deb/APT packaging. A Snap list entry means Snap packaging. If both appear, you may have conflicting installs—decide which launcher you actually use daily, then update only that channel. Updating the wrong channel is the fastest way to waste an afternoon and still see the same About dialog version.

Record the Version You Have Now

dpkg -l wps-office
snap info wps-office 2>/dev/null | sed -n '1,40p'

Save this output in a text file or screenshot. Without a before/after comparison, you cannot tell whether the terminal update applied a newer build or silently reinstalled an older Deb that was still sitting in Downloads. For Snap, note both the tracking channel and the revision if snap info shows them.

Update a Deb Install: Newer Official File, Same APT Pattern

Community answers that suggest sudo apt --only-upgrade install wps-office only help when a repository actually publishes that package. The official Deb download workflow typically does not. Use this path instead:

1. Open the official WPS Linux page.
2. Download the current Deb Package for your architecture.
3. Confirm architecture still matches with dpkg-deb -I.
4. Install the local file with APT.

cd ~/Downloads
sudo apt update
sudo apt install ./wps-office_NEWERVERSION_amd64.deb

Expected result: APT replaces/upgrades the existing wps-office package. You normally do not need to uninstall first. Uninstalling first is a last resort when the package database is already corrupted, not a routine step for every update.

If dependencies break mid-upgrade:

sudo apt --fix-broken install
sudo dpkg --configure -a

Then compare versions deliberately:

dpkg-deb -I ./wps-office_NEWERVERSION_amd64.deb | grep Version
dpkg -l wps-office

The installed version line should match the Deb you intended. If it does not, you likely installed an older file still present in Downloads—sort by modification time and pick the newest official download.

Practical Deb Update Walkthrough

Here is a concrete sequence that mirrors how careful Ubuntu users recover when “apt upgrade did nothing”:

mkdir -p ~/Downloads/wps-update && cd ~/Downloads/wps-update
# Download the current Deb from the official WPS Linux page into this folder
ls -lt
dpkg-deb -I ./wps-office_*.deb | grep -E "Package|Version|Architecture"
sudo apt install ./wps-office_*.deb

Prefer one Deb in that folder so a wildcard cannot grab the wrong file. If Downloads is messy, move only the newest official Deb into a clean directory first. After APT finishes, reopen Writer from the menu and check About / version information if your build exposes it, then compare with the earlier dpkg -l snapshot.

If APT prints dependency problems, resist the urge to paste the first outdated libpng12 workaround you find. Those workarounds were written for older WPS builds on older Ubuntu releases. On a current official Deb, start with sudo apt --fix-broken install and only install packages APT names explicitly.

Update a Snap Install: Refresh the Snap

When Ubuntu answers identify a Snap install, the terminal update is:

sudo snap refresh wps-office
snap info wps-office

Snap packages are designed to refresh automatically; the refresh command forces an update check. Use the exact snap name from snap list if your install is named differently (for example a multilanguage snap). Snap Store packaging is a different channel from the vendor Deb/Rpm downloads—do not call it the official Deb path, and do not expect Deb update recipes to move a Snap install.

If refresh reports the snap is already on the latest revision, your update problem may actually be a feature or permission problem rather than a version problem. Re-test document open paths and snap connections before downloading random third-party packages “to force an update.”

Choosing Between Refresh and a Full Channel Switch

Sometimes the real goal behind “update WPS” is “make USB / second HDD documents work” or “stop a crash.” Updating in place helps when the bug is fixed in a newer build. It does not help when Snap confinement blocks a second disk—those Ask Ubuntu reports are solved by connecting removable-media or migrating to Deb, not by refreshing forever. Likewise, a Deb install stuck on an obsolete dependency story is often fixed by installing a current official Deb, which is an update and a repair at the same time.

What Will Not Update a Deb WPS Install

• sudo apt update && sudo apt upgrade alone when no WPS repository exists
• Expired community wget URLs pointing at old builds
• Unofficial PPAs that claim to track WPS without vendor documentation
• Waiting for a Windows-style in-app updater that your Linux build does not expose
• Running Snap refresh when dpkg -l shows Deb and Snap list is empty

Post-Update Verification Checklist

1. Compare old and new version strings from the commands above.
2. Launch a confirmed binary or menu entry on a graphical session.
3. Open one existing document and save a trivial edit.
4. If you rely on USB drives or a second HDD, re-test those paths—especially if you are on Snap confinement, where removable-media connections matter.
5. If fonts warnings appear only after an upgrade, treat them as a separate issue from “update failed.”

Update Failures and Safe Fixes

APT offers to remove wps-office during the “fix”

Abort removal unless you intend to uninstall. Read the dependency names, fix what Ubuntu can provide, or download a different current official Deb. This is the same trap install threads document when apt-get install -f tries to delete a half-configured package.

Version string did not change

You may have reinstalled an older Deb still sitting in Downloads, or refreshed a Snap that was already current. Re-check file timestamps and snap info.

App fails to start after update

sudo dpkg --configure -a
sudo apt --fix-broken install

Reinstall the same newer Deb if the package is half-configured. Destructive purge is last and only after you back up documents.

snap refresh finds nothing

Run snap list | grep -i wps. If Snap is absent, you are on Deb—use the Deb update path. If the snap uses another name, refresh that exact name.

Need features that still fail after updating

Some usability issues—slow open times, second-disk permission errors, printer discovery—are channel/confinement problems rather than version problems. Updating alone will not fix a Snap removable-media gap; connecting the interface or moving to Deb may be required.

FAQ

Can I update without reinstalling?

For Deb installs, installing a newer Deb over the old package is the normal upgrade and does not require a purge first. For Snap, refresh updates in place.

Why is Check for Updates missing?

Some Linux builds do not expose the same in-app control documented for Windows. Use the packaging channel instead.

Should I mix Snap refresh and Deb upgrades?

No. Pick one install method and stay on it to avoid duplicate binaries and confusing version checks.

Will apt upgrade ever update Deb WPS?

Only if a configured repository publishes wps-office. The official Deb download path does not create that repository for you.

Is terminal update safer than downloading again in a browser?

You still need a trustworthy Deb file. The terminal part is the install/upgrade command; the source should remain the official Linux page.