The guide explains how Fedora 36 users can install WPS Office by downloading the official 64‑bit RPM from Kingsoft, first ensuring all required Xorg libraries are present so that dnf can resolve dependencies without stalling. It then shows how to run the local installation with sudo dnf install ./wps-office‑…rpm and, if the app does not appear in the menu, how to create a simple desktop shortcut manually. The article offers alternative sandboxed options such as Flatpak or Snap for those who prefer isolated packages and lists common hiccups—crashes from missing libXdamage, font shortages, and file‑open errors tied to outdated RPMs—along with quick fixes like reinstalling libraries or updating the package. Overall, it provides a dependency‑aware, straightforward path to get WPS Office up and running on Fedora 36 without chasing obscure mirrors or dealing with broken packages.

Installing WPS Office on Fedora 36

Fedora 36 users who need a free office suite that plays nicely with .docx files will find WPS Office to be a solid pick. The following steps show how to get it running without chasing down obscure dependencies or wrestling with broken package mirrors.

Grab the official RPM from Kingsoft

Head over to the WPS Office download page and pick “Linux‑RPM (64‑bit)”. The file will look something like wps-office-11.1.0.11291.x86_64.rpm.
Why this matters: the .rpm is built for Red Hat‑based systems, so Fedora can install it natively with no need to convert or repackage.

Install required libraries first

Some of WPS’s shared objects rely on older Xorg bits that aren’t in Fedora’s default repo. Running this before the main install saves a headache later:

sudo dnf install libXcomposite libXdamage libXrandr libXtst libXrender libXi

If you see “No matches found” for any package, enable EPEL or RPM‑Fusion; those repos hold the missing bits.

Fire up the installer

With dependencies in place, install the downloaded file:

sudo dnf install ./wps-office-11.1.0.11291.x86_64.rpm

The ./ tells dnf to look locally; this avoids hitting the network for a stale copy. Watch the progress bar—if it stalls on “Resolving Dependencies,” double‑check you’ve got all the libs from the previous step.

Check the desktop entry and launch

After installation, WPS should appear in your application menu. If not, create a simple shortcut:

cat <<EOF > ~/.local/share/applications/wps-office.desktop
[Desktop Entry]
Name=WPS Office
Exec=/opt/kingsoft/WPSOffice/wps
Icon=/opt/kingsoft/WPSOffice/res/icons/wps.png
Terminal=false
Type=Application
Categories=Office;
EOF

Run update-desktop-database ~/.local/share/applications to register it. Now you can launch WPS from your menu like any other app.

Alternative: Flatpak or Snap

If the RPM route feels brittle, use a sandboxed package:

flatpak install flathub org.wps.WPSOffice
# or
sudo snap install wps-office --classic

These versions include all dependencies in a controlled environment and sidestep Fedora’s version drift.

Common hiccups and quick fixes

• “WPS crashes when opening images” – I’ve seen this after a bad GPU driver update that removed libXdamage. Re‑install the lib with dnf, then restart WPS.
• Missing fonts – The bundled font list is minimal. Install sudo dnf install dejavu-sans-fonts (or your preferred set) for better rendering in documents.
• “Could not open file” on a .docx – Ensure you’re running the latest RPM; older releases sometimes miss the libxml2 update required to parse modern Word XML.