I'm experiencing this issue as well (on sid) after upgrading from sudo 1.8.3p1-3 to 1.8.3p2-1.1 (along with many other system updates). Here's what I can add:
There seems to be something like a race condition going on. Sometimes sudo works, sometimes it does not. For example: # for ((i=0; i<100; i++)); do sudo ls /; done bin boot dev etc home lib media mnt opt proc root run sbin selinux srv sys tmp usr var bin boot dev etc home lib media mnt opt proc root run sbin selinux srv sys tmp usr var bin boot dev etc home lib media mnt opt proc root run sbin selinux srv sys tmp usr var bin boot dev etc home lib media mnt opt proc root run sbin selinux srv sys tmp usr var bin boot dev etc home lib media mnt opt proc root run sbin selinux srv sys tmp usr var bin boot dev etc home lib media mnt opt proc root run sbin selinux srv sys tmp usr var bin boot dev etc home lib media mnt opt proc root run sbin selinux srv sys tmp usr var (There are 7 lines of output there; there should be 100 lines.) I've tried to reproduce this in a minimal i386 debootstrap image, but cannot. Frustratingly it works in the chroot image but not on my system. Downgrading sudo resolved the issue (I went all the way back to 1.7.4p4-2.squeeze.3 as it was available). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
