Hi All,
I’m trying to get the global clipboard working. For testing I’m trying to copy text & the file.txt between two non admin vms.
I’ve tried CTRL+C →
CTRL+SHIFT+C: (“Copied # bytes message”) →
Click to focus in other vms file manager →
CTRL+SHIFT+V: (no-message) →
CTRL+V: “Error: There is nothing on the clipboard to paste.”
Also in the Qubes OS Global Config window under both the Clipboard Policy tab, and the File Access tab I get the following error when I press okay:
WindowTitle: “[Dom0] Could not save changes”
WindowContent: "The following error occurred: Command ‘[’/user/lib/qubes/qubes-rpc-multiplexer’, ‘policy.Replace+40-config-clipboard’, ‘dom0]’ returned non-zero exit status 1.
The same for File Access except it says “filecopy” instead of “clipboard”.
Thanks in advance for any effort to help!
Do you get any more details in this message? Or maybe from journalctl
in dom0? It sounds like you have a typo somewhere in the policy, possibly in a different file.
Hi @marmarek,
Thanks for helping.
After CTRL+C → CTRL+SHIFT+C I got the following warning in systemctl once, but cannot reproduce it:
widget-wrapper[4374]: [date pyinotify WARNING] Unable to retrieve Watch object associated to <_RawEvent cookie=0 mask=0x100 name=qubes-clipboard.bin.xevent wd=1>
And when opening the Qubes Os Global Config it says:
dom0 sudo[7231]: PAM unable to dlopen(/usr/lib64/security/pam_sss.so): /usr/lib64/security/pam_sso.so: cannot open shared object file: No suc file or directory
Then:
dom0 sudo[8697]: PAM adding faulty module: /usr/lib64/security/pam_sss.so
Besides that when watching live with systemctl -f nothing happens when I click okay leaving it on default, or custom (without changing it) and that same message pops up that I mentioned in my first post in a window.
cat /etc/qubes/policy.d/50-config-filecopy.policy:
qubes.Filecopy * @anyvm @adminvm deny
qubes.Filecopy * @anyvm @anyvm ask
cat /etc/qubes/policy.d/90-default-gui-daemon.policy
qubes.ClipboardPaste * @adminvm @anyvm ask
qubes.ClipboardPaste * @anyvm @anyvm ask
qubes.WindowIconUpdater * @anyvm dom0 allow
Hope this clarifies something, thanks again for the help!
See what happens on Ctrl+shift+v
Nothing happens when I am watching systemctl live with -f when I do ctrl-shift-v or ctrl-v.
Thanks!
Check if qubes-qrexec-policy-daemon
service is alive (systemctl status qubes-qrexec-policy-daemon
) - if not, start it.
Thank you @marmarek you fixed it! It wouldn’t start, but it pointed me to syntax errors in files I just had to reset by deleting the contents.
Steps for future reference:
systemctl status qubes-qrexec-policy-daemon
It said
Active: failed
qubes-qrexec-policy-daemon.service: Failed with result 'exit-code'.
So I then started it like you said with:
sudo systemctl start qubes-qrexec-policy-daemon
Then after checking again if it was active it said the same thing. So I looked in:
/etc/qubes-rpc/policy/30-use.policy
like the traceback error in systemctl status mentioned "invalid action: * "
I think that was populated from a previous edits I made so I deleted the contents of the file.
Then when I tried to start it again I got another syntax error saying that in
/etc/qubes/policy.d/50-config-clipboard.policy:1: wrong number of fields
So I deleted the contents of the file and It started correctly.
Then I restarted the qubes and I could copy and paste text and files between them.
Thanks for your help!
1 Like