If there is “not enough RAM”, rads does not attempt to start gdm3.
There could have been a bug in theory if rads supported only gdm but not gdm3. Then with “not enough RAM”, gdm3 would have still been started, because rads might have missed to inhibit autostart of gdm3. But that’s not happening here.
The root cause is that Virtual Consoletty1 is missing by default which is a systemd issue:
For first boot into Whonix CLI:
The workaround until virtual console tty1 is automatically started is to use a different virtual console such as tty2 as per documentation.
# replaces the getty
Problem seems to be that gdm takes tty1 by default instead of tty7 (lightdm default). That’s why gdm is getting in the way.
Somehow above issue is even triggered although rads already created the required status files for systemd to recognize that “gdm condition for startup failed”. Seems like the systemd unit keyword Conflicts= is also active even if gdm won’t start due to “condition for startup failed” (status file created by rads because “not enough RAM”).
Just to clarify:
Virtual console is different from serial console.
(Actually non-trivial from wikipedia to guess who serial console is used nowadays in context of host reading textual output from the kernel from a KVM VM without need for a functional graphic device/driver.)
This forum thread is about virtual console only.
Serial console is really cool but entirely different thing as far as I understand. (Serial Console) Should be unrelated.