Ah, that was the piece I was missing. Somehow after adding the debian- installer repo in order to play with d-i creation, either I accidentally installed cdebconf-udeb, or some other package took it on as a dependency and I didn't even notice it (for a few years I might add).
I'm honestly surprised this hadn't caused issues before. It certainly wreaked havoc on my system during this attempted upgrade. I was eventually able to brute-force the removal of cdebconf and reconfigure debconf and fix my broken system. This is resolved, and was not an issue with libpam but rather my own misfortune and cdebconf being _almost good enough_ to fool me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831221 Title: do-release-upgrade fails due to package libpam0g:amd64 1.1.8-3.2ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1831221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs