Unfortunately, it didn't work still when qubes-gui-agent was running. I tried recompiling everything again, and the results have changed quite a bit. Now, instead of autohiding the HVM window in dom0, I can see a very clear failure which points me in the direction of Xorg instead.
Sadly, this feels like a regression, but alas... I'm sure I'll get there eventually. As far as "xl console lfs", dom0 reports "unable to attach console". And in terms of dom0, it is still giving no sense of failure: $ qvm-run --pass-io personal whoami user $ qvm-run --pass-io lfs whoami $ qvm-run lfs "touch /tmp/dummy" Running 'touch /tmp/dummy' on lfs Needless to say, /tmp/dummy doesn't ever emerge. The new error is.... systemctl status qubes-gui-agent.service ... Process: 660 ExecStart=/usr/bin/qubes-gui $GUI_OPTS (code=exited, status=1/FAILURE) ... lfs qubes-gui[660]: XIO fatal IO error 11 (Resource temporarily unavailable on X server ":0" lfs qubes-gui[660]: after 37 requests (36 known processed) with 0 events remaining) X works (startx shows me a desktop and consoles), but nothing yet from getting Qubes GUI agent and qrexec. -- 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/92378a13-da16-44e4-98b7-ee379179bbba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
