kmscon automatically replaced my linux terminal. That supposed to happen?

[trusktr]

I was in my standard Linux terminal when I ran the kmscon command to start kmscon in tty2.

Now, whenever I restart my computer, kmscon is always present in tty2 (not the other tty's).

Is that supposed to happen? What is kmscon doing to cause that?

[dvdhrm]

Ugh? No, that shouldn't happen. What distribution do you use? Did you install kmscon from git or via an internal package?

If you use systemd, a tty is started via autovt@ttyX.service. kmscon can be symlinked to that, but this definitely shouldn't be the default.

[trusktr]

I'm using Arch Linux with systemd and I installed kmscon from the official Arch repos.

I don't see any autovt@ttyX.service units, but I do see getty@ttyX.service units.

I am able to kill kmscon from another tty, and all returns to normal, and on next boot tty2 is restored to Linux console.

I haven't enabled or started kmscon using systemctl in any way, on by running the kmscon command from tty2 getty.

What other info can I provide to help figure out what's causing this?

[dvdhrm]

This sounds weird. I checked the kmscon PKGBUILD again and everything is fine. If you start kmscon once and you reboot the machine, can you check which process starts kmscon? Or which systemd rule causes kmscon to be started? kmscon doesn't start itself automatically.

Did you make any adjustments other than "pacman -S kmscon" after installing kmscon? Did you follow any guides from the wiki?

[trusktr]

I took a look at my bash history, and I forgot that I did systemctl enable kmscon.service after pacman -S kmscon. This was actually a few months ago, but I was too busy during the school semester so I forget what it was that was fishy.

After disabling kmscon.service, tty2 returns to agetty. Sorry for wasting some of your time on this.