Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qvm-move/copy-to-vm still prompts xenity response #9615

Open
kennethrrosen opened this issue Nov 30, 2024 · 2 comments
Open

qvm-move/copy-to-vm still prompts xenity response #9615

kennethrrosen opened this issue Nov 30, 2024 · 2 comments
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: core diagnosed Technical diagnosis has been performed (see issue comments). P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@kennethrrosen
Copy link

kennethrrosen commented Nov 30, 2024

How to file a helpful issue

Qubes OS release

4.2.3

Brief summary

Despite commands such as qvm-copy-to-vm personal [filename], a prompt still appears, requiring user input for destination qube. The command will exit without a destination vm, so this behavior seems as though it is intended for something that it says is not allowed.

Steps to reproduce

Run either qvm-copy-to-vm [dest-qube] [filename] or qvm-move-to-vm [dest-qube] [filename] from an appvm or standalonevm terminal.

Expected behavior

Files or directories are moved/copied without further input from user.

Actual behavior

Redundant user input is required via GUI prompt. Misleading error message on misuse of command.

@kennethrrosen kennethrrosen added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Nov 30, 2024
@marmarek
Copy link
Member

There is qvm-copy / qvm-move which avoids entering the name twice - you get only the prompt. qvm-copy-to-vm / qvm-move-to-vm used to tell you that, but I see they currently don't.

On the other hand, if you want to allow some of the copy operations without confirming at all, you can set it up in the "qubes global config" tool (file access tab) - choose "always" permission, and then you can use qvm-copy-to-vm without extra prompt (for the directions you allow).

I'll leave this open, to fix the message pointing at qvm-copy/qvm-move

@kennethrrosen
Copy link
Author

@marmarek thanks as always!

@andrewdavidwong andrewdavidwong added C: core diagnosed Technical diagnosis has been performed (see issue comments). affects-4.2 This issue affects Qubes OS 4.2. labels Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: core diagnosed Technical diagnosis has been performed (see issue comments). P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

3 participants