Sys-gui installed but no session menu for it on login screen?

Hi,

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.

What should I do to actually use the sys-gui?

Sys-gui is not about pass-through graphics acceleration to VMs, it’s for isolation of graphical devices from dom0 for security reasons:
Qubes Architecture Next Steps: The GUI Domain | Qubes OS

Even so, there is no session option on login interface and the question remains.
What should I do?

I still hope for feedback.

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 didn’t try sys-gui myself so I can’t help you out here.

Thanks for clarifying.

I can just guess that you missed something during sys-gui setup and it didn’t install properly.

That’s not true. I did exactly what the documentation says.

I hope someone who has experience to help as I am careful not to mess up something and not be able to use Qubes OS as a result.

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.

I kindly ask again for help.
I hope that’s not considered inappropriate.

I’d try to reinstall the sys-gui and see if there are any errors or warnings in the qubesctl commands output. Or post the logs here.

The section in documentation called “Delete GUI domain” explains how to set default_guivm as dom0. However, this seems unnecessary in my case as it already is dom0. Right?

Also, when I installed the sys-gui there were no error messages when running the qubesctl commands, only success was reported, so there is nothing to post.

This is quite confusing.
What should I do?

That means that something went wrong during installation because default_guivm should’ve beed set to sys-gui:

At this point, you need to shutdown all your running qubes as the default_guivm qubes global property has been set to sys-gui.

That means that something went wrong during installation

How do I know what that something is?

I don’t know what could go wrong. Try to reinstall sys-gui and check the logs in journalctl and in /var/log/qubes/*sys-gui.log.

I don’t know what could go wrong.

How do I find someone who knows?

Try to reinstall sys-gui and check the logs in journalctl and in /var/log/qubes/*sys-gui.log.

Which logs (in which VM)?

I don’t know much about sys gui but /var/log/qubes/*sys-gui.log will be on dom0.

If you tried to reinstall sys-gui but the problem remains then you can open an issue on github:
Issues · QubesOS/qubes-issues · GitHub