WPS doesn't launch in all-in-one mode

[fenris]

I've installed the WPS then I tried to change it to make it available to open all-in-one. Then after restarting the WPS ... it doesn't run anymore.

How to revert back to WPS modules instead of all-in-one?

[gasinvein]

Try removing lines

wpsoffice\Application%20Settings\AppComponentMode=prome_fushion
wpsoffice\Application%20Settings\AppComponentModeInstall=prome_fushion

from ~/.var/app/com.wps.Office/config/Kingsoft/Office.conf file.

[fwolf]

By the way, removing this 2 line of config, also solved my wps missing titlebar problem, and newest version won't start problem !

In Ubuntu, it in ~/.config/Kingsoft/Office.conf .

[dwuku]

Is it possible to actually make AIO work?

[gasinvein]

@dwuku Does it work in non-flatpak package?

[dwuku]

Yes, works fine. I was using 11.1.0.9080 deb package before switching to the flatpak

[gasinvein]

Looks like WPS Office all-in-one mode doesn't work when XDG_CONFIG_HOME is set, even if it points to the default path ($HOME/.config). Not sure if this can be easily fixed on our side.

[dwuku]

@gasinvein just out of curiosity, how did you figure this out?

[gasinvein]

@dwuku I've tried to reproduce flatpak environment on host, e.g. set XDG_*_HOME vars, which are usually unset otherwise.

[gasinvein]

We can workaround this by symlinking ~/.config to $XDG_CONFIG_HOME in the sandbox and then unsetting XDG_CONFIG_HOME upon startup, but this can break things for users who've added filesystem overrides, especially --filesystem=home.

[dwuku]

Symlinking ~/.config did not work for me. But interestingly, if you do not touch anything else and only unset XDG_CONFIG_HOME by entering a shell inside the flatpak, AIO mode does start working. Of course as soon as you exit the shell the config files are deleted (I think the new ones are created in /Kingsoft ?)

[gasinvein]

@dwuku I've meant symlinking ~/.config and unsetting XDG_CONFIG_HOME both inside flatpak sandbox, surely.

[dwuku]

@gasinvein could you please elaborate a bit on how to create this symlink? I create a filesystem override to ~/.config first?

[gasinvein]

@dwuku I'll open a PR with modified wrapper once/if I figure out how to do this safely.

I create a filesystem override to ~/.config first?

No! You absolutely shouldn't create filesystem overrides like this.

[dwuku]

@gasinvein alright thanks, but could you still answer the question please? Just for knowledge. What did you mean by symlinking ~/.config to $XDG_CONFIG_HOME ?

[gasinvein]

@dwuku By default, in the flatpak sandbox /home is on a per-instance tmpfs, so normally ~/.config doesn't exist in the sandbox. Instead, a special directory ~/.var/app/com.wps.Office/config is mounted from host, and XDG_CONFIG_HOME env var points to it.
My idea (not sure if it's a good one, though) was to add to the wps.sh wrapper something like
ln -s $XDG_CONFIG_HOME $HOME/.config followed by unset XDG_CONFIG_HOME,
so that we'll end up with config files still stored in ~/.var/app/com.wps.Office/config, but without XDG_CONFIG_HOME env var set.
Doing so is unsafe, since user may have filesystem overrides, so we'll have to check that ~/.config doesn't exist in sandbox, first.

[dwuku]

@gasinvein ah got it, inside the sandbox! For some reason I was thinking about the ~/.config of the host. Thanks so much for explaining in detail.

This workaround indeed does the job, I gave it a try just now.

The behaviour is a bit confusing though.
Once that symlink is created, the application does work fine, but the wrapper throws a message in the beginning which says "No config exists, creating one" and when you do ls / there is a new /Kingsoft directory (which is otherwise not created when XDG_CONFIG_HOME is not unset)

[gasinvein]

@dwuku The wrapper needs to be modified to handle this correctly.

[dwuku]

@gasinvein oh right, yes.

Also, I'm wondering if this could be useful in any way. Although, goes against sandboxing principles I guess.

[gasinvein]

I think it was fixed by latest upstream update, I can't reproduce it since of 11.1.0.10161
Can you please re-test if the issue is still present?

[okkymabruri]

Hi Guys, I got this issue on my machine, ubuntu 21.04 with WPS 11.1.0.10161
Could you tell me how to solve this issue?
@gasinvein

[gasinvein]

@okkymabruri I can't reproduce it anymore, but you still can try this.

[okkymabruri]

@gasinvein , I have tried it on
~/.config/Kingsoft/Office.conf
~/.var/app/com.wps.Office/config/Kingsoft/Office.conf
but still doesn't work

[Sciroccogti]

@fwolf

In Ubuntu, it in ~/.config/Kingsoft/Office.conf .

In my Ubuntu 22.10, the file does not exist. Is it placed somewhere else?

[fwolf]

I'm using debian sid now, and the conf file is still there, dont know Ubuntu 22.10 change it or not.

@fwolf

In Ubuntu, it in ~/.config/Kingsoft/Office.conf .

In my Ubuntu 22.10, the file does not exist. Is it placed somewhere else?

[Sciroccogti]

OK I find it in ~/.var/app/com.wps.Office/config/Kingsoft/Office.conf.

In my case, the two lines mentioned by @gasinvein do not exist originally, and manually adding them will enable all-in-one mode. That's great.

I'm using debian sid now, and the conf file is still there, dont know Ubuntu 22.10 change it or not.

@fwolf

In Ubuntu, it in ~/.config/Kingsoft/Office.conf .

In my Ubuntu 22.10, the file does not exist. Is it placed somewhere else?