Package Base Details: wps-office

Git Clone URL: https://aur.archlinux.org/wps-office.git (read-only, click to copy)
Submitter: felixonmars
Maintainer: Universebenzene
Last Packager: Universebenzene
Votes: 489
Popularity: 2.91
First Submitted: 2014-08-17 11:57 (UTC)
Last Updated: 2024-02-22 03:20 (UTC)

Pinned Comments

Universebenzene commented on 2023-01-20 10:34 (UTC)

Anyone who meet the problem of launching wpspdf, please install the optional dependency libtiff5

Universebenzene commented on 2020-10-22 02:25 (UTC)

If you have the "ERROR: One or more files failed the validity check!" problem, try cleaning your AUR cache first, and try again.

Universebenzene commented on 2020-01-10 04:48 (UTC) (edited on 2020-06-09 15:38 (UTC) by Universebenzene)

[ATTENTION] The new international version (11.1.0.9080) removed zh_CN support, login, and some other functions. If you still want full functions, or you want aarch64 support, you may need the Chinese version from https://linux.wps.cn here: https://aur.archlinux.org/pkgbase/wps-office-cn

Universebenzene commented on 2019-10-26 05:46 (UTC) (edited on 2019-10-26 07:10 (UTC) by Universebenzene)

I split the /usr/share/mime/packages/wps-office-*.xml files to the wps-office-mime package to avoid mime issues. If you still want the mime files provided by wps-office itself, you can install the new mime package.

Universebenzene commented on 2019-07-05 17:08 (UTC)

There is no official 32-bit package for version 11.1.0.8722, so I drop the support for i686 arch. For archlinux32 users you can create another wps-office package for 32-bit system yourself.

Universebenzene commented on 2019-04-16 13:34 (UTC)

When you shut down wps-office, the wpsoffice process may still exist. You can do sudo chmod -x /usr/lib/office6/wpsoffice to fix it. But this might bring you problem with signing in.

oowl commented on 2017-11-29 14:16 (UTC)

About the software issues, you can go to the official feedback problem. I'm just a packager, I can not solve the software problem.

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 69 Next › Last »

flavio92ux commented on 2021-08-12 12:59 (UTC)

Thanks, @CalzzOne. The second solution worked for me. Thanks very much a lot!

flavio92ux commented on 2021-08-12 12:59 (UTC)

Thanks, @CalzzOne. The second solution worked for me. Thanks very much a lot!

curlywei commented on 2021-08-12 10:00 (UTC) (edited on 2021-08-12 10:23 (UTC) by curlywei)

I can't display input block with fcitx5-chewing or fcitx5-mozc, but previous version is fine (English is no problem no matter what versions) Does anyone encounter this problem?

Refer here gif animation: https://imgur.com/eD4pO5p.mp4

Starting from 0:33, you can look problem when input Chinese.

CalzzOne commented on 2021-08-12 05:36 (UTC) (edited on 2021-08-12 05:37 (UTC) by CalzzOne)

@matt17br, @tornado99, @flavio92ux : I "fixed" the dark skin issue by modifying the theme files. In /usr/lib/office6/skins/ there are a bunch of folders, but WPS is only aware of 2019dark and 2019white. 2018white_dark palys nice with dark KDE themes. You have 2 options:

  1. rename 2018white_dark to 2019dark
  2. edit 2019dark/et.kuip file itelf. This file contains a bunch of <style>...</style> tags. Replace or edit the tag named "EtEditBarWidget" with the following data:

<style class="EtEditBarWidget"><linearGradient name="background" spread="pad" start="0,0" end="0,1"><color position="0" value="#e8e8e8"/></linearGradient><color name="background" value="#ffffff"/><color name="text" value="#000000"/></style>.

The background and 'text` were missing. Now that I know how theme files work, I am going to explore this and customize wps even further.

matt17br commented on 2021-08-10 23:34 (UTC)

"You can edit the actual files in /usr/bin/wps wpp et to include these 2 lines: (gOpt= is already there)

gOpt="-style=gtk+"

export GTK2_RC_FILES=/usr/share/themes/Breeze/gtk-2.0/gtkrc"

@tornado99 this fix used to work before this new version came out, but unfortunately I have to report that it doesn't seem to fix anything for me anymore. I was able to fix the pixelation editing the desktop files, but the weird theme artifacts are still a concern using a dark theme by default.

ppc52776 commented on 2021-08-09 04:00 (UTC)

@tornado99, Thanks!! Putting the env QT_SCREEN_SCALE_FACTORS=1 to .desktop file is a good solution.

JoveYu commented on 2021-08-09 03:43 (UTC)

any one meet this problem, you can delete file /usr/lib/office6/libstdc++.so*

libGL error: MESA-LOADER: failed to open radeonsi: /usr/lib/office6/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib/dri/radeonsi_dri.so) (search paths /usr/lib/dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open radeonsi: /usr/lib/office6/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib/dri/radeonsi_dri.so) (search paths /usr/lib/dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open swrast: /usr/lib/office6/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib/dri/swrast_dri.so) (search paths /usr/lib/dri)
libGL error: failed to load driver: swrast

tornado99 commented on 2021-08-06 23:08 (UTC) (edited on 2021-08-06 23:08 (UTC) by tornado99)

You can edit the actual files in /usr/bin/wps wpp et to include these 2 lines: (gOpt= is already there)

gOpt="-style=gtk+"

export GTK2_RC_FILES=/usr/share/themes/Breeze/gtk-2.0/gtkrc

flavio92ux commented on 2021-08-06 12:54 (UTC) (edited on 2021-08-06 19:00 (UTC) by flavio92ux)

How to fix wps spreadsheet breeze dark theme issue (KDE Plasma)? P.S. the command from Arch wiki (env GTK2_RC_FILES=/usr/share/themes/Breeze/gtk-2.0/gtkrc et -style gtk+) dont work for me.

The only temporary solution was to run it as root (because my root user have a light theme) but should have better solution.

tornado99 commented on 2021-08-06 09:58 (UTC)

You have to change the [Desktop Entry] in usr/share/applications/wps-office-wps.desktop and the other 3 wps files to: Exec=env QT_SCREEN_SCALE_FACTORS=1... That fixes the pixellation but it doesn't turn back on RGB antialiasing for low dpi displays.