Qubes global config returning error

guruji · May 20, 2025, 1:58pm

Hi everyone, I got a new qubes certified laptop and I got following error in the Qubes global config utility.

Any change in the Global config returns the error below after an attempt to save the change:

The following error occurred: Command "/usr/lib/qubes/qubes-rpc-multiplexer’, ‘policy.Replace+50-config-filecopy’, ‘domo’ returned non-zero exit status: 1.

Once I got that first error, my qrexec setups stopped communicating as well as copying the clipboard between VMs.

Qubes restored from the old laptop, except for dom0.

Any idea how to solve that?

kenosen · May 20, 2025, 11:07pm

Reported this issue a while back. And still face the same issue on a fresh install. I gave up and use the Policy Editor now instead.

github.com/QubesOS/qubes-issues

Error when attempting to save changes in Qubes Global Config

opened 08:20AM - 12 Oct 23 UTC

kennethrrosen

C: manager/widget P: default needs diagnosis affects-4.2

[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/) #…## Qubes OS release 4.2.0-rc3 ### Brief summary When attempting to `apply` or `ok` settings in QUbes OS Global config, changes are not saved for exceptions to updates checker and update proxy. ### Steps to reproduce Open Qubes OS Global Config. Enable Checking for updates for all existing qubes Check `except the following qubes...` Select a qube and Apply Or change update proxy from sys-net to whonix-16 ### Expected behavior Changes are applied, dialogue exists. ### Actual behavior The following error occurs, and no changes are saved: ``` The following error occurred: Command '['/usr/lib/qubes/qubes-rpc-multiplexer','policy.Replace+50-config-updates','dom0']' returned non-zero exit status 1. ```

Was supposed to be fixed.

github.com/QubesOS/qubes-issues

Stop using `qubes-rpc-multiplexer`

opened 09:17PM - 27 Mar 24 UTC

closed 01:52AM - 04 Feb 25 UTC

DemiMarie

C: core P: default pr submitted

[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/) #…## The problem you're addressing (if any) Executable RPC calls are made via a shell script, `qubes-rpc-multiplexer`. This slows things down for no real benefit. ### The solution you'd like Have the C code invoke the executable directly. ### The value to a user, and who that user might be Users will benefit from faster qrexec calls. ### Completion criteria checklist (This section is for developer use only. Please do not modify it.)

Some have found success by reverting policies.

guruji · May 21, 2025, 6:21am

In a funny way I get the same issue now on my old qubes laptop too.

The only common thing in between the two is the newest update applied and that I opened the Qubes global config on both and tried to save some changes.

So what is now the workaround for this situation? It is my main laptop actually and I am completely kicked out from any reasonable work You change the params in the /policy.d/config files directly?

Any help really appreciated.

kenosen · May 21, 2025, 10:25am

Yes. Give that a try.

guruji · May 21, 2025, 8:41pm

Solved!

Interestingly I found out that I used to have config related to the non-existing VM (delete). Once I deleted the content of the file, rebooted, all works well.

Interestingly this mistake that can happen easily, but completely disables basic functionalities of Qubes - qrexec itself and any communication in between Cams.