No root sign in or user unlock after update

Hi guys,

After the last update every time I lock the screen (KDE) I can’t unlock, it always says that the password is wrong, even when it’s not, I always checked the capslock key to be sure of that.

The root user also cannot be used for both login or su command, for sign-in it ask again for the login and show the error:
enp1s0:
wlp0s20f3: 192.168.1.90 fe80::3b3e:d27e:7edb:b116
**
From dmseg I can see that new lines after that:
[19786.658066] wlp0s20f3: deauthenticating from f0:9f:c2:34:d5:61 by local choice (Reason: 3=DEAUTH_LEAVING)
[19787.396309] atkbd serio0
: Unknown key pressed (translated set 2, code 0xf6 on isa0060/serio0).**
[19787.396313] atkbd serio0**: Use ‘setkeycodes e076 <keycode>’ to make it known.**
[19787.400504] atkbd serio0**: Unknown key released (translated set 2, code 0xf6 on isa0060/serio0).**
[19787.400507] atkbd serio0**: Use ‘setkeycodes e076 <keycode>’ to make it known.**

When I try to use the su command, that’s what I can see into dmesg:
[19844.812035] su[26153]: segfault at 0 ip 00007f015767edf5 sp 00007fff97d10cc8 error 4 in libc-2.32.so[7f0157540000+14f000]
[19844.812040] Code: 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 2b <c5> fd 74 0f c5 fd d7 c1 85 c0 0f 85 eb 00 00 00 48 83 c7 20 83 e1

Does anyone have any idea what I can do to fix that? Before the last update the S.O. was working fine since I installed almost an year ago.

I’m using a Lenovo ThinkBook 15-IIL.

Thanks in advance.

Aside from suspecting a keyboard settings (locale?) issue,
Are you logging in from a remote machine, eg SSH?
That could complicate what is going on.
Your error containing a network address is unusual if you are logging in directly in front of your machine.

TSU

Hello,

I have the same issue after zypper dup today.


Dez 15 16:36:45 pyxis dbus-daemon[926]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.serv>
Dez 15 16:36:45 pyxis systemd[1]: Starting Fingerprint Authentication Daemon...
Dez 15 16:36:45 pyxis dbus-daemon[926]: [system] Successfully activated service 'net.reactivated.Fprint'
Dez 15 16:36:45 pyxis systemd[1]: Started Fingerprint Authentication Daemon.
Dez 15 16:36:45 pyxis kernel: show_signal_msg: 43 callbacks suppressed
Dez 15 16:36:45 pyxis kernel: login[17928]: segfault at 0 ip 00007fba3f4c6df5 sp 00007ffcc9af35f8 error 4 in libc-2.32.so[7fba3f3>
Dez 15 16:36:45 pyxis kernel: Code: 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f9 48 89 fa c5 >
Dez 15 16:36:45 pyxis systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Dez 15 16:36:45 pyxis systemd[1]: Started Process Core Dump (PID 17934/UID 0).
Dez 15 16:36:45 pyxis systemd-coredump[17935]: Removed old coredump core.login.0.13a4d386fe8041418c7681b5c24b5aef.20491.160804071>
Dez 15 16:36:45 pyxis systemd-coredump[17935]: Process 17928 (login) of user 0 dumped core.
                                               
                                               Stack trace of thread 17928:
                                               #0  0x00007fba3f4c6df5 __strlen_avx2 (libc.so.6 + 0x164df5)
                                               #1  0x00007fba3f3f2573 __strdup (libc.so.6 + 0x90573)
                                               #2  0x00007fba3f595f03 pam_sm_authenticate (pam_fprint.so + 0x2f03)
                                               #3  0x00007fba3f56bcd2 n/a (libpam.so.0 + 0x8cd2)
                                               #4  0x00007fba3f56c479 pam_authenticate (libpam.so.0 + 0x9479)
                                               #5  0x000055c485e4f7a0 n/a (login + 0x47a0)
                                               #6  0x00007fba3f38a152 __libc_start_main (libc.so.6 + 0x28152)
                                               #7  0x000055c485e50dba n/a (login + 0x5dba)
Dez 15 16:36:45 pyxis systemd[1]: getty@tty2.service: Succeeded.
Dez 15 16:36:45 pyxis systemd[1]: systemd-coredump@0-17934-0.service: Succeeded.
Dez 15 16:36:45 pyxis systemd[1]: getty@tty2.service: Scheduled restart job, restart counter is at 1.
Dez 15 16:36:45 pyxis systemd[1]: Stopped Getty on tty2.
Dez 15 16:36:45 pyxis systemd[1]: Started Getty on tty2.

After booting into the snapshot before, everything was working fine.

Thinkpad X270

Thanks for help!

Solved it by removing fprintd … :wink:

You should really open bug report against fprintd in this case.

The fprintd people marked v1.90.6 already as broken.

Tumbleweed should update to v1.90.7 or v1.90.8 soon.

Greetings

No, it’s my personal laptop as localhost, a Lenovo ThinkBook 15-IIL.
All keys are OK and no issue with the network.
I tried to remove and install again libc, or change it to 64, but even Yast can’t be accessed, but it’s weird that I made another update today when I started the laptop, so somehow still working.

How are you updating?? in TW zyppper dup is the only way

At least KDE has an auto update, for some reason all kind of try to use super user or root fails, except that auto update.

And root user is OK, I can use single user, but I can’t change init state, not even to 0, so I can’t use init 3 and try to reinstall libc, or any other package.

something is seriously broken if zypper dup does not work show all input and outputs for zypper lr -d even if errors

You may simply want to rollback your system to a snapshot created prior to when you started having problems

https://doc.opensuse.org/documentation/leap/archive/15.0/reference/html/book.opensuse.reference/cha.snapper.html#sec.snapper.snapshot-boot

Unless you damaged an upgrade, you will want to continue to verify your setup doesn’t include any repos containing packages which can damage your machine.

TSU

Thanks all for the help.

After few months I could finally make it work, at the end I needed:

  • Boot as single user
  • Remove fprintd
  • Remove all fingerprint packages (I had some because none of them is working)
  • zypper refres
  • zypper dup

Now everything is back to normal, but so far I didn’t tried to install the packages I removed again.