I have sudo 1.8.3p1-1ubuntu3.1 from precise-proposed and I use pam_mount for mounting encrypted partitions at login.
While the original bug is fixed with the 1ubuntu3.1 version of sudo, 'sudoedit' command triggers pam_mount to enquire the password of the encrypted partition, trying to mount it and later to umount it. Mounting and umounting fails, because the encrypted partition is already mounted, unlocked and busy. $ sudoedit test reenter password for pam_mount: pam_mount(mount.c:69): Messages from underlying mount program: pam_mount(mount.c:73): crypt_activate_by_passphrase: File exists pam_mount(pam_mount.c:521): mount of /dev/myvolumehere/mypartitionhere failed pam_mount(mount.c:69): umount messages: pam_mount(mount.c:73): umount: /mnt/mymountedpartition: device is busy. pam_mount(mount.c:73): (In some cases useful info about processes that use pam_mount(mount.c:73): the device is found by lsof(8) or fuser(1)) pam_mount(mount.c:73): umount /mnt/mymountedpartition failed with run_sync status 1 pam_mount(mount.c:73): umount: /mnt/mymountedpartition: device is busy. pam_mount(mount.c:73): (In some cases useful info about processes that use pam_mount(mount.c:73): the device is found by lsof(8) or fuser(1)) pam_mount(mount.c:73): umount /mnt/mymountedpartition failed with run_sync status 1 pam_mount(mount.c:752): unmount of /dev/myvolumehere/mypartitionhere failed sudo does not trigger this behavior, just sudoedit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/927828 Title: sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/927828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
