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-open-in-(d)vm behaviour with directories #9360

Closed
alimirjamali opened this issue Jul 18, 2024 · 3 comments · Fixed by QubesOS/qubes-core-agent-linux#513
Closed

qvm-open-in-(d)vm behaviour with directories #9360

alimirjamali opened this issue Jul 18, 2024 · 3 comments · Fixed by QubesOS/qubes-core-agent-linux#513
Assignees
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. pr submitted A pull request has been submitted for this issue. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. ux User experience

Comments

@alimirjamali
Copy link

How to file a helpful issue

Qubes OS release

R4.2

Brief summary

According to a user on forum:

However, qvm-open-in-vm does not work correctly when I’m giving it a directory.

User tries to open a directory in a disposable and got confused, expecting it to be copied to Disposable and be opened in File Manager.

Steps to reproduce

  • Run qvm-open-in-dvm DIRECTORY
  • A DispVM is spawned
  • It shuts down immediately

Expected behavior

Either show an error message if the target is not a regular file; or copy the entire directory to destination VM and open it in Thunar (or applicable File Manager)

Actual behavior

Confusion

@alimirjamali alimirjamali 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 Jul 18, 2024
@alimirjamali alimirjamali changed the title qvm-open-(d)vm behaviour with directories qvm-open-in-(d)vm behaviour with directories Jul 18, 2024
alimirjamali added a commit to alimirjamali/qubes-core-agent-linux that referenced this issue Jul 18, 2024
alimirjamali added a commit to alimirjamali/qubes-core-agent-linux that referenced this issue Jul 18, 2024
@unman
Copy link
Member

unman commented Jul 18, 2024 via email

@alimirjamali
Copy link
Author

what about all those other possible targets that wont work?

The patch I submitted exactly does that. Clear error message on targets that won't work (directories, symlink, ...). But we have to consider that this tool is also used to open URLs. So it had to be allowed in the conditions.

alimirjamali added a commit to alimirjamali/qubes-core-agent-linux that referenced this issue Jul 19, 2024
alimirjamali added a commit to alimirjamali/qubes-core-agent-linux that referenced this issue Jul 19, 2024
@andrewdavidwong
Copy link
Member

Since both manpage and help state that these apply to files, the "expected behavior" is misplaced.

In Linux, directories are files.

@andrewdavidwong andrewdavidwong added C: core ux User experience diagnosed Technical diagnosis has been performed (see issue comments). pr submitted A pull request has been submitted for this issue. affects-4.2 This issue affects Qubes OS 4.2. labels Jul 21, 2024
marmarek pushed a commit to QubesOS/qubes-core-agent-linux that referenced this issue Aug 23, 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. pr submitted A pull request has been submitted for this issue. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. ux User experience
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants