Joseph Lenox wrote: > After updating Sid last week, I tried to install something with > apt-get using sudo and got the following error from dpkg: > > dpkg: warning: 'ldconfig' not found in PATH or not executable. > dpkg: warning: 'start-stop-daemon' not found in PATH or not executable. > dpkg: error: 2 expected programs not found in PATH or not executable. > Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin > and /sbin. > E: Sub-process /usr/bin/dpkg returned an error code (2) > > Any apt-get subcommand that calls dpkg as a subprocess (install, > autoremove) fails with that error.. if I use sudo. > > Synaptic package manager works fine, as does changing to root with "su -". > > Any offhand ideas as to where to look first to figure out what's going on? Just recently a new sudo entered Wheezy Testing and it changed the behavior of secure_path. See Bug#639841 for details. It no longer overrides your path with a standard system PATH by default. So now unless you set it in your /etc/suders file it will use the PATH it started with and if you don't already add the /usr/sbin and other paths then it won't either. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639841 Quick fix: Add this line to your /etc/sudoers file. Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" Bob
Attachment:
signature.asc
Description: Digital signature