Comment 4 for bug 1799083

> Did this issue start happening after an update/upgrade?

Yes, it happened after the upgrade to Ubuntu 18.10. The subject of the bug report was "virtual console unavailable with upgrade of cosmic or Ubuntu 18.10". The logs included in my original bug report showed "UpgradeStatus: Upgraded to cosmic on 2018-10-20 (1 days ago)".

> Was there a prior kernel version where you were not having this particular problem?

Yes. My bug report said "Using the older release kernel package 4.15.0-33.36, the virtual terminals work as normal."

> Would it be possible for you to test the latest upstream kernel?

Yes. I tested kernel v4.19-rc8 and kernel v4.19.

After the initial upgrade of Ubuntu 18.10 I noticed the problem immediately because I often login to the virtual terminal so that I can killall chrome or killall firefox when the laptop becomes sluggish from running out of memory. I searched online and bug reports and tried a few things attempting to resolve the issue. I also compared cat /proc/cmdline of the two kernels running and a few other things which didn't help.

Another thing I tried after finding some info on either stack exchange or the Ubuntu forums was to uncomment #NAutoVTs=6 /etc/systemd/logind.conf and after checking the logind.conf(5) man page I changed it to NAutoVTs=4. It seemed to do nothing with the new kernel 4.18.0-10.11, and the 4.15.0-33.36 kernel displayed tty 1-4 and 6, but not tty5. so I changed the file back.. Then here's where things make even less sense, tty 1-6 all work now. One thing that was odd is I did a pstree -ap and only tty1 showed up, then logged into tty1, went back to the graphical Lubuntu terminal and all 6 tty's or agetty processes were active. It seems that if agetty tty1 is spawned the others activate when I enter alt-F2 etc...

So this doesn't make a lot of sense because reverting the only change made in /etc/systemd/logind.conf seems to have fixed the problem running kernel package v4.18.0-10.

Kernel testing:
v4.19-rc8
Virtual terminals were working.

kernel v4.19
Virtual terminals were not working. Furthermore the login.conf change didn't seem to fix the issue.

kernel v4.18.0-10
Virtual terminals are working.

In other words the results are somewhat confusing because it seems to be producing random results. It's not clear that the bug is in the kernel, it could be systemd, agetty, system libraries or an interaction of the various components.