On Mon, Nov 05, 2018 at 01:56:00PM -0800, Otto Kratik wrote: > > Thanks for the extensive troubleshooting. > > > > It looks as if there's a problem *either* with the service *or* with the > > desktop files on fedoratest. > > Can you check the contents of /etc/qubes/rpc/policy/qubes.StartApp to > > make sure that you dont have a "deny" statement at the top of that file? > > You could temporarily insert a line at the top: > > dom0 $anyvm allow > > $anyvm $anyvm allow > > > > Just concentrate on using: > > qvm-run -a --service --dispvm=fedoratest -- qubes.StartApp+firefox (or > > gedit) > > Check the log file in /var/log/qubes : you should see a log created for > > whatever dispVM is atrted and qubes.log updated. > > > > unman > > > So during testing, even though I'd stopped all other VMs from running, I > started noticing some odd slowdowns and other memory-related issues, wondered > if RAM shortage was affecting my attempts, and decided to reboot and try > again from scratch with no autostart VMs enabled. > > After that, I am now able to run pretty much any app in a Debian or Whonix > based DispVM without issue. In Fedora based DVMs, some apps like Firefox, > Filezilla, Calculator etc all run fine from the DVM menu, while other apps > such as Gedit and Nautilus/Files simply don't seem to want to act as the > "launch leaders" for DispvM's. > > Meaning, the DispVM gets launched, but those apps don't open, and then the > DVM halts again a minute or so later, as previously described. If I launch > Firefox instead first in a Fedora DVM, and then from the widget select "Run > terminal" for that very same already-open DVM, I can then launch Gedit or > Nautilus or any other app from the command line without any problem. But > those apps won't open as the initial "launch-apps" for Fedora DVMs. > > By contrast, in Debian DVM's I can launch KWrite or Dolphin or whatever other > equivalents easily, a well as Firefox or Tor Browser, and so far haven't > found one that refuses to launch. > > Thus it seems like a bit of an interoperability quirk between Fedora26 and > the DVM system, so far as I can tell. Results are the same whether trying > from gui menu or dom0 command line, though admittedly with some apps like > Gedit, I am unsure which of the following I should be typing: > > qvm-run -a --service --dispvm=fedoratest -- qubes.StartApp+gedit > qvm-run -a --service --dispvm=fedoratest -- qubes.StartApp+org.gnome.gedit > qvm-run -a --service --dispvm=fedoratest -- "qubes.StartApp+Text Editor" > > All of them fail in the same way, however.. so I'm not sure it makes much > difference. > > Out of curiosity for comparison, are you able to launch Gedit or > Nautilus/Files in a Fedora based DVM without issue, as the initial launch-app > either from the menu or command line? >
I'm glad that some progress is being made. I wonder if there's some issue with the desktop files in Fedora which are preventing those applications from running? Those symptoms are exactly those that fit with problems with the desktop files. I dont have Fedora here to test, I'm afraid: Debian and BSD only. If you open a Fedora based qube, do the applications work if you try to open files that would use them? I mean create text file, and then double click on it in nautilus, etc etc unman -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181106152947.7u5idnqomx5g3pmm%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
