in my policy. I have set default dispvm template for Qubes based on fedora 40 (dvm) template. When I doubleclick, or via context menu entry try to open/view/edit file in dispvm, dispvm starts, and then I’m getting dialog box question form that dispVM asking me
Are you sure you want to start another disposable VM?
If I choose No, it shuts down and I can’t view file. If I choose Yes, it would open another dispVM, with the same question form that new dispvm, and so on, and so on, without possibility to ever Open/View/Edit file in dispVM.
WTH?
I have no such problems in dispVMs based on fedora 39.
That’s strange. It seems to work as expected for me, everything is default and using fedora 40 dvm template as installed during initial qubes OS configuration post-install. Are you sure that you don’t have a conflicting policy entry that is being read before that line?
:EDIT: oh you said it works fine using Fedora 39 dvm template. I have no idea then.
Is it a fedora-39-minimal template or a standard fedora-39 template?
I’ve tested this with a default fedora-39-minimal template without any changes and it behaves in the same way.
I guess there are no application associated by default with text files and if no application is found it’ll open this file in the new disposable by default.
So for the minimal templates you need to configure the files association manually.
After inspecting @qub411’s and @apparatus’ leads, I have found that for some reason /usr/share/applications/defaults.list differs in fedora-40-minimal from previous versions.
fedora-40-minimal has only
text/plain=qvm-open-in-dvm.desktop
which obviously produces loop, and once I changed it to equals with fedora-39-minimal and earlier