As per the video, the first TTY1 is showing for about 10 sec, then it goes black for 5 sec and then the TTY1 comes back for three sec.
The defaults.conf file has a setting called debug. If I make it true and reboot then there should be error messages in system.log Or is it .xsession-errors?
Wait I will check the .xsessions-errors file first, just in case.

FWIW This file has lots of entries even on a system that works fine. Sometimes it's just reporting a bug and those need to be fixed in the code and recompiled.

Mine is huge and my system works fine except for one hardware related annoyance which I have not been able to fix yet and probably can't fix without fixing code and recompiling.
Anything more than that is beyond my current scope of knowledge which means I would be googleing and reading books until I find the answer.

Prsman wrote:Late to this party, I also have this feature or problem. I get the tty1 login twice, And the text changes color randomly. Might be white, next time yellow, next time brown. my dmesg error is this:

I thought this was a feature. I haven't tried to login at that point. My grub has quiet splash. I also get the tty1 login at shutdown too. Ideas anyone? Thanks

For me I would try updating the firmware for the BIOS. It's dangerous to do it though. If you mess it up your computer is bricked.
At a minimum you should do it while on a UPS because if you lose power in the middle of the write it's going to be messed up.
That's me personally though and only if it's actually causing real problems or if the update adds a needed feature. Do you think it's truly causing a problem?

I am running the latest BIOS. Is this a problem? No, my computer runs fine. The question is, why does my boot sequence have this feature? The operating
system should be consistent for everyone. Lets call this action a quirk. Thanks for your time and help.

Prsman wrote:I am running the latest BIOS. Is this a problem? No, my computer runs fine. The question is, why does my boot sequence have this feature? The operating
system should be consistent for everyone. Lets call this action a quirk. Thanks for your time and help.

If your computer runs fine then that's your answer. It runs fine. I think you guys have gotten yourselves focused on this idea that something is wrong when the computer is actually booting up normally.

This bug seems to add about 10 seconds to the boot time of my 5 year old Samsung laptop running 18.1 Mate which I find significant. Playing with the nvidia/nouveau drivers has not effect. Both the mate 18.1 and 18.2 mate 64 bit livedvds show the same problem.

No, I have not found a solution yet. I am just living with it, because my computer is good enough that the boot time is not substantially different, at least to me, at I can live with it looking a little sloppy. It kind of brings back reminiscence of the old days, so it's kind of fun. However, I'm glad I'm not the only one who had or noticed this problem. If you find anything, please post it.

Just giving an update. not sure if this is a solution. I re-installed the OS. Did a reboot after install and did not have the tty1. Installed the nvidia driver and rebooted and did not have the tty1. Then I did the update manager and rebooted and got the tty1. So I went to check what was updated and UM installed nvidia prime.
I used Synaptic to completely remove nvidia prime and rebooted. No tty1. So far so good, its been two days. Will see how long this problem stays away.

Prsman wrote:Just giving an update. not sure if this is a solution. I re-installed the OS. Did a reboot after install and did not have the tty1. Installed the nvidia driver and rebooted and did not have the tty1. Then I did the update manager and rebooted and got the tty1. So I went to check what was updated and UM installed nvidia prime.
I used Synaptic to completely remove nvidia prime and rebooted. No tty1. So far so good, its been two days. Will see how long this problem stays away.

Thank you for the suggestion. I tried multiple restarts uninstalling and reinstalling Nvidia Prime and the NVidia Prime applet, but I could not get it fixed from this. I was hoping the solution would work for me, but I can't get it to. If you have anymore insights, please share.