Every new Ubuntu LTS brings the same question from people who live in documents and spreadsheets. Is LibreOffice enough this time, or does the team still need something that opens a client’s DOCX without shifting the layout by half a page? Ubuntu 26.04 LTS, codenamed Resolute Raccoon, shipped on April 23, 2026 with LibreOffice 25.8. That is a solid suite. Even so, plenty of freelancers, accountants and office staff want the Microsoft-style ribbon, tabbed documents and the PDF tools that WPS Office offers.

The install itself looks trivial. Download a file, run one command, done. In practice, though, Ubuntu 26.04 differs from what most older tutorials assume. The desktop is now Wayland only. The default terminal is Ptyxis. APT is at version 3.2. The kernel is 7.0. Some of those changes touch how a third-party Qt application behaves, and old guides don’t mention any of it.

This guide walks through the complete process the way it would be done on a real workstation. It covers the official Deb package, the Snap alternative, verification, fonts, Wayland quirks, updates, removal, and a troubleshooting section built from the errors people actually hit. It also covers a few sysadmin habits that matter when you roll this out to more than one machine. If you manage Ubuntu desktops for a small office, or you just set up your own laptop, you should be able to follow it start to finish without guessing.

What Changed in Ubuntu 26.04 That Affects WPS Office

Some background on the platform first, because it explains several decisions later on.

Ubuntu 26.04 ships Linux kernel 7.0 and GNOME 50. X11 sessions have been removed from GDM, so the desktop runs on Wayland only. The desktop system requirements went up as well, to 6 GB of RAM and 25 GB of free storage for a comfortable experience. Ubuntu 26.04.1 LTS became available on September 29, 2026, which is the point where many cautious admins begin upgrading production desktops.

For WPS Office, three of these changes matter.

• Wayland only: WPS is a Qt application, and it may run through XWayland rather than as a native Wayland client. Most of the time that works fine. Occasionally you will see blurry text on fractional scaling or odd popup positions. There is a fix for that later on.
• APT 3.2: It keeps transaction history with rollback support. That is handy when you install a large local package and want a clean way back.
• Newer libraries: Ubuntu 26.04 carries newer versions of core libraries. Proprietary packages built against older library versions can complain about missing dependencies. The troubleshooting section covers that.

Ubuntu 26.04 is supported until April 2031. That is a long runway, so it is worth choosing an install method you can maintain for years and not just one that works today.

Choosing the Right Install Method

There are two realistic ways to get WPS Office on Ubuntu 26.04 LTS. Each has trade-offs, and picking the wrong one is the source of half the support questions.

The official WPS guidance is to download the current package from the WPS Linux page and install that local file with your package manager. The Snap route exists too, using sudo snap install wps-office. Before using Snap, check the publisher shown by snap info wps-office. Treat the publisher name and the confinement status as things to verify, not assume.

For most people, the Deb package is the better choice. It behaves like a normal application, the file picker sees your whole home directory, and troubleshooting is simpler because there is no sandbox in the way. Snap is worth considering on a locked-down shared machine, where confinement is a feature.

Prerequisites and Pre-Flight Checks

A few minutes of preparation saves a lot of debugging later. Start by confirming what you are running.

lsb_release -a
uname -m

You should see Ubuntu 26.04 and x86_64 on a typical PC. If uname -m returns aarch64, you are on ARM64. Ubuntu 26.04 now offers an official ARM64 desktop ISO, so this is no longer exotic. Make sure you download the package that matches your architecture. Installing the wrong one is a classic time-waster.

Next, bring the system up to date.

sudo apt update
sudo apt full-upgrade -y

A fully patched base avoids dependency conflicts where APT wants to upgrade a library mid-install. If the upgrade pulls in a new kernel, reboot before continuing. It is boring advice, but it prevents the kind of mismatch where a graphics stack changes under a running session.

Check free disk space too, since Office suites are not small.

df -h /

Keep at least a few gigabytes free. The package itself is a few hundred megabytes, but the unpacked size, caches and user data grow with use.

Finally, make sure the helper tools you will need are present.

sudo apt install -y wget curl ca-certificates fontconfig

Method 1: Install the Official Deb Package

This is the recommended route.

Step 1: Download the Deb file

Open the official WPS Office for Linux page in your browser and pick the Deb package for Ubuntu, Debian, Linux Mint and similar systems. Save it to ~/Downloads. Use the official page every time. Random mirrors and repackaged builds are exactly how a document editor ends up with something unwanted bundled in.

If you prefer the terminal or work over SSH on a remote desktop, copy the direct link from the official page and download it like this:

cd ~/Downloads
wget -O wps-office.deb "PASTE_THE_OFFICIAL_LINK_HERE"

Direct download URLs change between releases, which is why a hard-coded link in a tutorial goes stale quickly. Always copy the current one.

Step 2: Verify the file

Check that the file is a real Debian package and not an HTML error page saved with a .deb name. It happens more than you would think, especially behind captive portals and proxies.

file wps-office.deb
dpkg-deb --info wps-office.deb | head -n 20
sha256sum wps-office.deb

You should see “Debian binary package” in the first output. The info command shows the package name, version, architecture and dependency list. Reading the Depends: line is a useful habit. It tells you in advance what APT will want to pull in.

If the vendor publishes a checksum, compare it to the sha256sum result. If none is published, at least confirm you downloaded over HTTPS from the official domain.

Step 3: Install with APT

Use APT, not raw dpkg, for the install. APT resolves dependencies automatically, and the path must be explicit so it treats the argument as a local file.

cd ~/Downloads
sudo apt install ./wps-office.deb

The ./ matters. Without it, APT searches the repositories for a package called wps-office.deb and fails. WPS’s own instructions use this same pattern.

The older method still works if you prefer it:

sudo dpkg -i ./wps-office.deb
sudo apt-get install -f

The second command repairs missing dependencies after dpkg complains. Why prefer the APT one-liner? It does everything in a single transaction, which makes the history cleaner and any rollback simpler. On APT 3.2 the transaction history feature is a real advantage here.

Step 4: Launch and check

Open the Activities overview and search for WPS Writer, or start it from a terminal:

wps

Running it from a terminal for the first launch is worth the extra ten seconds. Any missing library or plugin error prints right there, and that message is what you will search for if something fails. The WPS docs recommend launching Writer once and opening a DOCX or XLSX file to confirm everything works. That is the right test. A splash screen appearing proves very little. Opening a real document with tables and images proves a lot.

The other entry points are wpp for Presentation, et for Spreadsheets and wpspdf for the PDF tool. These are the usual command names in the Linux package, but confirm with dpkg -L wps-office | grep /usr/bin.

Method 2: Install WPS Office with Snap

If you would rather use Snap, the command is short.

sudo snap install wps-office

Check what you are getting before you trust it:

snap info wps-office

Look at the publisher, the channel and the confinement. Then handle the sandbox. If you keep documents on a USB drive or external disk, connect the removable-media interface manually:

sudo snap connect wps-office:removable-media

That interface connection is documented in community answers about the Snap build. Without it, the file picker will show an empty or read-only view of your external storage, and people often assume the app is broken.

Snap has one more practical quirk. Confined apps read fonts from a limited set of locations, so fixing missing fonts works differently than with the Deb. If you are going to be tuning fonts a lot, the Deb package will cause you less grief.

Snap updates happen in the background through snapd’s refresh schedule. You can inspect it with snap refresh --time. On a workstation where you would rather choose when things change, hold refreshes for a while with sudo snap refresh --hold=72h wps-office.

Fixing Missing Fonts

The first time you open a document from a Windows user, a dialog may warn about missing fonts. It looks alarming and usually is not. Some formula symbols and special characters fail to display because WPS expects Windows-style fonts such as Symbol and Wingdings that Ubuntu does not ship by default.

The sensible approach, echoed by WPS’s own guidance, is to read the exact font names in the dialog first and then install only those. Do not blindly copy a giant font bundle from the internet.

Check what you already have:

fc-list | grep -i -E "symbol|wingdings|arial|times|calibri" | head
fc-match "Arial"
fc-match "Calibri"

fc-match shows what fontconfig will substitute. If “Calibri” resolves to something with different metrics, line breaks will move. Metric-compatible substitutes exist for the most common Microsoft fonts. Carlito replaces Calibri, Caladea replaces Cambria, and Liberation covers Arial, Times New Roman and Courier New. All three are available in the Ubuntu repositories.

sudo apt install -y fonts-crosextra-carlito fonts-crosextra-caladea fonts-liberation2

For a user-only install of extra fonts, no root needed:

mkdir -p ~/.local/share/fonts/wps-extra
cp /path/to/extracted/fonts/*.ttf ~/.local/share/fonts/wps-extra/
fc-cache -f -v

System-wide installs go under /usr/share/fonts/ followed by sudo fc-cache -f -v. Then restart WPS fully. Closing the window is not enough if a background process is still running, so use pkill -f wps when in doubt.

A licensing note. Symbol and Wingdings substitutes found in community repositories vary in license. If you deploy this on company machines, confirm you are allowed to distribute whatever you install. WPS’s guidance says the same: install fonts you are entitled to use.

Wayland, Scaling and Display Quirks

Since GNOME 50 removed X11 sessions from GDM, every Ubuntu 26.04 desktop session is Wayland. Most Qt applications cope through XWayland or a native plugin. WPS is usually fine, but a few symptoms are worth knowing.

Blurry text on a HiDPI or fractionally scaled display. XWayland applications get scaled up as bitmaps in some setups. Try running WPS with a specific Qt platform variable:

QT_QPA_PLATFORM=xcb wps

Or, if your install has a Wayland Qt plugin available:

QT_QPA_PLATFORM=wayland wps

Test both and keep whichever renders better. To make it permanent for your user, copy the desktop launcher and edit the Exec= line:

mkdir -p ~/.local/share/applications
cp /usr/share/applications/wps-office-wps.desktop ~/.local/share/applications/
nano ~/.local/share/applications/wps-office-wps.desktop

Change the Exec= line to begin with env QT_QPA_PLATFORM=xcb. Save, then run update-desktop-database ~/.local/share/applications. Copying to the user directory means package upgrades will not overwrite your change, which is the entire point of doing it that way.

Popups and menus appearing in the wrong place. This tends to be a Wayland-versus-XWayland mismatch. The same platform variable usually resolves it.

Clipboard or drag and drop misbehaving between apps. Update first. Then check that xdg-desktop-portal-gnome is installed and running, since portals mediate a lot of Wayland desktop behavior.

systemctl --user status xdg-desktop-portal.service

If you see graphical glitches specifically after a kernel or Mesa update, note that Ubuntu 26.04 ships Mesa 26.0. Collect the output of glxinfo -B before filing a bug. It saves a lot of back and forth.

Making WPS the Default and Setting File Associations

Installing an office suite does not automatically make it the handler for Word files. Ubuntu will still open DOCX in LibreOffice unless told otherwise.

Set associations from the terminal:

xdg-mime default wps-office-wps.desktop application/vnd.openxmlformats-officedocument.wordprocessingml.document
xdg-mime default wps-office-et.desktop application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
xdg-mime default wps-office-wpp.desktop application/vnd.openxmlformats-officedocument.presentationml.presentation

Confirm what is set:

xdg-mime query default application/vnd.openxmlformats-officedocument.wordprocessingml.document

Desktop file names can differ between package versions, so list them first with ls /usr/share/applications | grep -i wps. Getting a name wrong makes xdg-mime silently accept a nonexistent handler, which produces the confusing result of files that open in nothing at all.

Performance Tuning

WPS Office is lighter than most of its competitors, but a few adjustments help on modest hardware or crowded machines.

RAM. Ubuntu 26.04 raised its desktop recommendation to 6 GB. On an 8 GB laptop running a browser with forty tabs, WPS with a large spreadsheet can push the system into swap. Check with:

free -h
swapon --show

If the machine swaps heavily, consider zram, which compresses memory instead of writing to disk. It makes a noticeable difference on laptops with slow storage.

sudo apt install -y systemd-zram-generator

CPU. Watch behavior with top or the new default Resources monitor, which groups processes by app and can also track GPU usage. If a runaway wps process keeps a core pinned after you close a document, kill and relaunch it. Then look at whether a plugin or cloud sync feature is the trigger.

Disk I/O. Autosave and backup features write frequently. On spinning disks or network home directories this can hurt. Check with iostat -x 2 from the sysstat package, or iotop. If home directories live on NFS, keep the WPS backup and cache folders local where you can.

Network. Cloud features, update checks and online templates create outbound traffic. On a metered link or a tight office firewall, that is worth knowing about. Watch it with:

sudo ss -tpn | grep -i wps

This lists live connections belonging to WPS processes, so you can decide whether to allow or block them.

Security Considerations

A proprietary office suite deserves the same skepticism as any other third-party software, and Ubuntu 26.04 gives you decent tools to apply it.

Source and integrity. Get the package only from the official WPS Linux page. Inspect what the package will do before installing.

dpkg-deb --contents wps-office.deb | head -n 50
dpkg-deb -I wps-office.deb
dpkg-deb -e wps-office.deb /tmp/wps-control && ls /tmp/wps-control

The control directory can contain postinst and similar scripts, which run as root during installation. Reading them takes two minutes and is standard practice for any package that does not come from a signed repository.

Repositories and updates. A locally installed Deb will not be updated by apt upgrade unless it added a repository. Check:

grep -ril wps /etc/apt/sources.list /etc/apt/sources.list.d/ 2>/dev/null
apt-cache policy wps-office

If nothing shows, you are responsible for checking for new versions. Put a reminder in your monthly maintenance routine, because an office suite parses untrusted files from email all day, and old versions are a real exposure.

Firewall. WPS is a client application, so it needs no inbound ports. Keep the default deny policy on.

sudo ufw status verbose
sudo ufw default deny incoming
sudo ufw enable

Permissions. Never run WPS with sudo. It creates root-owned files in your home directory that later break the app for your normal user. If you already did, fix ownership with sudo chown -R "$USER":"$USER" ~/.config/Kingsoft ~/.local/share/Kingsoft.

Macros and untrusted documents. Disable macros by default and open unknown attachments in Protected View or a throwaway user account. Ubuntu 26.04 also improves application permission controls, so favor confined installs on shared machines.

Sandboxing the Deb build. If you want extra isolation without Snap, Firejail or Bubblewrap can wrap wps. Test carefully, since aggressive profiles break file pickers and fonts.

Updating, Downgrading and Removing WPS Office

Updating a manually installed Deb means downloading the new file and running the same install command over the old one.

sudo apt install ./wps-office_NEWVERSION_amd64.deb

APT handles the upgrade in place. Your settings live in your home directory, so they survive.

To see the install history, and roll back if the new version misbehaves, use APT’s history feature introduced in the 3.x series:

apt history-list

Check the exact subcommands with apt help, as syntax may differ slightly by release. Keeping the previous .deb file around is a simpler and more reliable fallback. Reinstalling an older Deb requires --allow-downgrades:

sudo apt install --allow-downgrades ./wps-office_OLDVERSION_amd64.deb

To remove it:

sudo apt remove wps-office
sudo apt autoremove

To purge system-level configuration as well:

sudo apt purge wps-office

User data stays in your home directory. Clean it out only if you are sure:

rm -rf ~/.config/Kingsoft ~/.local/share/Kingsoft

For Snap, use sudo snap remove wps-office. Add --purge if you want to skip the automatic data snapshot.

Troubleshooting Common Errors

Here are the failures that come up most often, with the cause and the fix.

“dependency problems – leaving unconfigured” after dpkg

This happens when you use dpkg -i directly and a dependency is missing. Run:

sudo apt-get install -f

That pulls in whatever was missing and finishes the configuration. Next time, use apt install ./file.deb from the start.

“Unable to locate package wps-office.deb”

You forgot the ./ or you are in the wrong directory. Run pwd and ls *.deb. Then use sudo apt install ./wps-office.deb, or the full path.

libcrypto.so.1.1 or libssl.so.1.1 not found

Some builds link against OpenSSL 1.1, which modern Ubuntu releases no longer ship by default. WPS’s guidance is to install the matching libssl1.1 package for your architecture, and only if that exact error appears. First confirm the missing library:

ldd $(which wps) 2>/dev/null | grep "not found"
ldd /opt/kingsoft/wps-office/office6/wps | grep "not found"

The second path is the usual install location, but check with dpkg -L wps-office | grep office6. Match the architecture (amd64 or arm64) with uname -m. Since 1.1 is long out of upstream support, treat this as a stopgap. Prefer a newer WPS build if one is available, and avoid installing old crypto libraries on machines that handle sensitive data.

Missing Libtiff or other shared library warnings

The pattern is the same. Identify the library, find the package that provides it, and install only that.

apt-file update
apt-file search libtiff.so.5

Install apt-file first with sudo apt install apt-file. Guessing package names and installing several at random tends to make things worse.

WPS will not start and prints nothing

Launch it from a terminal and look at the output. Then check for stale lock files and processes:

pkill -f wps
ls ~/.config/Kingsoft/
mv ~/.config/Kingsoft ~/.config/Kingsoft.bak
wps

Moving the config directory aside is safer than deleting it. If WPS starts with a clean profile, the old configuration was corrupt, and you can restore individual files from the backup.

Cannot open files on a USB drive (Snap)

That is the confinement issue described earlier. Connect the interface with sudo snap connect wps-office:removable-media.

Interface text is tiny, huge or blurry

Test the QT_QPA_PLATFORM variable as described in the Wayland section. You can also try a scaling factor for Qt:

QT_SCALE_FACTOR=1.25 wps

Documents look different from what the sender saw

That is nearly always fonts. Compare with fc-match, install the metric-compatible families listed earlier, and rebuild the cache with fc-cache -f -v.

Installation stalls at “Waiting for cache lock”

Another package process is running, often an automatic update. Wait a couple of minutes. Check with ps aux | grep -E "apt|dpkg|unattended". Do not delete lock files unless no process is holding them, since that can corrupt the package database.