Are there any files in /etc/sudoers.d?
Only this one
Check the system polkit directories in /usr/share/polkit-1 as well. It would be kind of odd to store a custom file in there, but maybe worth a peek.
I’m suspicious of that sys group. Do you know why you added your user to that group?
/u/s/polkit-1 ❯❯❯ ls -lR
.:
total 12
drwxr-xr-x 2 root root 4096 Apr 21 08:48 actions/
-rw-r--r-- 1 root root 881 Jan 15 08:36 policyconfig-1.dtd
drwxr-xr-x 2 root root 4096 Apr 20 09:18 rules.d/
./actions:
total 1316
lrwxrwxrwx 1 root root 62 Apr 5 16:47 com.teamviewer.TeamViewer.policy -> /opt/teamviewer/tv_bin/script/com.teamviewer.TeamViewer.policy
-rw-r--r-- 1 root root 1872 Apr 18 21:42 io.systemd.credentials.policy
-rw-r--r-- 1 root root 4032 Apr 18 21:42 io.systemd.mount-file-system.policy
-rw-r--r-- 1 root root 1051 Apr 2 17:15 org.debian.pcsc-lite.policy
-rw-r--r-- 1 root root 3912 Nov 26 21:30 org.fedoraproject.FirewallD1.desktop.policy.choice
lrwxrwxrwx 1 root root 49 Nov 26 21:30 org.fedoraproject.FirewallD1.policy -> org.fedoraproject.FirewallD1.server.policy.choice
-rw-r--r-- 1 root root 4020 Nov 26 21:30 org.fedoraproject.FirewallD1.server.policy.choice
-rw-r--r-- 1 root root 33541 Apr 19 2024 org.freedesktop.accounts.policy
-rw-r--r-- 1 root root 171266 Apr 9 16:30 org.freedesktop.fwupd.policy
-rw-r--r-- 1 root root 4788 Apr 18 21:42 org.freedesktop.home1.policy
-rw-r--r-- 1 root root 4160 Apr 18 21:42 org.freedesktop.hostname1.policy
-rw-r--r-- 1 root root 2812 Apr 18 21:42 org.freedesktop.import1.policy
-rw-r--r-- 1 root root 1902 Apr 18 21:42 org.freedesktop.locale1.policy
-rw-r--r-- 1 root root 25154 Apr 18 21:42 org.freedesktop.login1.policy
-rw-r--r-- 1 root root 6224 Apr 18 21:42 org.freedesktop.machine1.policy
-rw-r--r-- 1 root root 53717 Apr 11 02:38 org.freedesktop.ModemManager1.policy
-rw-r--r-- 1 root root 10975 Apr 18 21:42 org.freedesktop.network1.policy
-rw-r--r-- 1 root root 171933 Feb 28 18:56 org.freedesktop.NetworkManager.policy
-rw-r--r-- 1 root root 8964 Jan 15 08:36 org.freedesktop.policykit.examples.pkexec.policy
-rw-r--r-- 1 root root 5982 Jan 15 08:36 org.freedesktop.policykit.policy
-rw-r--r-- 1 root root 2225 Apr 18 21:42 org.freedesktop.portable1.policy
-rw-r--r-- 1 root root 1785 Jul 13 2024 org.freedesktop.RealtimeKit1.policy
-rw-r--r-- 1 root root 10883 Apr 18 21:42 org.freedesktop.resolve1.policy
-rw-r--r-- 1 root root 4385 Apr 18 21:42 org.freedesktop.systemd1.policy
-rw-r--r-- 1 root root 3104 Apr 18 21:42 org.freedesktop.timedate1.policy
-rw-r--r-- 1 root root 1342 Apr 18 21:42 org.freedesktop.timesync1.policy
-rw-r--r-- 1 root root 367712 Sep 3 2024 org.freedesktop.UDisks2.policy
-rw-r--r-- 1 root root 1032 Apr 10 20:40 org.freedesktop.upower.policy
-rw-r--r-- 1 root root 10873 Jan 30 20:46 org.gnome.gparted.policy
-rw-r--r-- 1 root root 12345 Apr 2 23:04 org.kde.fontinst.policy
-rw-r--r-- 1 root root 6486 Apr 2 19:48 org.kde.kameleonhelper.policy
-rw-r--r-- 1 root root 11706 Apr 2 19:54 org.kde.kcontrol.kcmclock.policy
-rw-r--r-- 1 root root 9395 Apr 11 18:53 org.kde.kcontrol.kcmkwallet5.policy
-rw-r--r-- 1 root root 35246 Apr 2 20:08 org.kde.kcontrol.kcmsddm.policy
-rw-r--r-- 1 root root 9613 Apr 2 19:57 org.kde.kded.smart.policy
-rw-r--r-- 1 root root 17022 Apr 2 19:40 org.kde.kinfocenter.dmidecode.policy
-rw-r--r-- 1 root root 7197 Apr 11 16:06 org.kde.kpmcore.externalcommand.policy
-rw-r--r-- 1 root root 52956 Apr 2 18:34 org.kde.ksysguard.processlisthelper.policy
-rw-r--r-- 1 root root 8569 Apr 20 09:04 org.kde.ktexteditor6.katetextbuffer.policy
-rw-r--r-- 1 root root 30677 Apr 2 19:42 org.kde.powerdevil.backlighthelper.policy
-rw-r--r-- 1 root root 33439 Apr 2 19:42 org.kde.powerdevil.chargethresholdhelper.policy
-rw-r--r-- 1 root root 8181 Apr 2 19:42 org.kde.powerdevil.discretegpuhelper.policy
-rw-r--r-- 1 root root 86187 Apr 1 11:15 org.libvirt.api.policy
-rw-r--r-- 1 root root 3729 Apr 1 11:15 org.libvirt.unix.policy
-rw-r--r-- 1 root root 1764 Feb 18 21:49 power-profiles-daemon.policy
./rules.d:
total 20
-rw-r--r-- 1 root root 326 Jan 15 08:36 50-default.rules
-rw-r--r-- 1 root root 281 Apr 1 11:15 50-libvirt.rules
-rw-r--r-- 1 root root 252 Apr 9 16:30 org.freedesktop.fwupd.rules
-rw-r--r-- 1 root root 287 Sep 4 2024 org.freedesktop.GeoClue2.rules
-rw-r--r-- 1 root root 527 Apr 18 21:42 systemd-networkd.rules
Not sure what I should be looking for in here.
Should I try removing myself from the sys group? I haven’t learnt anything about groups so if that looks out of place it could well be part of the change I made.
I’m not sure, I have never used that group. I am wondering if it was recommended in a guide you followed when you set it up, or something like that.
This article is how to set the NOPASSWD option in the sudoers file, which it seems is not the case here…but if you scroll all the way down to the comments, there are a couple suggestions for automatically providing the password to a sudo prompt with a python script. Do you think you may have set up something like that?
If so, perhaps there has been an alias set.
alias | grep 'sudo'
It works regardless of using either bash or fish, and there’s nothing under either of those sets of aliases. It’s weird because I don’t remember seeing anything about visudo or NOPASSWD at the time, so either I was a lot worse at figuring out the right search terms or maybe I asked someone…
Don’t know if the sudo site has a forum but if it has, they should know what happens.
Edit: you seem to have some teamviewer settings, are you using it? That might lead to the culprit…
What does the journal say when you use sudo?
Example:
journalctl -b | grep sudo
~ ❯❯❯ sudo ls /root
Desktop Documents Downloads Music Pictures Public Templates Videos
~ ❯❯❯ journalctl -b | grep sudo
Apr 25 07:27:41 pigeon sudo[2781]: pam_unix(sudo:auth): user [laura] has blank password; authenticated without it
Apr 25 07:27:41 pigeon sudo[2781]: laura : TTY=pts/2 ; PWD=/home/laura ; USER=root ; COMMAND=/usr/bin/rm -f /var/lib/pacman/db.lck
Apr 25 07:27:41 pigeon sudo[2781]: pam_unix(sudo:session): session opened for user root(uid=0) by laura(uid=1000)
Apr 25 07:27:41 pigeon sudo[2781]: pam_unix(sudo:session): session closed for user root
Apr 25 07:27:41 pigeon sudo[2787]: laura : TTY=pts/2 ; PWD=/home/laura ; USER=root ; COMMAND=/usr/bin/pacman -Sy
Apr 25 07:27:41 pigeon sudo[2787]: pam_unix(sudo:session): session opened for user root(uid=0) by laura(uid=1000)
Apr 25 07:27:48 pigeon sudo[2787]: pam_unix(sudo:session): session closed for user root
Apr 25 07:27:49 pigeon sudo[2823]: laura : TTY=pts/2 ; PWD=/home/laura ; USER=root ; COMMAND=/usr/bin/pacman -Su
Apr 25 07:27:49 pigeon sudo[2823]: pam_unix(sudo:session): session opened for user root(uid=0) by laura(uid=1000)
Apr 25 07:28:29 pigeon sudo[2823]: pam_unix(sudo:session): session closed for user root
Apr 25 07:28:49 pigeon sudo[3191]: pam_unix(sudo:auth): user [laura] has blank password; authenticated without it
Apr 25 07:28:49 pigeon sudo[3191]: laura : TTY=pts/4 ; PWD=/home/laura ; USER=root ; COMMAND=/usr/bin/ls /root
Apr 25 07:28:49 pigeon sudo[3191]: pam_unix(sudo:session): session opened for user root(uid=0) by laura(uid=1000)
Apr 25 07:28:49 pigeon sudo[3191]: pam_unix(sudo:session): session closed for user root
That’s very strange, because I don’t have a blank password, I can’t pass SDDM without a password. But… I used passwd to set my password to what I thought my password was, and now it’s acting as I’d want. I have no idea how I’d retrospective this, but its fixed.
Now you know what you did 
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.