Package: sudo
Version: 1.8.27-1+deb10u2
Severity: normal
On a system with disk errors, which had therefore remounted its
file systems read-only, I tried to sudo in order to do further
diagnostics as root, but sudo crashed with a segfault.
I think it should be possible (perhaps with a special option) to
continue without writing this file, even if it means I'll be
lectured again if I run sudo again soon. In a situation like this,
it might be more important to get root access at all.
Even if it won't do this, a segfault is certainly a bug.
% sudo su
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
[sudo] password for frank:
sudo: unable to mkdir /var/lib/sudo/lectured: Input/output error
Segmentation fault
-- System Information:
Debian Release: 10.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500,
'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.6.0-0.bpo.2-amd64 (SMP w/24 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE=de_DE
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages sudo depends on:
ii libaudit1 1:2.8.4-3
ii libc6 2.28-10
ii libpam-modules 1.3.1-5
ii libpam0g 1.3.1-5
ii libselinux1 2.8-1+b1
ii lsb-base 10.2019051400
sudo recommends no packages.
sudo suggests no packages.
-- no debconf information
