How to Fix WPS Office Not Opening on Ubuntu

To fix WPS Office not opening on Ubuntu, start by launching it from a terminal so you can see the real error, then triage the failure type before reinstalling. “Not opening” is not one bug: the dock icon may flash and vanish, Writer may open for a few seconds and close, the suite may start only with sudo, or documents on a USB/second disk may fail while home-folder files work.

Shortest path: confirm the package is installed → launch from terminal → match the symptom to a branch below → apply the matching non-destructive fix → only then reinstall from the official Deb or repair Snap. Success means a normal user session opens Writer without root, and a sample document stays open.

If the dock icon flashes then disappears → capture terminal output first.
If it opens briefly then closes → check Wayland/Qt warnings and package integrity.
If it only runs as root → fix permissions/libraries, do not keep using sudo.
If only external disks fail → treat it as Snap confinement or permissions, not a “won’t start” bug.

Confirm What Is Installed and How You Launch It

dpkg -l wps-office 2>/dev/null
snap list 2>/dev/null | grep -i wps
command -v wps
command -v wps-office
ls /usr/share/applications/*wps* 2>/dev/null

An ii Deb row, a Snap list entry, or both tell you which repair path is valid. Launcher names such as wps, et, and wpp are build-dependent—confirm with command -v or the desktop files you actually have. Do not diagnose on a headless SSH session; WPS Office is desktop GUI software.

Also note how you installed it. A Deb from the official Linux page, a Snap from Ubuntu Software, and an old community wget Deb are different repair stories. If both Deb and Snap traces exist, remove or ignore the unused channel after you identify which launcher the dock actually calls—duplicate installs produce “I fixed it but the icon still fails” confusion.

Capture the Real Error From a Terminal

Ask Ubuntu reports often say “no error window,” yet the terminal prints a segfault, a missing library, a Qt/Wayland warning, or nothing useful until you launch the exact binary. From a graphical session:

wps
# If that command is missing, try a menu-discovered name, or:
snap run wps-office

Leave the terminal open. Copy the full output. That string decides whether you chase a style/theme crash, a missing .so after an Ubuntu upgrade, a Snap permission issue, or a broken package state.

Branch A: Icon Appears Then Vanishes (Silent Quit / Segfault)

Threads titled “WPS doesn’t start” and “Writer not loading” describe a dock icon that lasts a few seconds, then vanishes, sometimes with Segmentation fault (core dumped) in /usr/bin/wps. Community workarounds that helped some users include launching with a GTK Qt style hint:

wps -style gtk+
# or, depending on the report:
wps -style gtk

If that keeps Writer open, you can temporarily edit the matching .desktop Exec line the same way—only after you confirm the desktop file path on your system:

grep -R "Exec=" /usr/share/applications/*wps* 2>/dev/null

Change only a confirmed Exec line for testing. Prefer a user copy under ~/.local/share/applications/ when possible so a package update does not silently fight your edit. If the style flag does nothing, move on—do not stack unrelated Wine or Flatpak tips.

On Plasma/Kubuntu desktops, the same silent-quit pattern sometimes tracks Qt theme conflicts. Installing and adjusting Qt4 configuration tools was a historical workaround on older Ubuntu releases; on current releases, prefer proving the -style flag in a terminal first, then decide whether a desktop-file edit is worth keeping. If the segfault disappears only with the flag, keep that minimal change and stop layering more theme experiments.

Branch B: Opens for a Few Seconds, Then Closes

Some users see a brief window, then an exit with terminal messages such as Qt not supporting Wayland, locale fallbacks, or accessibility registration warnings. Those messages are clues, not always the single root cause. Non-destructive checks:

sudo dpkg --configure -a
sudo apt --fix-broken install
dpkg -l wps-office

Expected result: the package is fully configured (ii). If you are on a Wayland session and the terminal explicitly complains about Wayland/Qt, test once on an Xorg session from the login screen if your Ubuntu flavor offers it. Treat that as a diagnostic branch, not a universal requirement to abandon Wayland forever.

Branch C: Starts Only With sudo (Permission / Library Traps)

Ubuntu 22.04-era reports show WPS refusing to start for a normal user after upgrades, while sudo wps works. That is unsafe as a daily habit. Two community clusters appear:

• Missing OpenSSL 1.1 libraries after moving to a release that no longer ships them by default—terminal may mention libcrypto.so.1.1.

• Permission problems on bundled libraries under the WPS install tree (paths vary by build; often under an office6 directory).

If the terminal names libcrypto.so.1.1 or libssl.so.1.1, this is a version-era dependency gap for that WPS build on that Ubuntu release—not a reason to invent a PPA. Prefer downloading a current official Deb from wps.com/office/linux and installing the local file with APT. Only install a specifically named compatibility library when the error prints that name and you understand it is a stopgap for that old build.

ldd /opt/kingsoft/wps-office/office6/wps 2>/dev/null | grep -i "not found"
# Path is build-dependent; locate binaries first:
dpkg -L wps-office | grep -E "office6|bin" | head

If ldd reports missing libraries, fix those names deliberately. If files exist but only root can read them, correct ownership/permissions carefully—do not chmod 777 your home directory.

Another “only as root” pattern is a corrupted user config. After backups, some users remove a Kingsoft config folder under ~/.config/ so the app regenerates settings. That deletes local WPS settings for that user, not your Documents files—still back up first.

ls -ld ~/.config/Kingsoft ~/.config/*wps* 2>/dev/null

Branch D: “Not Opening” Is Really a File-Access Failure

If Writer starts for home-folder documents but fails on USB drives or a second HDD with permission messages, you are not facing a blank launch bug. For Snap installs:

snap connections wps-office
sudo snap connect wps-office:removable-media

Use the exact snap name from snap list. If connect is impossible or still fails, remove the Snap and install the official Deb instead—common advice when confinement blocks dual-boot or secondary disks.

Repair Package State Before a Full Reinstall

sudo dpkg --configure -a
sudo apt --fix-broken install
dpkg -l wps-office

If the Deb is half-installed, finish configuration before deleting anything. A package stuck in iF or similar half-configured states can look exactly like “WPS won’t open” because the desktop entries exist while binaries are incomplete. Read APT’s proposed actions carefully—if it offers to remove wps-office to “fix” dependencies, abort unless you intend to uninstall, then download a current official Deb instead of accepting a destructive cleanup.

For Snap:

sudo snap refresh wps-office
snap run wps-office

Reinstall Last (Official Channel)

Only after triage, reinstall. For Deb:

cd ~/Downloads
# Download current Deb Package from the official WPS Linux page first
sudo apt install ./wps-office_VERSION_amd64.deb

Use the exact filename you downloaded. Do not paste multi-year-old community wget URLs as the default. For Snap:

sudo snap remove wps-office
sudo snap install wps-office

Avoid running Deb and Snap side by side while testing launches—duplicate launchers hide which binary still fails.

Slow to Open Is Not the Same as Not Opening

Some Deb users report multi-second delays that feel like a hang, especially while WPS substitutes missing fonts or reaches the network. Snap users sometimes see faster perceived startup because of different confinement and network defaults. If Writer eventually opens, treat performance tuning separately from crash triage: close extra documents, test offline once, and only then consider channel differences. Do not reinstall in a loop for a slow-but-successful launch.

Verify Success

1. Launch Writer as your normal user (no sudo).

2. Open a sample .docx from Documents and leave it open for a minute.

3. If you need USB/second-disk files, re-test those paths.

4. Confirm Spreadsheets and Presentation also start if you use them.

Keep Working Smoothly in WPS Office

Once Ubuntu can launch the suite again, stay on the official WPS Office build for Writer, Spreadsheet, Presentation, and PDF in one place. That keeps DOCX, XLSX, PPTX, and PDF workflows consistent—without switching apps every time a file fails to open.

Fix and Reinstall WPS Office on Ubuntu Free

Free Download

FAQ

Why is there no error dialog?

Many launch failures exit before a GUI error appears. Always start from a terminal once.

Is sudo a valid fix?

No. It is only a diagnostic clue that permissions or libraries differ for the normal user.

Does a font warning mean WPS is not opening?

No. Formula-symbol font dialogs are a different issue; the suite can still be running.

Should I add a PPA to fix startup?

No. Prefer the official Deb/Rpm page or Snap tooling you already use.

What if the terminal prints nothing and still exits?

Recheck package status, try the other channel’s launcher if both exist, and inspect dmesg or journalctl --user-unit only after the simple package checks fail.

Does “unknown media /ALL” during install cause not opening?

Some installs print odd media messages yet still unpack. Always verify with a terminal launch afterward instead of assuming the message alone explains a later silent quit.

Free Office Download

• Use Word, Excel, and PPT for FREE, No Ads.

• Edit PDF files with the powerful PDF toolkit.

• Microsoft-like interface. Easy to learn. 100% Compatibility.

• Boost your productivity with WPS's abundant free Word, Excel, PPT, and CV templates.

Free Download

100% secure