I messed up Edit/View in dispVM

[corporateblush]

I messed up something with Edit/View in Disposable VM option.

I have this line in my rpc policy:

qubes.OpenInVM * @anyvm @default ask

but when I choose the option to View/Edit as well as dvm template, dispVM fires up and immediately shuts down.

Any idea how to start debug tracing? Or even better, what could I mess up?

I tried:
qubes.OpenInVM * @anyvm @dispvm ask

too, but with the same result. After each time I changed rpc policy I restarted qubesd.

If I manually copy file to said dvm template’s dispVM, I can view/edit it there.

Thanks in advance.

[murdock]

Do your disp vm knows, what to do with the file, that you are trying to open in that dispvm. Specially, has your /usr/share/mimeapps.list in the dispvm template the correct entries?
If your dispvm does not know, how to handle that type of file, then it starts, recognizes, that it has no application for that filetype and shuts down after that (same behaviour, as you described).
For check, please copy the file over to the dispvm template, open a thunar filemanager, click on that file with the right mt and chose “open” (or double click that file).
If the file is not started in the correct application or viewer, it can be the reason for the problem.

[parulin]

The command qvm-open-in-dvm doesn’t output anything useful?

I dont think it is related the RPC policies as the disposable opens up.

[corporateblush]

@parulin

qvm-open-in-dvm

Thanks, but I don’t think this command works at all anymore for me. it’s “vm” not “dvm”.
EDIT: Actually it works from the command line with the same outcome, but not even firing up dipsVM when using in File Manager via context menu “Open with other application…”

@murdock

Do your disp vm knows, what to do with the file, that you are trying to open in that dispvm.

As I wrote, when I send the file to a dispVM created by said dvm-template and double click it opens. Now, if in that dispVM I’m trying to View the file with /usr/bin/qvm-open-in-vm @dispvm:dvm-template of that very dispVM, new dispVM fires up and immediately shuts down.

So both dispVMs have the same dvm -template, but inconsistent behavior when trying to view them inside dispVM or via other dipsVM invoked by the command above and created by the same dvm-template…

[unman]

As I wrote, when I send the file to a dispVM created by said dvm-template and double click it opens. Now, if in that dispVM I’m trying to View the file with /usr/bin/qvm-open-in-vm @dispvm:dvm-template of that very dispVM, new dispVM fires up and immediately shuts down.

You are very coy about the file type, and whether this affects all
file types or just the one. Give a little.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

[corporateblush]

@unman

You are very coy…

… all over my body. But let’s say that with any dispVM created by my default fedora-mostly-minimal dvm-template (so, not the stock one) I can’t view/edit any plain text document, except the way described above. Nor with any other dvm-template. I don’t want to complicate it here additionally with the fact that in a specific qube (appVM) I can do it with only one of those “non-working” dvm-templates, and it works only for that qube. Now you at least can guess why I was shy…

But if I have to choose, may I also ask you to look at this, since that is of a higher priority for me / more annoying and more frequent than the issue from the OP

Qubes Update tool and Qubes contrib repo fc42

So, https://contrib.qubes-os.org/yum/r4.2/current/vm/fc42 is obviously non-existent. When updating qubes from within templates, “404” is letting update process nevertheless, while Qubes Update Tool doesn’t. It is painfully annoying. I don’t want to set skip_if_unavailable=True when “404” because I want it “False” for any other errors. Any other idea what to do to avoid manual qubes updating?

Thanks in advance

[corporateblush]

I’d be glad to continue. but on said topic, so I’m asking @deeplow to move offtopic posts there

[deeplow]

Now moved