Hi Guys, I’m new to qubes and need some help with the terminal using. : )
So I was try to copy and paste code to terminal on a disposable VM. When copying everything works fine but when pasting (Ctl + Shift + V) it shows like following
‘ERROR (disp6060) the paste from disp6060 to disp6060 is denied by policy.’
But when I use mouse to paste it works ok
Can i solve this by any means? or any other short cut keys available? Appreciate for the help!
Remapping either terminal copy and past actions or qubes copy and paste actions is a solution. Qubes clipboard settings are in the global config.
The default is bad, and the reason for not changing it is silly: qubes ctrl-shift-c/v collides with terminal c&p · Issue #4573 · QubesOS/qubes-issues · GitHub
You can use Ctrl+Inser and Shift+Inser to copy-paste in terminal.
The comment doesn’t look like the real reason. It refers to another statement that I would be curious to read.
This happens because (Ctl + Shift + V) is a shortcut used by Qubes for
inter-qube pasting. That is blocked in the case of pasting from the
global clipboard back to the originating qube, which is why you get the
message about policy.
You can solve this in two ways:
IMHO, mouse-wheel click is the easiest solution, as it’s easy to remember, easy to use, and requires changing no shortcuts. If you’re not yet accustomed to the default global clipboard shortcuts (and especially if you’re already accustomed to using Ctl + Shift + V for terminal pasting), then changing the global clipboard shortcuts might suit you better.
Later on in the conversation adw links back to this comment. It should have decent summary of the reason or somehow link to in. Perhaps we’re missing something.
@adw please give us the knowledge. Surely little people (if any) depend on a default GUI key combination, and nobody should depend on it this hard
Ah, sorry, I made that comment over seven years ago and can’t recall what I was referring to. I tried searching to see if I could reconstruct my train of thought but to no avail. I apologize for neglecting to include a summary or reference in the comment at the time. (I’ve made an effort to be better about that sort of thing since then.)
However, rather than poring over my old comment, which could be outdated by now anyway, I think it would be more productive if we just ask @marmarek for his current thoughts on the matter.
Hm, what do you mean by “depend on”? I’m guessing the vast majority of Qubes users probably don’t change the defaults and end up getting used to them over time.
It doesn’t really matter what I mean by depend from the perspective of the issue.
If you still want to know, this is just my attempt to reason how the cost of changing the default copy shortcut could outweigh the benefit:
Majority of Qubes users don’t care about this - they either have it salted or otherwise manage their config or can set it the way they want manually. All competent Qubes users know how to do it, or can guess how. Even with no automation, you only need to set it once per install. Friction is very small, filing an issue is harder. Even searching for an issue might be harder.
Thus, it got to be one of the other groups: incompetent users and people that somehow depend on this (not just for copying)
Incompetent users seem to prefer mod4-based shortcuts, because ctrl+shift-based shortcuts are commonly used for terminals while mod4-based aren’t used anywhere else by default (I think). This problem reoccurs on the forum from time to time. Since both sets of shortcuts are new to them, there is no other difference.
Only guess I have left at this point are the people that depend on this. Maybe for a script, maybe because they teach Qubes and don’t want to change their slides, maybe because they deploy Qubes and don’t want to automate this.
I don’t know, I still believe no critical system of any kind should depend on this, and fixing this is so trivially easy that it cannot be more costly than missing out on a conflict-less binding by default.
Don’t dwell on your old comment 
Could this be relevant?
Thank you very much! This works perfectly fine! 