Not a single user can log in on my system

[leyvi]

Not technically a kernel issue, but definately a system one:
Checked permissions for login shells, all good.
Nothing in syslog. Started in the middle of my last update: after I locked the screen (I use KDE) I couldn't unlock, and trying to log in from a VT would tell me that the user did not exist (for every single one).
If you're wondering how I got the logs, I used the livecd.
Get this weird thing printed when I open a new tmux pane after chrooting into my system:

[leyvi]

UPDATE:
In rc.log was a whole bunch of errors about different systemd modules missing symbol definitions. Not good.
I use OpenRC, but there are a few services that depend on systemd.
I noticed during my last update that the strip command kept failing at the end of each emerge, something to do with object files not being formatted correctly. Maybe there's a connection? Tried oneshotting all the relevant systemd-related packages, failed due to an undefined symbol named crypt_r.

[Banana]

without any error or log files it is hardly possible to provide you any good solution.

So here is just a wild guess:
Maybe something failed during the last update? Power outage? Disk failure?
It sounds like something is really off.

I think the best way, if possible, to boot from a USB stick and chroot into it.
_________________
Forum Guidelines

PFL - Portage file list - find which package a file or command belongs to.
My delta-labs.org snippets do expire

[leyvi]

As mentioned, I did try chrooting into my system from livecd. I didn't find much. Tried emerge oneshotting some stuff that looked sus. I will use wgetpaste to upload my entire log directory for analysis as soon as I get home.

Should I try updating my @world from inside the chroot?

Also, the one thing I did find in my logs were a lot of errors related to undefined symbols, missing functionality, and during my last update strip kept failing, something about invalid file formats.

[NeddySeagoon]

leyvi,

Has your console keymap got (re)set?

[leyvi]

Thanks for the suggestion, Ned. I'll look into it as soon as I get home.
I don't think that's the issue though. My OS (without the LiveCD) boots fine, with a few systemd-related services failing. When I type any of my usersnames into the login prompt, they come out the way I'd expect (typing "root" yields "root"), just login doesn't like them.

[NeddySeagoon]

leyvi,

Is PAM if you use it, in a mess?

Keymaps cam be quite subtle.
us and gb are very similar, with a few keys swapped. Usernames are OK. Passwords may not be, if you use one or more of the swapped symbols.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[leyvi]

No, I don't use PAM. Perhaps the issue is related to all the errors to do with symbols mentioned previously? You'll definately see them, once I upload the log directory.

Also: if I wgetpaste a tarball, would that be convenient for you guys? I can provide a PGP signature as well, if you like.

[NeddySeagoon]

leyvi,

Play with the -s and -S options to wgetpaste. Different sites have different size limits.
Downloading things makes us all nervous.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[pingtoo]

Try to boot in to single user to example rootfs. May be rootfs was corrupted or bad storage.

[leyvi]

I just got home:
File: /etc/conf.d/keymaps

[leyvi]

[leyvi]

OK, here's the link:
https://0x0.st/8ABy.tar.xz
Let me know if you want a signature or a checksum.

Files included:

• auth.log
  
• dmesg
  
• emerge.log
  
• kern.log
  
• messages
  
• rc.log
  
• sddm.log
  
• syslog