Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
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.
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.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB Debian - "If you can't apt install something, it isn't useful or doesn't exist" My Giant Sources.list
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
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB Debian - "If you can't apt install something, it isn't useful or doesn't exist" My Giant Sources.list
/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).
Wikipedia wrote:The unstable, development distribution is permanently nicknamed sid, after the emotionally unstable next-door neighbor boy who regularly destroyed toys.
Debian == { > 30, 000 packages }; Debian != systemd
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
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.
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!!
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.
Old Threads: It is 'best' to start another Thread.
Posting in old threads, or "necrobumping" is generally discouraged in the technical issue subforums, since it can potentially create disjointed "zombie" information; outdated posts with data which is no longer relevant due to Debian 'future' updates, combined with more recent posts reflecting more current circumstance.
Furthermore, technical support threads should remain succinct, and multiple pages are to be avoided if possible.