su still works, so I was able to update all of my packages (except for AUR), though sudo is still not working. Using dmesg -wH the following error appears every time I invoke sudo:
[ +0.000256] sudo[3708]: segfault at 0 ip 00007f8df6642a85 sp 00007fffd6f0e2c8 error 4 in libc-2.32.so[7f8df6506000+14d000]
What about running just sudo, does that work? You could run sudo in gdb: gdb sudo, then r ls and enter, then when it dies, type bt and enter, and then it’ll show where the problem is. Maybe that could shed some light on the issue.
Sorry, I’m not quite sure I understand-- I’ve never used gdb before. Simply running sudo works just fine, though, but sudo gdb segfaults. When I try to run sudo within gdb, I get:
Some more (hopefully useful) information. The problem I have seems similar to the one here: Sudo broken [Solved] / Newbie Corner / Arch Linux Forums. I noticed that the segfault does not appear when I run strace sudo ls, but I do get the following error at the end of the strace:
write(2, "effective uid is not 0, is /usr/"..., 133effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?) = 133
the output of coredumpctl gdb sudo ls still indicates a segfault, however:
~ >>> coredumpctl gdb sudo ls [1]
PID: 7887 (sudo)
UID: 1000 (osman)
GID: 1000 (osman)
Signal: 11 (SEGV)
Timestamp: Tue 2020-12-08 20:18:04 EST (21min ago)
Command Line: sudo -s
Executable: /usr/bin/sudo
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-8e179c86-e009-4421-9c87-d50c3cd78ad2.scope
Unit: user@1000.service
User Unit: vte-spawn-8e179c86-e009-4421-9c87-d50c3cd78ad2.scope
Slice: user-1000.slice
Owner UID: 1000 (osman)
Boot ID: c4aebb3ae7544e23b786215519e7a82c
Machine ID: bacf17a284dd4a6dad8290b0ddae9f97
Hostname: univac
Storage: none
Message: Process 7887 (sudo) of user 1000 dumped core.
The thread I linked above, smbclient was apparently the one causing problems. However, smbclient was last updated on the 2nd, and this problem only appeared today.
I had the same issue earlier. I just restored my Timeshift system backup from last night with no success. However, I was able to run sudo pacman -Syu after switching to a BASH shell. After updating again neither ZSH nor BASH worked again. I may try restoring my backup again and hold off on the update until tomorrow.
These are the packages that were updated since my Timeshift backup was made last night:
No, sudo and sudo su are now working fine after I restored my Timeshift backup before those updates.
I tried downgrading apparmor, but that didn’t help. I just restored my Timeshift backup again and will hold off updating for now. Maybe it’s the systemd packages. I see Arch pushed 247.1-3, which we don’t have just yet.
You are not running sudo in a root shell there, you are probably only running ls in a root shell…
(Unless i interpreted your output wrongly ofcourse)
It could also be because of the difference of shell used in the root shell, which is bash…