The solution was to symlink default.target to graphical.target. So it was to do "systemctl set-default graphical.target" or deleting the existing default.target in /etc/systemd/system/default.target and reboot. It was symlinked to the wrong target. https://wiki.archlinux.org/index.php/Systemd#Change_default_target_to_boot_into
On Tuesday, September 29, 2020 at 12:06:31 AM UTC-4 xyzo wrote: > I have a Kali HVM that was working fine until I installed a few of qubes > core packages on it. I installed qubes-usb-proxy, qubes-core-qrexec, > qube-core-agent. It required a few more qubes packages as dependencies like > qubesdb.etc.. The installation was successful and I double checked that > qrexec, core-agent daemons were successfully running. So everything was > good so far. And I was able to attach usb devices to HVM, copy to other Vm > from HVM..etc.. But something got messed up in Xorg-server. I'm not sure > what exactly happened. Now every time I boot into the HVM, I have to login > through tty first then type "startx" for xinit to pull up the desktop > environment. I already tested with a few different DE, gdm, lightdm. They > all worked when I typed startx. So it's not the DE. it's something in > xorg. This is my Xorg.0.log. I noticed it says glamor failed. but I > failed to fix that. Any help is really appreciated . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c703f8ef-2690-4e1e-a1fc-f4ea3540336cn%40googlegroups.com.