Package Details: wps-office 11.1.0.8392-1

Git Clone URL: https://aur.archlinux.org/wps-office.git (read-only)
Package Base: wps-office
Description: Kingsoft Office (WPS Office) is an office productivity suite
Upstream URL: http://wps-community.org/
Licenses: custom
Conflicts: kingsoft-office
Submitter: felixonmars
Maintainer: Universebenzene
Last Packager: Universebenzene
Votes: 403
Popularity: 13.216640
First Submitted: 2014-08-17 11:57
Last Updated: 2019-04-16 13:33

Sources (4)

Pinned Comments

Universebenzene commented on 2019-04-16 13:34

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.

attenuation commented on 2017-11-29 14:16

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

1 2 3 4 5 6 ... Next › Last »

Universebenzene commented on 2019-04-16 13:34

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.

echizenryoma commented on 2019-04-16 06:51

Please use DEB to package, for RPM version cannot sign in.

Universebenzene commented on 2019-04-11 02:58

@keybreak I didn't do anything to the desktop entry file. That should be WPS's own issue.

keybreak commented on 2019-04-10 16:51

@Universebenzene One more thing i've noticed that WPS programs icons are kinda blurry at least with Deepin DE, .desktop files states:

Icon=/usr/share/icons/hicolor/48x48/apps/wps-office-wpsmain.png

And even though technically there are 256x256 icons available - still the actual files are kinda blurry... Is this WPS itself or package issue?

keybreak commented on 2019-04-09 15:36

@Universebenzene Also, i think it's a good idea to include https://aur.archlinux.org/packages/ttf-wps-fonts/ fonts in this package by default, as WPS 11 throws annoying exception on launch now anyway, so it's almost not optional now :)

But...It's about M$ licensing bs, right?

keybreak commented on 2019-04-09 15:15

@Universebenzene sure, but you better try yourself because in my experience if you'll fix one there will be another so it would be faster for maintainer to catch -> fix -> try again)

Here's first one, hard to say where exactly it fails, but:

==> Starting package()...
install: cannot stat '/run/media/x133/STORAGE': No such file or directory
install: cannot stat '1/WPS': No such file or directory
install: cannot stat 'Office/Build/src/etc/xdg/menus/applications-merged/*': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

I ran it from directory:

/run/media/x133/STORAGE 1/WPS Office/Build

Universebenzene commented on 2019-04-09 15:03

@keybreak Could you please show me your error output? That might help me to fix it.

keybreak commented on 2019-04-09 14:32

@Universebenzene not sure what exactly, but if you try to build it from folder (which contains spaces in it's path like "/One Two/Three") with makepkg -s it will fail to build...

This usually happens because not all commands in script, which contains path are wrapped in quotes, for example something like cd "$mypathwithspaces" if not quoted will fail obviously)

Not big deal since you can build successfully within folder path without spaces, but just would be good tone to fix it :)

Universebenzene commented on 2019-04-09 14:19

@keybreak You mean the desktop-directories and templates should be in the package?

keybreak commented on 2019-04-09 11:49

Please fix all build scripts paths, to contain quotes around, so they can build in directories which contain spaces.

That's rare use case, but good to have for someone who build stuff in custom directories like me)