Hi, I've recently decided to try out enabling some autologin functionality in my Artix system, basically following the instructions from this thread in the forums (https://forum.artixlinux.org/index.php/topic,1716.msg11807.html)
The autologging works fine, but right after loggin dmesg spits out some warnings:
[ 7069.830435] elogind[4723]: elogind is already running as PID 1132
This doesn't seem to cause any issues, and I might not even have noticed since I usually use the "quiet" kernel parameter which hides these warnings from taking over your tty.
I found this reddit thread (https://www.reddit.com/r/artixlinux/comments/tanilk/how_do_i_properly_set_up_autologin_with_runit_my/) on the Artix subreddit which details the same problem and the solution for the user seemed to be disabling elogind as a service by with:
# touch /run/runit/service/elogind/down
since dbus apparently already starts elogind when needed, acordding to this following reddit thread (https://www.reddit.com/r/voidlinux/comments/sv6h4z/switch_to_different_tty_elogind_is_already/) on the Void Linux subreddit, but I personally am not a fan of messing with that.
This isn't a huge issue as long as I'm certain it doesn't affect elogind functionality, but even then, I wonder if there's a better way of getting autologin from a tty without getting those dmesg warnings.