I am willing to give GUI domain a try. I have followed the documentation for the hybrid version. As a final step it instructs:
“At this point, you need to shutdown all your running qubes as the default_guivm qubes global property has been set to sys-gui.”
So, I have rebooted the computer.
“In order to use sys-gui as GUI domain, you need to logout and, in the top right corner, select lightdm session type to GUI domain (sys-gui).”
OK but there is no such option on top right. There I have only one choice - XFCE Session. I can simply login as usual and I don’t see any changes, apart from a running VM named sys-gui. Executing systemctl status lightdm shows that this service is running but I don’t notice any speed up of visual UI. For example, the scrolling in the text editor of the default “untrusted” VM is still choppy.
I didn’t try sys-gui myself so I can’t help you out here. I can just guess that you missed something during sys-gui setup and it didn’t install properly. I can just suggest you to look through these threads and try to figure out what’s missing:
I have gone through all the threads you linked but there is no answer to my question there.
Something more: I tested what one of the threads suggests and created a test-vm, then I set its guivm to sys-gui through qvm-prefs. Then I tried to run apps in test-vm (XTerm, Firefox). Result: nothing shows. I also notice that I can’t even open a terminal in sys-gui itself. OTOH, I notice some CPU load (~14%) on sys-gui when looking at the running Qubes in tray menu, even with test-vm not running at all.
I really hope someone can shed some light on this.
After giving up on sys-gui and removing it from the system, today I decided to try sys-gui-gpu, as I do have an Intel VGA (integrated in the CPU).
Following strictly the instructions in the docs, after rebooting, I was unable to use sys-gui-gpu too - after login, it is not running. The moment I attempt to start it manually, the whole computer experiences a hard reset. I retried the whole procedure but that didn’t change anything, except that the second time the system reset happened instantly at the last step: