Latest Sid updates broken [solved]

[buntunub]

Getting this on todays updates -

Code: Select all

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)
A package failed to install.  Trying to recover:
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.

Updates for

Code: Select all

libegl1-mesa libegl1-mesa-drivers libgbm1 libgl1-mesa-dev libgl1-mesa-dri
  libgl1-mesa-glx libglapi-mesa libglu1-mesa libglu1-mesa-dev libopenvg1-mesa
  librasqal3 mesa-common-dev

[ALLurGroceries]

Add /sbin back to your path as root and then retry the upgrade. Your PATH should be at least:

Code: Select all

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

so as root:

Code: Select all

export PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin

and then retry your apt-get upgrade

[anticapitalista]

I had something similar caused by the /etc/sudoers file.

It needed these lines.

Code: Select all

Defaults   env_reset
Defaults   secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"


[craigevil]

No issues here, running sid with daily or more often d-u.
Host: debian Kernel: 3.0.0-1-486 i686 (32 bit) Desktop KDE 4.6.5 Distro: Debian GNU/Linux wheezy/sid

# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

[craigevil]

I had something similar caused by the /etc/sudoers file.

It needed these lines.

Code: Select all

Defaults   env_reset
Defaults   secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"


Default root PATH:

echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Normal user (most people won't have the RealPlayer or surfraw)
craig@debian:~$ echo $PATH
/home/craig/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/opt/real/RealPlayer:/usr/lib/surfraw:/usr/lib/surfraw

[anticapitalista]

Just to clarify.

/etc/sudoers in sid, default already has those lines I posted. Mine didn't as my install had been upgraded from Testing and I kept my own sudoers file so it used the default from Testing (back then).

Code: Select all

# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/games


[buntunub]

Thanks for the help all. Updating my sudoers file with the proper path fixed this. I guess it got broke after the latest sudo update somehow.

[edbarx]

The unstable, development distribution is permanently nicknamed sid, after the emotionally unstable next-door neighbor boy who regularly destroyed toys.

[vbrummond]

Thanks! I had this issue as well and adding the lines to /etc/sudoers with visudo fixed it.

[62chevy]

Code: Select all

From root@sid Tue Sep 27 19:55:40 2011
Envelope-to: root@sid
Delivery-date: Tue, 27 Sep 2011 19:55:40 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Subject: apt-listchanges: news for sid
To: root@sid
From: root <root@sid>
Date: Tue, 27 Sep 2011 19:55:40 -0400

sudo (1.8.2-1) unstable; urgency=low

  The sudo package is no longer configured using --with-secure-path.
  Instead, the provided sudoers file now contains a line declaring
  'Defaults secure_path=' with the same path content that was previously
  hard-coded in the binary.  A consequence of this change is that if you
  do not have such a definition in sudoers, the PATH searched for commands
  by sudo may be empty.

  Using explicit paths for each command you want to run with sudo will work
  well enough to allow the sudoers file to be updated with a suitable entry
  if one is not already present and you choose to not accept the updated
  version provided by the package.
 
 -- Bdale Garbee <bdale@gag.com>  Wed, 24 Aug 2011 13:33:11 -0600



I received this message the other day when I updated my install.

[Lns]

Just another person that this thread fixed added the 'secure_path' line to /etc/sudoers via 'visudo' and everything works again. Strange how it stopped after a while, not sure when it broke exactly, but I'm running testing. Thank you all for the tips as always!!

[EddieB]

Chalk up another ... I opted not to update the sudoers during a push from squeeze to sid and was greeted with several debconf errors ...

Another saving thread ...

TY DUF.

[absum]

Had this same issue upgrading from squeeze to wheezy (chose to keep old sudoers file, might've caused this), adding the secure_path line fixed it. Thank you.