You are not logged in.

#1 2020-10-05 19:10:01

ErdosOrGauss
Member
Registered: 2017-06-21
Posts: 40

login screen loop after update

Hi,

I am having an issue logging into Arch after updating. I am aware there is a reported bug with the tally module or faillock config, but these don't apply/work for me.

Specifically, I was, at first, having the same issue listed here. However, after commenting out the lines including "tally," I then started having a different issue.

That is, I keep getting stuck at the login screen. Whenever I enter my password, it doesn't do anything but reload the login screen.

I am aware of a similar issue here, but the actual issue is different and the fix doesn't apply.

Furthermore, my output for

journalctl -p 3 -xb

Only produces the output

[sdb] No Caching mode page found
[sdb] Assuming drive cache: write through

which, to my understanding, isn't actually an error (as sdb is a USB).

Maybe I'm not able to find a post that applies? Any help/recommendations would be appreciated.

Last edited by ErdosOrGauss (2020-10-05 22:54:20)

Offline

#2 2020-10-05 19:15:11

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: login screen loop after update

Are you trying to login into the console or something else?  What is the output from the journal from a failed login without filtering for priority or including catalogue messages i.e no -p 3 or-x.
What is the contents of any files in /etc/pam.d you have modified?  What caused the issue to start happening?  Is the system fully updated?

Offline

#3 2020-10-05 19:36:51

ErdosOrGauss
Member
Registered: 2017-06-21
Posts: 40

Re: login screen loop after update

loqs wrote:

Are you trying to login into the console or something else?

I believe I am trying to login to the console. I only use i3, so no real desktop environment.

loqs wrote:

What is the output from the journal from a failed login without filtering for priority or including catalogue messages i.e no -p 3 or-x.

I am not exactly sure how to find the exact output from a failed login attempt in my journal.

However, the "error" itself is that it just redirects me to the login screen.


loqs wrote:

What is the contents of any files in /etc/pam.d you have modified?

 

#auth required pam_tally2.so onerr=succeed file=var/log/tallylog
auth required pam_shells.so
auth requisit pam_nologin.so
auth include system-auth

#account require pam_tally2.so
acount required pam_access.so
account required pam_nologin.so
account include system-auth

password include system-auth

session optional pam_loginuid.so
session optional pam_keyinit.so       force revoke
session include system-auth
session optional pam_motd.so         motd=/etc/motd
session optional pam_mail.so          dir=/var/spool/mail standard quiet
-session optional pam_systemd.so
session required pam_env.so
 
loqs wrote:

What caused the issue to start happening?

After I used

pacman -Syu 

I started receiving the error caused by "tally" but then after fixing that bug, I started receiving this one.

loq wrote:

Is the system fully updated?

Yes, I believe so.

Last edited by ErdosOrGauss (2020-10-05 20:41:22)

Offline

#4 2020-10-05 19:37:43

euromatlox
Member
Registered: 2017-02-10
Posts: 153

Re: login screen loop after update

If graphical target, I would switch to multiuser target (at least while examining the problem). You should be able to do that (if not possible normal way) using live cd (or usb drive) and commands like in this bbs post or in Wiki. If you lost root password, read this Wiki page.

Last edited by euromatlox (2020-10-05 19:42:11)

Offline

#5 2020-10-05 19:42:12

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: login screen loop after update

Please post the full unfiltered journal from a boot with the issue.  See the tip box from pastebin to pipe the output directly to a pastebin if it will not fit in code tags.

Offline

#6 2020-10-05 21:12:14

ErdosOrGauss
Member
Registered: 2017-06-21
Posts: 40

Re: login screen loop after update

euromatlox wrote:

If graphical target, I would switch to multiuser target (at least while examining the problem). You should be able to do that (if not possible normal way) using live cd (or usb drive) and commands like in this bbs post or in Wiki. If you lost root password, read this Wiki page.

***EDITED***

Sorry, after poking through the first link you posted, I decided to check. It indeed does have the default set to graphical.target. However, when I changed it, it didn't do anything to the error.

Concerning the lost root password possibility, this doesn't seem to be the issue.

Thanks!


loqs wrote:

Please post the full unfiltered journal from a boot with the issue.  See the tip box from pastebin to pipe the output directly to a pastebin if it will not fit in code tags.

I have done as you said concerning the pastebin. Here is my journal output. Though I think that it may be a bit much. I did find, however, something that may be useful. If you ctrl+f "session closed for user max", you will find what I'm talking about. This seems to be the login and then it is immediately killed by pam_unix. I am going to investigate there.

loqs wrote:

What is the contents of any files in /etc/pam.d you have modified?

I have updated the original reply and also included it here, for convenience.

#auth required pam_tally2.so onerr=succeed file=var/log/tallylog
auth required pam_shells.so
auth requisit pam_nologin.so
auth include system-auth

#account require pam_tally2.so
acount required pam_access.so
account required pam_nologin.so
account include system-auth

password include system-auth

session optional pam_loginuid.so
session optional pam_keyinit.so       force revoke
session include system-auth
session optional pam_motd.so         motd=/etc/motd
session optional pam_mail.so          dir=/var/spool/mail standard quiet
-session optional pam_systemd.so
session required pam_env.so
 

Last edited by ErdosOrGauss (2020-10-05 21:26:52)

Offline

#7 2020-10-05 21:37:09

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: login screen loop after update

Oct 05 13:21:58 Gauss login[437]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost=  user=max
Oct 05 13:21:58 Gauss dbus-daemon[412]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.14' (uid=0 pid=437 comm="/bin/login -p --     ")
Oct 05 13:21:58 Gauss dbus-daemon[412]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 05 13:21:58 Gauss login[437]: pam_systemd_home(login:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 05 13:21:58 Gauss audit[437]: USER_AUTH pid=437 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="max" exe="/usr/bin/login" hostname=Gauss addr=? terminal=tty1 res=failed'
Oct 05 13:21:58 Gauss kernel: kauditd_printk_skb: 17 callbacks suppressed
Oct 05 13:21:58 Gauss kernel: audit: type=1100 audit(1601925718.231:28): pid=437 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="max" exe="/usr/bin/login" hostname=Gauss addr=? terminal=tty1 res=failed'
Oct 05 13:22:00 Gauss login[437]: FAILED LOGIN SESSION FROM tty1 FOR max, Permission denied
Oct 05 13:22:03 Gauss systemd[1]: getty@tty1.service: Succeeded.
Oct 05 13:22:03 Gauss audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:03 Gauss kernel: audit: type=1131 audit(1601925723.561:29): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:03 Gauss kernel: audit: type=1130 audit(1601925723.581:30): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:03 Gauss kernel: audit: type=1131 audit(1601925723.581:31): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:03 Gauss kernel: audit: type=1130 audit(1601925723.581:32): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:03 Gauss audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:03 Gauss audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:03 Gauss audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:03 Gauss systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
Oct 05 13:22:03 Gauss systemd[1]: Stopped Getty on tty1.

Permission denied on first attempt.

Oct 05 13:22:03 Gauss systemd[1]: Started Getty on tty1.
Oct 05 13:22:07 Gauss audit[449]: USER_AUTH pid=449 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="max" exe="/usr/bin/login" hostname=Gauss addr=? terminal=tty1 res=success'
Oct 05 13:22:07 Gauss kernel: audit: type=1100 audit(1601925727.601:33): pid=449 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="max" exe="/usr/bin/login" hostname=Gauss addr=? terminal=tty1 res=success'
Oct 05 13:22:07 Gauss dbus-daemon[412]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.15' (uid=0 pid=449 comm="/bin/login -p --     ")
Oct 05 13:22:07 Gauss dbus-daemon[412]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 05 13:22:07 Gauss login[449]: pam_systemd_home(login:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 05 13:22:07 Gauss audit[449]: USER_ACCT pid=449 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct="max" exe="/usr/bin/login" hostname=Gauss addr=? terminal=tty1 res=success'
Oct 05 13:22:07 Gauss kernel: audit: type=1101 audit(1601925727.664:34): pid=449 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct="max" exe="/usr/bin/login" hostname=Gauss addr=? terminal=tty1 res=success'
Oct 05 13:22:07 Gauss kernel: audit: type=1103 audit(1601925727.664:35): pid=449 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="max" exe="/usr/bin/login" hostname=Gauss addr=? terminal=tty1 res=success'
Oct 05 13:22:07 Gauss kernel: audit: type=1006 audit(1601925727.668:36): pid=449 uid=0 old-auid=4294967295 auid=1000 tty=tty1 old-ses=4294967295 ses=1 res=1
Oct 05 13:22:07 Gauss audit[449]: CRED_ACQ pid=449 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="max" exe="/usr/bin/login" hostname=Gauss addr=? terminal=tty1 res=success'
Oct 05 13:22:07 Gauss login[449]: pam_unix(login:session): session opened for user max(uid=1000) by LOGIN(uid=0)
Oct 05 13:22:07 Gauss systemd[1]: Created slice User Slice of UID 1000.
Oct 05 13:22:07 Gauss systemd[1]: Starting User Runtime Directory /run/user/1000...
Oct 05 13:22:07 Gauss systemd-logind[415]: New session 1 of user max.
Oct 05 13:22:07 Gauss systemd[1]: Finished User Runtime Directory /run/user/1000.
Oct 05 13:22:07 Gauss audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:07 Gauss systemd[1]: Starting User Manager for UID 1000...
Oct 05 13:22:07 Gauss kernel: audit: type=1130 audit(1601925727.691:37): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:07 Gauss dbus-daemon[412]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.17' (uid=0 pid=451 comm="(systemd) ")
Oct 05 13:22:07 Gauss dbus-daemon[412]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Oct 05 13:22:07 Gauss systemd[451]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 05 13:22:07 Gauss audit[451]: USER_ACCT pid=451 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct="max" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:07 Gauss audit[451]: CRED_ACQ pid=451 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="max" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Oct 05 13:22:07 Gauss systemd[451]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[max] ruser=[<unknown>] rhost=[<unknown>]
Oct 05 13:22:07 Gauss systemd[451]: pam_unix(systemd-user:session): session opened for user max(uid=1000) by (uid=0)
Oct 05 13:22:07 Gauss audit[451]: USER_START pid=451 uid=0 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="max" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:07 Gauss kernel: audit: type=1101 audit(1601925727.698:38): pid=451 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_permit,pam_time acct="max" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:07 Gauss audit: BPF prog-id=9 op=LOAD
Oct 05 13:22:07 Gauss audit: BPF prog-id=9 op=UNLOAD
Oct 05 13:22:07 Gauss systemd[456]: Exec binary '/usr/lib/at-spi-bus-launcher' does not exist: No such file or directory
Oct 05 13:22:07 Gauss systemd[456]: Not generating service for XDG autostart app-at\x2dspi\x2ddbus\x2dbus-autostart.service, error parsing Exec= line: No such file or directory
Oct 05 13:22:07 Gauss systemd[456]: Exec binary 'start-pulseaudio-x11' does not exist: No such file or directory
Oct 05 13:22:07 Gauss systemd[456]: Not generating service for XDG autostart app-pulseaudio-autostart.service, error parsing Exec= line: No such file or directory
Oct 05 13:22:07 Gauss systemd[451]: Queued start job for default target Main User Target.
Oct 05 13:22:07 Gauss systemd[451]: Reached target Paths.
Oct 05 13:22:07 Gauss systemd[451]: Reached target Timers.
Oct 05 13:22:07 Gauss systemd[451]: Starting D-Bus User Message Bus Socket.
Oct 05 13:22:07 Gauss systemd[451]: Listening on GnuPG network certificate management daemon.
Oct 05 13:22:07 Gauss systemd[451]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct 05 13:22:07 Gauss systemd[451]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Oct 05 13:22:07 Gauss systemd[451]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Oct 05 13:22:07 Gauss systemd[451]: Listening on GnuPG cryptographic agent and passphrase cache.
Oct 05 13:22:07 Gauss systemd[451]: Listening on p11-kit server.
Oct 05 13:22:07 Gauss systemd[451]: Listening on D-Bus User Message Bus Socket.
Oct 05 13:22:07 Gauss systemd[451]: Reached target Sockets.
Oct 05 13:22:07 Gauss systemd[451]: Reached target Basic System.
Oct 05 13:22:07 Gauss systemd[451]: Reached target Main User Target.
Oct 05 13:22:07 Gauss systemd[451]: Startup finished in 76ms.
Oct 05 13:22:07 Gauss systemd[1]: Started User Manager for UID 1000.
Oct 05 13:22:07 Gauss audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@1000 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 05 13:22:07 Gauss systemd[1]: Started Session 1 of user max.
Oct 05 13:22:07 Gauss audit[449]: USER_START pid=449 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="max" exe="/usr/bin/login" hostname=Gauss addr=? terminal=tty1 res=success'
Oct 05 13:22:07 Gauss audit[449]: CRED_REFR pid=449 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="max" exe="/usr/bin/login" hostname=Gauss addr=? terminal=tty1 res=success'
Oct 05 13:22:07 Gauss login[449]: LOGIN ON tty1 BY max
Oct 05 13:22:07 Gauss audit[449]: CRED_DISP pid=449 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="max" exe="/usr/bin/login" hostname=Gauss addr=? terminal=tty1 res=success'
Oct 05 13:22:07 Gauss login[449]: pam_unix(login:session): session closed for user max
Oct 05 13:22:07 Gauss audit[449]: USER_END pid=449 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct="max" exe="/usr/bin/login" hostname=Gauss addr=? terminal=tty1 res=success'

Session closed on the second.

Can you login as root?

Offline

#8 2020-10-05 21:46:59

ErdosOrGauss
Member
Registered: 2017-06-21
Posts: 40

Re: login screen loop after update

loqs wrote:

Can you login as root?

No. Here is the journal output. I first tried my user, then root a few times. From what I can tell, the permission was denied. Could this be linked to the same issue I referenced in the beginning?

Offline

#9 2020-10-05 21:59:53

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: login screen loop after update

What is the output of the following:

# pacman -Qkk $(pacman -Qoq /etc/pam.d)
pacman -Qi pam

To rule out the password either create a new user with a simple password or set a new password for an existing user.

Offline

#10 2020-10-05 22:09:36

ErdosOrGauss
Member
Registered: 2017-06-21
Posts: 40

Re: login screen loop after update

I have entered the output of the commands below (entered in the order they appear).

pacman -Qkk $(pacman -Qoq /etc/pam.d)

The output for this one is long, I have uploaded it here.

pacman -Qi pam

The output is as follows:

Name            : pam
Version         : 1.4.0-3
Description     : PAM (Pluggable Authentication Modules) library
Architecture    : x86_64
URL             : http://linux-pam.org
Licenses        : GPL2
Groups          : None
Provides        : None
Depends On      : glibc  libtirpc  pambase  audit
Optional Deps   : None
Required By     : i3lock  kbd  shadow  sudo  systemd  util-linux
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 2.77 MiB
Packager        : Tobias Powalowski <tpowa@archlinux.org>
Build Date      : Wed Aug 12 13:29:38 2020
Install Date    : Mon Oct  5 12:02:49 2020
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature 



To rule out the password either create a new user with a simple password or set a new password for an existing user.

I have done ask you asked. The result is the same.

Offline

#11 2020-10-05 22:29:51

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: login screen loop after update

If the pacman update that caused the issue contained pam-1.4.0-3 and pambase to pambase 20200721.1-2,  check /var/log/pacman.log.  What if you downgrade to pam-1.3.1-2 and pambase-20190105.1-2?

Offline

#12 2020-10-05 22:41:06

ErdosOrGauss
Member
Registered: 2017-06-21
Posts: 40

Re: login screen loop after update

loqs wrote:

If the pacman update that caused the issue contained pam-1.4.0-3 and pambase to pambase 20200721.1-2,  check /var/log/pacman.log.  What if you downgrade to pam-1.3.1-2 and pambase-20190105.1-2?

I did as you asked and the result is the same.

Last edited by ErdosOrGauss (2020-10-05 22:41:28)

Offline

#13 2020-10-05 22:45:09

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: login screen loop after update

That rules out the issues you linked to in your first post.
What was in the pacman update that caused the issue?  Please post the contents of var/log/pacman.log from that update onward or the whole file.
Also the contents of /etc/pam.d/system-auth and /etc/pam.d/system-login now.

Last edited by loqs (2020-10-05 22:45:27)

Offline

#14 2020-10-05 22:51:36

ErdosOrGauss
Member
Registered: 2017-06-21
Posts: 40

Re: login screen loop after update

loqs wrote:

What was in the pacman update that caused the issue?  Please post the contents of var/log/pacman.log from that update onward or the whole file.

Here is the output. I am not sure what could've caused the issue.

/etc/pam.d/system-auth

#%PAM-1.0

auth      required  pam_unix.so     try_first_pass nullok
auth      optional  pam_permit.so
auth      required  pam_env.so

account   required  pam_unix.so
account   optional  pam_permit.so
account   required  pam_time.so

password  required  pam_unix.so     try_first_pass nullok sha512 shadow
password  optional  pam_permit.so

session   required  pam_limits.so
session   required  pam_unix.so
session   optional  pam_permit.so

/etc/pam.d/system-login now.

#%PAM-1.0

#auth       required   pam_tally2.so        onerr=succeed file=/var/log/tallylog
auth       required   pam_shells.so
auth       requisite  pam_nologin.so
auth       include    system-auth

#account    required   pam_tally2.so 
account    required   pam_access.so
account    required   pam_nologin.so
account    include    system-auth

password   include    system-auth

session    optional   pam_loginuid.so
session    optional   pam_keyinit.so       force revoke
session    include    system-auth
session    optional   pam_motd.so          motd=/etc/motd
session    optional   pam_mail.so          dir=/var/spool/mail standard quiet
-session   optional   pam_systemd.so
session    required   pam_env.so
#auth optional pam_faildelay.so delay=5000000
#auth required pam_tall2.so deny=10 unlock_time=600 onerr=succeed file=/var/log/tallylog

Last edited by ErdosOrGauss (2020-10-05 22:55:36)

Offline

#15 2020-10-05 23:06:31

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: login screen loop after update

Some of pacman.log seems to be missing.  Does the system have a separate /var partition?

Offline

#16 2020-10-05 23:16:17

ErdosOrGauss
Member
Registered: 2017-06-21
Posts: 40

Re: login screen loop after update

loqs wrote:

Some of pacman.log seems to be missing.  Does the system have a separate /var partition?

It does not. That seems to be all there is, although I agree it is definitely weird.

I hate to be fatalistic, but is it seeming as if I should just do a fresh install?

Offline

#17 2020-10-05 23:31:20

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: login screen loop after update

I would you backup your data if you do not have one already.  A few things to try before resorting to re-installation:
I would suggest running a S.M.A.R.T. self test.  After it has completed post the output of

# smartctl -a /dev/<device>

Run an fsck on all the filesystems.
Post the output of:

# pacman -Qkk 2>&1 | grep -Fv '0 altered files'

Last edited by loqs (2020-10-05 23:31:50)

Offline

#18 2020-10-05 23:50:38

ErdosOrGauss
Member
Registered: 2017-06-21
Posts: 40

Re: login screen loop after update

loqs wrote:

I would you backup your data if you do not have one already.

I do have a backup. So, it wouldn't be the worst thing.



After it has completed post the output of

# smartctl -a /dev/<device>

Here is the output.

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.8.12-arch1-1] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       INTEL SSDPEKKF256G8L
Serial Number:                      PHHP935502DF256B
Firmware Version:                   L12P
PCI Vendor/Subsystem ID:            0x8086
IEEE OUI Identifier:                0x5cd2e4
Controller ID:                      1
Number of Namespaces:               1
Namespace 1 Size/Capacity:          256,060,514,304 [256 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            5cd2e4 2991408c4e
Local Time is:                      Mon Oct  5 17:38:51 2020 MDT
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Maximum Data Transfer Size:         64 Pages
Warning  Comp. Temp. Threshold:     75 Celsius
Critical Comp. Temp. Threshold:     80 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     9.00W       -        -    0  0  0  0        0       0
 1 +     4.60W       -        -    1  1  1  1        0       0
 2 +     3.80W       -        -    2  2  2  2        0       0
 3 -   0.0450W       -        -    3  3  3  3     2000    2000
 4 -   0.0040W       -        -    4  4  4  4     6000    8000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        27 Celsius
Available Spare:                    100%
Available Spare Threshold:          12%
Percentage Used:                    0%
Data Units Read:                    1,827,417 [935 GB]
Data Units Written:                 1,276,867 [653 GB]
Host Read Commands:                 11,869,048
Host Write Commands:                21,005,391
Controller Busy Time:               333
Power Cycles:                       642
Power On Hours:                     184
Unsafe Shutdowns:                   112
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0

Error Information (NVMe Log 0x01, max 256 entries)
No Errors Logged

Run an fsck on all the filesystems.
Post the output of:

# pacman -Qkk 2>&1 | grep -Fv '0 altered files'

Here is the output. It is also uploaded here.

warning: ca-certificates-utils: /etc/ssl/cert.pem (Modification time mismatch)
warning: ca-certificates-utils: /etc/ssl/certs/ca-certificates.crt (Modification time mismatch)
warning: dhcpcd: /var/lib/dhcpcd (UID mismatch)
warning: dhcpcd: /var/lib/dhcpcd (GID mismatch)
warning: dhcpcd: /var/lib/dhcpcd (Permissions mismatch)
warning: e2fsprogs: /etc/e2scrub.conf (Modification time mismatch)
warning: filesystem: /bin (Modification time mismatch)
warning: filesystem: /lib (Modification time mismatch)
warning: filesystem: /lib64 (Modification time mismatch)
warning: filesystem: /sbin (Modification time mismatch)
warning: filesystem: /etc/arch-release (Modification time mismatch)
warning: filesystem: /etc/mtab (Modification time mismatch)
warning: filesystem: /etc/resolv.conf (UID mismatch)
warning: filesystem: /etc/resolv.conf (GID mismatch)
warning: filesystem: /etc/profile.d/locale.sh (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/05-reset-dirs-sample.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/05-reset-dirs-sample.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/09-autohint-if-no-hinting.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/09-autohint-if-no-hinting.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-autohint.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-autohint.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-hinting-full.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-hinting-full.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-hinting-medium.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-hinting-medium.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-hinting-none.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-hinting-none.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-hinting-slight.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-hinting-slight.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-no-sub-pixel.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-no-sub-pixel.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-scale-bitmap-fonts.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-scale-bitmap-fonts.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-sub-pixel-bgr.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-sub-pixel-bgr.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-sub-pixel-rgb.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-sub-pixel-rgb.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-sub-pixel-vbgr.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-sub-pixel-vbgr.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-sub-pixel-vrgb.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-sub-pixel-vrgb.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-unhinted.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/10-unhinted.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/11-lcdfilter-default.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/11-lcdfilter-default.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/11-lcdfilter-legacy.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/11-lcdfilter-legacy.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/11-lcdfilter-light.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/11-lcdfilter-light.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/20-unhint-small-vera.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/20-unhint-small-vera.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/25-unhint-nonlatin.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/25-unhint-nonlatin.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/30-metric-aliases.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/30-metric-aliases.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/35-lang-normalize.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/35-lang-normalize.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/40-nonlatin.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/40-nonlatin.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/45-generic.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/45-generic.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/45-latin.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/45-latin.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/49-sansserif.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/49-sansserif.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/50-user.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/50-user.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/51-local.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/51-local.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/60-generic.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/60-generic.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/60-latin.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/60-latin.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/65-fonts-persian.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/65-fonts-persian.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/65-khmer.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/65-khmer.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/65-nonlatin.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/65-nonlatin.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/69-unifont.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/69-unifont.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/70-no-bitmaps.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/70-no-bitmaps.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/70-yes-bitmaps.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/70-yes-bitmaps.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/80-delicious.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/80-delicious.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.avail/90-synthetic.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.avail/90-synthetic.conf (Size mismatch)
warning: fontconfig: /etc/fonts/conf.d/10-hinting-slight.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/10-scale-bitmap-fonts.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/20-unhint-small-vera.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/30-metric-aliases.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/40-nonlatin.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/45-generic.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/45-latin.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/49-sansserif.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/50-user.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/51-local.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/60-generic.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/60-latin.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/65-fonts-persian.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/65-nonlatin.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/69-unifont.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/80-delicious.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/90-synthetic.conf (Modification time mismatch)
warning: fontconfig: /etc/fonts/conf.d/README (Modification time mismatch)
backup file: bash: /etc/bash.bash_logout (Modification time mismatch)
backup file: bash: /etc/bash.bashrc (Modification time mismatch)
backup file: bash: /etc/skel/.bash_logout (Modification time mismatch)
backup file: bash: /etc/skel/.bash_profile (Modification time mismatch)
backup file: bash: /etc/skel/.bashrc (Modification time mismatch)
ca-certificates-utils: 26 total files, 2 altered files
backup file: dhcpcd: /etc/dhcpcd.conf (Modification time mismatch)
backup file: dhcpcd: /etc/dhcpcd.conf (Size mismatch)
dhcpcd: 40 total files, 1 altered file
backup file: e2fsprogs: /etc/mke2fs.conf (Modification time mismatch)
e2fsprogs: 202 total files, 1 altered file
backup file: filesystem: /etc/crypttab (Modification time mismatch)
backup file: filesystem: /etc/fstab (Modification time mismatch)
backup file: filesystem: /etc/fstab (Size mismatch)
backup file: filesystem: /etc/group (Modification time mismatch)
backup file: filesystem: /etc/group (Size mismatch)
backup file: filesystem: /etc/gshadow (Modification time mismatch)
backup file: filesystem: /etc/gshadow (Size mismatch)
backup file: filesystem: /etc/host.conf (Modification time mismatch)
backup file: filesystem: /etc/hosts (Modification time mismatch)
backup file: filesystem: /etc/hosts (Size mismatch)
backup file: filesystem: /etc/issue (Modification time mismatch)
backup file: filesystem: /etc/ld.so.conf (Modification time mismatch)
backup file: filesystem: /etc/motd (Modification time mismatch)
backup file: filesystem: /etc/nsswitch.conf (Modification time mismatch)
backup file: filesystem: /etc/nsswitch.conf (Size mismatch)
backup file: filesystem: /etc/passwd (Modification time mismatch)
backup file: filesystem: /etc/passwd (Size mismatch)
backup file: filesystem: /etc/profile (Modification time mismatch)
backup file: filesystem: /etc/profile (Size mismatch)
backup file: filesystem: /etc/resolv.conf (Modification time mismatch)
backup file: filesystem: /etc/resolv.conf (Size mismatch)
backup file: filesystem: /etc/securetty (Modification time mismatch)
backup file: filesystem: /etc/shadow (Modification time mismatch)
backup file: filesystem: /etc/shadow (Size mismatch)
backup file: filesystem: /etc/shells (Modification time mismatch)
backup file: filesystem: /etc/shells (Size mismatch)
filesystem: 118 total files, 8 altered files
backup file: fontconfig: /etc/fonts/fonts.conf (Modification time mismatch)
backup file: fontconfig: /etc/fonts/fonts.conf (Size mismatch)
fontconfig: 118 total files, 55 altered files
freetype2: 68 totalwarning: glibc: /etc/rpc (Modification time mismatch)
warning: i3-gaps: /etc/i3/config.keycodes (Modification time mismatch)
warning: iproute2: /etc/iproute2/bpf_pinning (Modification time mismatch)
warning: iproute2: /etc/iproute2/group (Modification time mismatch)
warning: iproute2: /etc/iproute2/nl_protos (Modification time mismatch)
warning: iptables: /etc/iptables/empty.rules (Modification time mismatch)
warning: iptables: /etc/iptables/simple_firewall.rules (Modification time mismatch)
warning: iputils: /etc/xinetd.d/tftp (Modification time mismatch)
warning: iputils: /etc/xinetd.d/tftp (Size mismatch)
backup file: glibc: /etc/gai.conf (Modification time mismatch)
backup file: glibc: /etc/locale.gen (Modification time mismatch)
backup file: glibc: /etc/locale.gen (Size mismatch)
backup file: glibc: /etc/nscd.conf (Modification time mismatch)
glibc: 1571 total files, 1 altered file
backup file: grub: /etc/default/grub (Modification time mismatch)
backup file: grub: /etc/default/grub (Size mismatch)
backup file: grub: /etc/grub.d/40_custom (Modification time mismatch)
backup file: grub: /etc/grub.d/40_custom (Size mismatch)
backup file: i3-gaps: /etc/i3/config (Modification time mismatch)
i3-gaps: 60 total files, 1 altered file
backup file: i3lock: /etc/pam.d/i3lock (Modification time mismatch)
backup file: i3status: /etc/i3status.conf (Modification time mismatch)
backup file: iana-etc: /etc/protocols (Modification time mismatch)
backup file: iana-etc: /etc/services (Modification time mismatch)
backup file: iana-etc: /etc/services (Size mismatch)
backup file: iproute2: /etc/iproute2/ematch_map (Modification time mismatch)
backup file: iproute2: /etc/iproute2/rt_dsfield (Modification time mismatch)
backup file: iproute2: /etc/iproute2/rt_protos (Modification time mismatch)
backup file: iproute2: /etc/iproute2/rt_realms (Modification time mismatch)
backup file: iproute2: /etc/iproute2/rt_scopes (Modification time mismatch)
backup file: iproute2: /etc/iproute2/rt_tables (Modification time mismatch)
iproute2: 185 total files, 3 altered files
backup file: iptables: /etc/ethertypes (Modification time mismatch)
backup file: iptables: /etc/iptables/ip6tables.rules (Modification time mismatch)
backup file: iptables: /etc/iptables/ip6tables.rules (Size mismatch)
backup file: iptables: /etc/iptables/iptables.rules (Modification time mismatch)
backup file: iptables: /etc/iptables/iptables.rules (Size mismatch)
iptables: 257 total files, 2 altered files
iputils: 52 total files, 1 altered file
backup file: keyutils: /etc/request-key.conf (Modification time mismatch)
backup file: krb5: /etc/krb5.conf (Modification time mismatch)
backup file: libldap: /etc/openldap/ldap.conf (Modification time mismatch)
backup fwarning: linux: /usr/lib/modules/5.8.13-arch1-1/modules.alias (Modification time mismatch)
warning: linux: /usr/lib/modules/5.8.13-arch1-1/modules.alias.bin (Modification time mismatch)
warning: linux: /usr/lib/modules/5.8.13-arch1-1/modules.builtin.alias.bin (Modification time mismatch)
warning: linux: /usr/lib/modules/5.8.13-arch1-1/modules.builtin.bin (Modification time mismatch)
warning: linux: /usr/lib/modules/5.8.13-arch1-1/modules.dep (Modification time mismatch)
warning: linux: /usr/lib/modules/5.8.13-arch1-1/modules.dep.bin (Modification time mismatch)
warning: linux: /usr/lib/modules/5.8.13-arch1-1/modules.devname (Modification time mismatch)
warning: linux: /usr/lib/modules/5.8.13-arch1-1/modules.softdep (Modification time mismatch)
warning: linux: /usr/lib/modules/5.8.13-arch1-1/modules.symbols (Modification time mismatch)
warning: linux: /usr/lib/modules/5.8.13-arch1-1/modules.symbols.bin (Modification time mismatch)
warning: openssl: /etc/ssl/ct_log_list.cnf (Modification time mismatch)
warning: openssl: /etc/ssl/ct_log_list.cnf.dist (Modification time mismatch)
warning: openssl: /etc/ssl/openssl.cnf.dist (Modification time mismatch)
warning: openssl: /etc/ssl/misc/CA.pl (Modification time mismatch)
warning: openssl: /etc/ssl/misc/tsget (Modification time mismatch)
warning: openssl: /etc/ssl/misc/tsget.pl (Modification time mismatch)
warning: p11-kit: /etc/pkcs11/pkcs11.conf.example (Modification time mismatch)
warning: perl: /etc/profile.d/perlbin.csh (Modification time mismatch)
warning: perl: /etc/profile.d/perlbin.sh (Modification time mismatch)
warning: perl: /etc/profile.d/perlbin.sh (Size mismatch)
ile: libldap: /etc/openldap/ldap.conf (Size mismatch)
backup file: man-db: /etc/man_db.conf (Modification time mismatch)
backup file: mkinitcpio: /etc/mkinitcpio.conf (Modification time mismatch)
backup file: openssl: /etc/ssl/openssl.cnf (Modification time mismatch)
openssl: 4112 total files, 6 altered files
p11-kit: 73 total files, 1 altered file
backup file: pacman: /etc/makepkg.conf (Modification time mismatch)
backup file: pacman: /etc/makepkg.conf (Size mismatch)
backup file: pacman: /etc/pacman.conf (Modification time mismatch)
backup file: pacman: /etc/pacman.conf (Size mismatch)
backup file: pacman-mirrorlist: /etc/pacman.d/mirrorlist (Modification time mismatch)
backup file: pacman-mirrorlist: /etc/pacman.d/mirrorlist (Size mismatch)
backup file: pambase: /etc/pam.d/system-login (Modification time mismatch)
backup file: pambase: /etc/pam.d/system-login (Size mismatch)
perl: 2799 total files, 2 altered files
pkgconf: 43 total fiwarning: shadow: /usr/bin/newgidmap (Permissions mismatch)
warning: shadow: /usr/bin/newuidmap (Permissions mismatch)
warning: systemd: /etc/X11/xinit/xinitrc.d/50-systemd-user.sh (Modification time mismatch)
warning: systemd: /etc/systemd/pstore.conf (Modification time mismatch)
warning: systemd: /etc/xdg/systemd/user (Modification time mismatch)
warning: systemd: /var/log/journal (GID mismatch)
backup file: rsync: /etc/rsyncd.conf (Modification time mismatch)
backup file: rsync: /etc/xinetd.d/rsync (Modification time mismatch)
backup file: rsync: /etc/xinetd.d/rsync (Size mismatch)
backup file: shadow: /etc/login.defs (Modification time mismatch)
backup file: shadow: /etc/default/useradd (Modification time mismatch)
backup file: shadow: /etc/pam.d/chage (Modification time mismatch)
backup file: shadow: /etc/pam.d/chgpasswd (Modification time mismatch)
backup file: shadow: /etc/pam.d/chpasswd (Modification time mismatch)
backup file: shadow: /etc/pam.d/groupadd (Modification time mismatch)
backup file: shadow: /etc/pam.d/groupdel (Modification time mismatch)
backup file: shadow: /etc/pam.d/groupmems (Modification time mismatch)
backup file: shadow: /etc/pam.d/groupmod (Modification time mismatch)
backup file: shadow: /etc/pam.d/newusers (Modification time mismatch)
backup file: shadow: /etc/pam.d/passwd (Modification time mismatch)
backup file: shadow: /etc/pam.d/shadow (Modification time mismatch)
backup file: shadow: /etc/pam.d/useradd (Modification time mismatch)
backup file: shadow: /etc/pam.d/userdel (Modification time mismatch)
backup file: shadow: /etc/pam.d/usermod (Modification time mismatch)
shadow: 558 total files, 2 altered files
backup file: sudo: /etc/sudo.conf (Modification time mismatch)
backup file: sudo: /etc/sudo.conf (Size mismatch)
backup file: sudo: /etc/sudo_logsrvd.conf (Modification time mismatch)
backup file: sudo: /etc/sudoers (Modification time mismatch)
backup file: sudo: /etc/sudoers (Size mismatch)
backup file: sudo: /etc/pam.d/sudo (Modification time mismatch)
backup file: systemd: /etc/pam.d/systemd-user (Modification time mismatch)
backup file: systemd: /etc/systemd/coredump.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/journal-remote.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/journal-upload.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/journald.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/journald.conf (Size mismatch)
backup file: systemd: /etc/systemd/logind.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/logind.conf (Size mismatch)
backup file: systemd: /etc/systemd/networkd.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/networkd.conf (Size mismatch)
backup file: systemd: /etc/systemd/resolved.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/resolved.conf (Size mismatch)
backup file: systemd: /etc/systemd/sleep.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/system.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/system.conf (Size mismatch)
backup file: systemd: /etc/systemd/timesyncd.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/user.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/user.conf (Size mismatch)
backup file: systemd: /etc/udev/udev.conf (Modification time mismatch)
backup file: systemd: /etc/udev/udev.conf (Size mismatch)
systemd: 1818 total files, 4 altered files
backup file: util-linux: /etc/pam.d/chfn (Modification time mismatch)
backup file: util-linux: /etc/pam.d/chsh (Modification time mismatch)
backup file: util-linux: /etc/pam.d/login (Modification time mismatch)
backup file: util-linux: /etc/pam.d/runuser (Modification time mismatch)
backup file: util-linux: /etc/pam.d/runuser-l (Modification time mismatch)
backup file: util-linux: /etc/pam.d/su (Modification time mismatch)
backup file: util-linux: /etc/pam.d/su-l (Modification time mismatch)
backup file: vim-runtime: /etc/vimrc (Modification time mismatch)

Offline

#19 2020-10-05 23:58:27

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: login screen loop after update

warning: filesystem: /bin (Modification time mismatch)
warning: filesystem: /lib (Modification time mismatch)
warning: filesystem: /lib64 (Modification time mismatch)
warning: filesystem: /sbin (Modification time mismatch)

What is the output of

stat /bin /lib /lib64 /sbin

Last edited by loqs (2020-10-05 23:59:28)

Offline

#20 2020-10-06 00:01:05

ErdosOrGauss
Member
Registered: 2017-06-21
Posts: 40

Re: login screen loop after update

loqs wrote:

What is the output of

stat /bin /lib /lib64 /sbin

The output is as follows:

File: /bin -> usr/bin
  Size: 7         	Blocks: 0          IO Block: 4096   symbolic link
Device: 10305h/66309d	Inode: 12          Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2020-10-05 10:18:11.342557042 -0600
Modify: 2020-05-19 16:42:31.000000000 -0600
Change: 2020-10-05 09:03:08.304916303 -0600
 Birth: 2020-10-01 22:54:24.294029351 -0600
  File: /lib -> usr/lib
  Size: 7         	Blocks: 0          IO Block: 4096   symbolic link
Device: 10305h/66309d	Inode: 13          Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2020-10-05 10:28:40.133077712 -0600
Modify: 2020-05-19 16:42:31.000000000 -0600
Change: 2020-10-05 09:03:08.304916303 -0600
 Birth: 2020-10-01 22:54:24.297362783 -0600
  File: /lib64 -> usr/lib
  Size: 7         	Blocks: 0          IO Block: 4096   symbolic link
Device: 10305h/66309d	Inode: 14          Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2020-10-05 09:53:23.411416305 -0600
Modify: 2020-05-19 16:42:31.000000000 -0600
Change: 2020-10-05 09:03:08.304916303 -0600
 Birth: 2020-10-01 22:54:24.297362783 -0600
  File: /sbin -> usr/bin
  Size: 7         	Blocks: 0          IO Block: 4096   symbolic link
Device: 10305h/66309d	Inode: 15          Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2020-10-05 10:43:38.959999975 -0600
Modify: 2020-05-19 16:42:31.000000000 -0600
Change: 2020-10-05 09:03:08.304916303 -0600
 Birth: 2020-10-01 22:54:24.297362783 -0600

Offline

#21 2020-10-06 00:10:55

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: login screen loop after update

pwck -r
grpck -r

There will be no output if no issues are detected.

If you add the boot option emergency to boot to emergency.target which uses a different pam stack can you login as root?

Offline

#22 2020-10-06 00:27:09

ErdosOrGauss
Member
Registered: 2017-06-21
Posts: 40

Re: login screen loop after update

I have posted the output of the commands below. They were entered in the order they appeared.

pwck -r

This had the following output:

user 'root': program '/bin/zsh' does not exist
user 'max':program '/usr/bin/zsh' does not exist

After installing zsh (and zsh-completions), the command above produces no output, as desired. After I tried logging in, the same error persists.


The command

grpck -r

produced no output.



If you add the boot option emergency to boot to emergency.target which uses a different pam stack can you login as root?

Yes, I can.

Offline

#23 2020-10-06 00:43:19

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: login screen loop after update

ErdosOrGauss wrote:

If you add the boot option emergency to boot to emergency.target which uses a different pam stack can you login as root?

Yes, I can.

What if you overwrite system-auth with the system-auth.pacnew file:

# mv /etc/pam.d/system-auth.pacnew /etc/pam.d/system-auth

Offline

#24 2020-10-06 00:49:23

ErdosOrGauss
Member
Registered: 2017-06-21
Posts: 40

Re: login screen loop after update

loqs wrote:
ErdosOrGauss wrote:

If you add the boot option emergency to boot to emergency.target which uses a different pam stack can you login as root?

Yes, I can.

What if you overwrite system-auth with the system-auth.pacnew file:

# mv /etc/pam.d/system-auth.pacnew /etc/pam.d/system-auth

By the system-auth.pacnew file, do you mean the system-login.pacnew file? I do not have a system-auth.pacnew file.

Last edited by ErdosOrGauss (2020-10-06 00:52:11)

Offline

#25 2020-10-06 00:51:43

loqs
Member
Registered: 2014-03-06
Posts: 19,043

Re: login screen loop after update

Yes.

Offline

Board footer

Powered by FluxBB