You are not logged in.

#1 2022-05-08 14:38:36

mjiricka
Member
Registered: 2017-04-20
Posts: 10

[SOLVED] I cannot log into tty as user after system upgrade

Hello,

after system upgrade few weeks ago I cannot log into neither TTY as regular user on one of my computers. After entering username and password,  this error appears quickly and login screen restarts:

Assertion 'close_nointr(fd) != -EBADF' failed at src/basic/fd-util.c:74, function safe_close(). Aborting.

I had to film the screen with phone to be able to read it. But I can log in as root.

I have no idea where to look, what to check. Googling the error did not tell me much. Does anybody have an idea?

Last edited by mjiricka (2022-05-08 18:48:39)

Offline

#2 2022-05-08 16:15:42

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: [SOLVED] I cannot log into tty as user after system upgrade

Something™ tries to close a file that's not open (or doesn't exist at all/anymore)
Since you can still log in as root
1. check the journal on whether you can get more context on this
2. Your shell rc might be very relevant here => what shell and what does its config files look like?

Online

#3 2022-05-08 17:16:53

mjiricka
Member
Registered: 2017-04-20
Posts: 10

Re: [SOLVED] I cannot log into tty as user after system upgrade

Oh, I forgot to check journal, how could I?

Here is more info for the error:

May 08 19:00:43 desktop systemd-coredump[12179]: [?] Process 12177 (login) of user 1000 dumped core.

                                                Module linux-vdso.so.1 with build-id c44838b6f952044acc4a4965fe03ad60a34a6683
                                                Module libnss_systemd.so.2 with build-id be2c0a0cad78bb62221fff5133304deaf6794edb
                                                Module pam_warn.so with build-id 5b73faf8abe96fd6b460ef6c703cb127fe8e312b
                                                Module pam_deny.so with build-id 023269774049f20683b13e4304d7e254a1c7a0b2
                                                Module pam_systemd.so with build-id 1cd58dea73fdd607bd1bbca17508c61811b94b09
                                                Module pam_mail.so with build-id 2e76a4a0eb21f3217a766329838b850a7085b16b
                                                Module pam_motd.so with build-id f3ed720bd88c652152737c440039dd0b9589174c
                                                Module pam_limits.so with build-id 904f399db1e3e4b168ab6fcd9152c52a52d41d3f
                                                Module pam_keyinit.so with build-id 6bd2a336d004dc8458f1c4cdf8fcd941d1c4925f
                                                Module pam_loginuid.so with build-id 45bcbb167aef0cae946704ce218c4a8f442393ad
                                                Module pam_time.so with build-id 27045c468605f64203a35fa2d83d7c423220c298
                                                Module pam_access.so with build-id 9e188fc5620336bf5919f51c25952325ff4de10e
                                                Module pam_env.so with build-id e28d502d7e4820f936437d20d459e51036d1a243
                                                Module pam_permit.so with build-id 59f4a785cc0a8400f0438321eac923ff96c34bdd
                                                Module libresolv.so.2 with build-id 46ffdf3d477a170314060c26927470d7399bc900
                                                Module libkeyutils.so.1 with build-id ac405ddd17be10ce538da3211415ee50c8f8df79
                                                Module libkrb5support.so.0 with build-id 36db7c21bc57a9b934ad2d3463782db9fef4af07
                                                Module libcom_err.so.2 with build-id 358b783c9b3d12ba8248519ea2e7f3da4c4e0297
                                                Module libk5crypto.so.3 with build-id f1c113fea46023cdf62c7e51cb643c45831abdd5
                                                Module libkrb5.so.3 with build-id 9350783c946d77aec8ee8fd9c6bc12f4f7b72be9
                                                Module libpthread.so.0 with build-id 7fa8b52fae071a370ba4ca32bf9490a30aff31c4
                                                Module libgssapi_krb5.so.2 with build-id 1813217c8baf82a1078772eed0d868310cd59f8b
                                                Module libtirpc.so.3 with build-id 5bef2adfdee3df283f593b3e2d37b6dac405256a
                                                Module libcrypt.so.2 with build-id a0a45f81771945f0559d04e93726d245159930da
                                                Module pam_unix.so with build-id 608e03b3693ba42760a2b836763d41d1c079a2bf
                                                Module libgcc_s.so.1 with build-id 5d817452a709ca3a213341555ddcf446ecee37fa
                                                Module libm.so.6 with build-id 596b63a006a4386dcab30912d2b54a7a61827b07
                                                Module libcap.so.2 with build-id 21b00ab76bb16fde56fd741f07233c78069f0579
                                                Module pam_systemd_home.so with build-id b59c0e5a4c045e314ebaa6b49da9aa94610f60cb
                                                Module pam_faillock.so with build-id 7e42bd70303fbc079e452d777b6907bb5614df5d
                                                Module pam_shells.so with build-id 827b2de32a5ec108462699009e6e441b42792b26
                                                Module pam_nologin.so with build-id 9f749b8e7bd55bfb75e294bc32aaa56ac353d6c0
                                                Module pam_securetty.so with build-id f50f4594f4bc962c6e9b8d75b3219dfb610f27d1
                                                Module libcap-ng.so.0 with build-id 707f9d3134a43306625e3dab8662899ea368ac91
                                                Module ld-linux-x86-64.so.2 with build-id c09c6f50f6bcec73c64a0b4be77eadb8f7202410
                                                Module libdl.so.2 with build-id bb9bd2657bfba9f60bd34d2050cc63a7eb024bc4
                                                Module libaudit.so.1 with build-id 53c797475ffeed05918d78f49f85dbf4127fb174
                                                Module libc.so.6 with build-id 85766e9d8458b16e9c7ce6e07c712c02b8471dbc
                                                Module libpam_misc.so.0 with build-id 74aaf2951cb6eb6cf89a69339285a6015876bee4
                                                Module libpam.so.0 with build-id bb11b2685fe89555938ffd330ea44d82b0f8701c
                                                Module login with build-id cf05f4e8b1b90fcc6fefe422748d91003165b80a
                                                Stack trace of thread 12177:
                                                #0  0x00007fa526b0f34c __pthread_kill_implementation (libc.so.6 + 0x8f34c)
                                                #1  0x00007fa526ac24b8 raise (libc.so.6 + 0x424b8)
                                                #2  0x00007fa526aac534 abort (libc.so.6 + 0x2c534)
                                                #3  0x00007fa526a025a8 n/a (pam_systemd_home.so + 0x2b5a8)
                                                #4  0x00007fa526a02dbf n/a (pam_systemd_home.so + 0x2bdbf)
                                                #5  0x00007fa5269f43d0 n/a (pam_systemd_home.so + 0x1d3d0)
                                                #6  0x00007fa5269f89cb n/a (pam_systemd_home.so + 0x219cb)
                                                #7  0x00007fa526c9247c n/a (libpam.so.0 + 0x347c)
                                                #8  0x00007fa526c92fe2 pam_end (libpam.so.0 + 0x3fe2)
                                                #9  0x0000564976ac8061 n/a (login + 0x5061)
                                                #10 0x00007fa526aad310 __libc_start_call_main (libc.so.6 + 0x2d310)
                                                #11 0x00007fa526aad3c1 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2d3c1)
                                                #12 0x0000564976ac8ad5 n/a (login + 0x5ad5)
                                                ELF object binary architecture: AMD x86-64

Btw, it should not be anything shell related, I can sudo to my user after login on root or SSH on my user directly.

Offline

#4 2022-05-08 18:01:35

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: [SOLVED] I cannot log into tty as user after system upgrade

Online

#5 2022-05-08 18:17:15

mjiricka
Member
Registered: 2017-04-20
Posts: 10

Re: [SOLVED] I cannot log into tty as user after system upgrade

And also these two:

May 08 19:49:36 desktop sshd[883]: pam_systemd_home(sshd:auth): Not a user managed by systemd-homed: No home for user martin known
May 08 19:49:36 desktop sshd[883]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=10.0.0.13  user=martin
May 08 19:49:43 desktop sshd[883]: pam_systemd(sshd:session): Failed to get user record: Input/output error
May 08 19:49:43 desktop sshd[883]: pam_env(sshd:session): deprecated reading of user environment enabled

I guess it would be something with PAM or systemd-homed. It is very old Arch installation. Maybe it is time to do a fresh installation...

Offline

#6 2022-05-08 18:31:31

mjiricka
Member
Registered: 2017-04-20
Posts: 10

Re: [SOLVED] I cannot log into tty as user after system upgrade

Oh, I missed this one, thank you!!

Yes, commenting all lines containing "pam_systemd_home.so" in /etc/pam.d/system-auth solved the problem!

Thank you once again!

Last edited by mjiricka (2022-05-08 18:45:11)

Offline

#7 2022-05-08 19:24:11

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: [SOLVED] I cannot log into tty as user after system upgrade

"martin" doesn't sound weird, though - does the user lack a valid $HOME or are there other things (permissions) "off" about it?

Online

#8 2022-05-09 06:53:08

mjiricka
Member
Registered: 2017-04-20
Posts: 10

Re: [SOLVED] I cannot log into tty as user after system upgrade

I don't know, it is standard user, created many years ago. I will have to learn more about PAM and systemd-homed. On my other Arch computer, where everything is working without problem, I found this:

May 09 08:40:38 laptop systemd[757]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.

So I guess systemd-homed contains some bug? I will have to read more about it and then I will try to inspect the problem a little bit more.

Offline

#9 2022-05-09 07:00:35

seth
Member
Registered: 2012-09-03
Posts: 28,839

Re: [SOLVED] I cannot log into tty as user after system upgrade

The other message is "normal" (by systemd standards) and yes: the recent pam failures are for sure a regression in lennarts disfuncitonal solution in search for *some* problem.

grep martin /etc/passwd # don't worry - there're no passwords in that file
stat ~martin

Online

Board footer

Powered by FluxBB