To be clear: For me, the issue with having to *shutdown* kdm *prior* to doing the upgrade is separate from the issue of configuring 'libpam0g'. I don't think I even had the dialog about libpam0g.
What I did have, however, was that the dist-upgrade started, downloaded the package lists and calculated required changes, and at this point (before starting the actual upgrade), asked me stop kdm and try again. So I cancelled out, logged out of X and stopped kdm, and started the dist-upgrade process again. This time around it seemed to download (again) the same things, and calculate the required changes (again). But it managed to continue alright. In sum: In retrospect I cannot be sure if my issue with kdm is the same as the original submitter's issue with kdm. I assume yes, because the requirement to shutdown kdm was *unconditional* (as per the OP's "has to be manually shut down before it can proceed"), no options were given. If this wasn't the case also for the OP, this may be a different issue. -- Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown https://bugs.launchpad.net/bugs/223226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
