Saturday, April 1, 2017

Administrative Password Rejected After Pacman Upgrade And Pacnew Merges

I updated the system today.

[2017-04-01 07:22] [PACKAGEKIT] synchronizing package lists
[2017-04-01 07:46] [PACMAN] Running 'pacman -Syu'
[2017-04-01 07:46] [PACMAN] synchronizing package lists
[2017-04-01 07:46] [PACMAN] starting full system upgrade
[2017-04-01 07:46] [ALPM] transaction started
[2017-04-01 07:46] [ALPM] warning: /etc/group installed as /etc/group.pacnew
[2017-04-01 07:46] [ALPM] warning: /etc/passwd installed as /etc/passwd.pacnew
[2017-04-01 07:46] [ALPM] warning: /etc/gshadow installed as /etc/gshadow.pacnew
[2017-04-01 07:46] [ALPM] warning: /etc/shadow installed as /etc/shadow.pacnew
[2017-04-01 07:46] [ALPM] upgraded filesystem (2016.12-2 -> 2017.03-2)
[2017-04-01 07:46] [ALPM] upgraded dbus (1.10.16-1 -> 1.10.16-2)
[2017-04-01 07:46] [ALPM] upgraded libutil-linux (2.29.2-1 -> 2.29.2-2)
[2017-04-01 07:46] [ALPM] upgraded util-linux (2.29.2-1 -> 2.29.2-2)
[2017-04-01 07:46] [ALPM] upgraded xdg-desktop-portal-gtk (0.5-3 -> 0.6-1)
[2017-04-01 07:46] [ALPM] upgraded xdg-desktop-portal (0.5-3 -> 0.6-1)
[2017-04-01 07:46] [ALPM] transaction completed
[2017-04-01 07:46] [ALPM] running 'systemd-sysusers.hook'...
[2017-04-01 07:46] [ALPM] running 'systemd-update.hook'...
[2017-04-01 07:46] [ALPM] running 'update-desktop-database.hook'...

The I know I have some pacnew files to merge. So I use pacdiff. I manually edited the files and overwrite it with pacdiff.

Everything is fine except I can't sudo because my administrative passwords aren't working. su isn't working either because well passwords aren't working. I'm in trouble.


Post a Comment

Reflections On My Blogging: Keeping It Honest

When you're facing a white, blank screen trying to decide what to write, it seemed hopeless and hopeful at the same time. It's like...