I updated to kernel 5.18.8-artix1-1 and now I can't login. Before I was looking for a solution this morning after my steam mysteriously stopped working, it was skipping system requirements for some reason. If anyone can help me out I'd appreciate it, as of late i've been having a lot of login issues.
When I insert my username and password in the terminal login prompt it say's it's not correct.
Try to login as user root? If you can you can adjust your normal user pw after. If you can't from lighten or sddm try Ctrl + alt + f4 to exit that and try from the terminal.
Yeah that's the first thing I did.
Was this kernal update released on accident? I don't have this upgrade available on my other Artix installation.
i have 5.18.6 so you likely have a gremlins repo enabled in pacman.conf.
You should have a backup of your system made before you update esp with using gremlins repo.
And when i say you i mean YOU specifically more than most people should be making backups of your system before updating because YOU seem to attract errors. Not saying that to be mean but it seems YOU create more wonky messes than most so YOU need those backups most of all.
Even somthing as simple as having a usb drive with a copy of your partitions saved to it before updating your system would be the minimum requirement.
I keep everything backed up. Next time I'll disable gremlins on my next install.
it's disabled by default. you would have had to enable it.
With a USB I can access my OS files, is there a way I can roll back the kernal manually?
FWIW, I'm running 5.18.8 right now. It doesn't make sense to me why the kernel merely updating would have any impact on your user accounts. Something sounds weird here.
Sure. The easiest thing to do is to chroot into the root partition (use artix-chroot) and then install the old kernel again from package cache.
Now that you have a USB, chroot into your system and see the logs.
My choice would be logs from the kernel stored in /var/log/kernel and the user login logs from /var/log/pwdfail, but these log locations are from metalog, so see what choice of files your syslog daemon uses.
Also I don't think its your kernel causing this.