There have to be edge cases where the replacement does not happen even
if I never touched a file myself. But I don't know how to debug this.
There are more ".pacnew" in my /etc. All for files that I never touched
myself.
And about the "system-login"-thing: I'm not the only one who had this
problem:
https://www.reddit.com/r/archlinux/comments/id6tem/cant_login_as_user_or_root_after_upgrade/
https://www.reddit.com/r/archlinux/comments/ie3i8d/super_weird_login_problem/
https://www.reddit.com/r/archlinux/comments/idjpw3/issues_with_pam_tally2_after_full_system_upgrade/
https://www.reddit.com/r/archlinux/comments/iczyr0/psa_be_careful_with_pacnew_when_updating/
https://www.reddit.com/r/archlinux/comments/id3dsu/unable_to_login_after_upgrade/
https://www.reddit.com/r/archlinux/comments/id6ce4/not_able_to_login_after_updating_pam_to_1403/
https://www.reddit.com/r/archlinux/comments/icnzrx/after_latest_update_my_computer_cant_login/
https://www.reddit.com/r/archlinux/comments/icr4sv/incorrect_login_with_correct_password_even_reset/
And maybe more. I guess there is something wrong with the way how pacman
decides when to move ".pacnew" into place directly.
And I'm wondering how many users actually got lost with this issue of
not being able to log in after updating and just wiped Arch off their
hard drive... :(
IMHO something should be done to at least find out why pacman does not
replace *non user modified* files in some cases...
Manuel
On 19.08.20 21:07, Josef Miegl wrote:
This can only happen if you or another program modified the original file.
Josef Miegl
On August 19, 2020 9:02:12 PM GMT+02:00, Manuel Reimer <mail+archgeneral@xxxxxxxxxxx> wrote:
Hello,
I know that Arch is not for the "average user" and some background
knowledge is expected, but this was the first time I needed a boot
stick
since I think at least one year.
Some minutes ago I did a regular system update and after that decided
to
reboot. After reboot I was unable to log into my system. After fiddling
a bit I rebooted to an Arch boot stick to find the following message in
pacman.log:
[2020-08-19T20:42:55+0200] [ALPM] warning: /etc/pam.d/system-login
installed as
/etc/pam.d/system-login.pacnew
As this seemed to be a candidate that may cause login problems, I
deleted "system-login" and moved the ".pacnew" into place.
After reboot I'm now able to log in again...
IMHO something like this should not happen...
Maybe it's worth a note on the Arch homepage that it is important to
move this pacnew into place before reboot?
Manuel
