cat /etc/sudoers|egrep -v '^$|^#'
root ALL=(ALL:ALL) ALL
@includedir /etc/sudoers.d
%wheel ALL=(ALL) ALL
Defaults!/etc/ctdb/statd-callout !requiretty
rpcuser ALL=(ALL) NOPASSWD: /etc/ctdb/statd-callout
This is the result.
Thank you.
may 03 17:53:52 mlpbcn-systemproductname plasmashell[1978]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:89:9: QML ScrollView: Binding loop detected for property "bottomPadding"
may 03 17:53:53 mlpbcn-systemproductname systemd[1]: systemd-timedated.service: Deactivated successfully.
may 03 17:53:53 mlpbcn-systemproductname audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
may 03 17:53:53 mlpbcn-systemproductname kernel: audit: type=1131 audit(1651593233.319:186): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
may 03 17:53:53 mlpbcn-systemproductname audit: BPF prog-id=0 op=UNLOAD
may 03 17:53:53 mlpbcn-systemproductname audit: BPF prog-id=0 op=UNLOAD
may 03 17:53:53 mlpbcn-systemproductname audit: BPF prog-id=0 op=UNLOAD
may 03 17:53:53 mlpbcn-systemproductname kernel: audit: type=1334 audit(1651593233.349:187): prog-id=0 op=UNLOAD
may 03 17:53:53 mlpbcn-systemproductname kernel: audit: type=1334 audit(1651593233.349:188): prog-id=0 op=UNLOAD
may 03 17:53:53 mlpbcn-systemproductname kernel: audit: type=1334 audit(1651593233.349:189): prog-id=0 op=UNLOAD
may 03 17:53:55 mlpbcn-systemproductname xdg-desktop-portal-kde[2267]: xdp-kde-background: GetAppState called: no parameters
may 03 17:53:55 mlpbcn-systemproductname systemd[1]: blueman-mechanism.service: Deactivated successfully.
may 03 17:53:55 mlpbcn-systemproductname audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
may 03 17:53:55 mlpbcn-systemproductname kernel: audit: type=1131 audit(1651593235.842:190): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
may 03 17:54:01 mlpbcn-systemproductname dbus-daemon[1018]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.99' (uid=0 pid=2557 comm="sudo pacman -Syyu")
may 03 17:54:01 mlpbcn-systemproductname dbus-daemon[1018]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
may 03 17:54:01 mlpbcn-systemproductname sudo[2557]: pam_systemd_home(sudo:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
may 03 17:54:08 mlpbcn-systemproductname audit[2557]: USER_AUTH pid=2557 uid=1000 auid=1000 ses=2 subj==unconfined msg='op=PAM:authentication grantors=? acct="mlpbcn" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=failed'
may 03 17:54:08 mlpbcn-systemproductname kernel: audit: type=1100 audit(1651593248.279:191): pid=2557 uid=1000 auid=1000 ses=2 subj==unconfined msg='op=PAM:authentication grantors=? acct="mlpbcn" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=failed'
may 03 17:54:15 mlpbcn-systemproductname systemd[1]: systemd-localed.service: Deactivated successfully.
may 03 17:54:15 mlpbcn-systemproductname audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
may 03 17:54:15 mlpbcn-systemproductname kernel: audit: type=1131 audit(1651593255.699:192): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
may 03 17:54:15 mlpbcn-systemproductname audit: BPF prog-id=0 op=UNLOAD
may 03 17:54:15 mlpbcn-systemproductname audit: BPF prog-id=0 op=UNLOAD
may 03 17:54:15 mlpbcn-systemproductname audit: BPF prog-id=0 op=UNLOAD
may 03 17:54:15 mlpbcn-systemproductname kernel: audit: type=1334 audit(1651593255.782:193): prog-id=0 op=UNLOAD
may 03 17:54:15 mlpbcn-systemproductname kernel: audit: type=1334 audit(1651593255.782:194): prog-id=0 op=UNLOAD
may 03 17:54:15 mlpbcn-systemproductname kernel: audit: type=1334 audit(1651593255.782:195): prog-id=0 op=UNLOAD
may 03 17:54:25 mlpbcn-systemproductname xdg-desktop-portal-kde[2267]: xdp-kde-background: GetAppState called: no parameters
may 03 17:54:26 mlpbcn-systemproductname systemd[1]: pcscd.service: Deactivated successfully.
may 03 17:54:26 mlpbcn-systemproductname audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=pcscd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
may 03 17:54:26 mlpbcn-systemproductname kernel: audit: type=1131 audit(1651593266.449:196): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=pcscd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
may 03 17:54:43 mlpbcn-systemproductname audit[2557]: USER_AUTH pid=2557 uid=1000 auid=1000 ses=2 subj==unconfined msg='op=PAM:authentication grantors=? acct="mlpbcn" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=failed'
may 03 17:54:43 mlpbcn-systemproductname k```
This is the result.
Thank you.You forgot to verivy this:
Yes I did, thatās why my answer says Iāve done the āthreeā things you told me.
Then I suggest that you follow the advice of @stargazer and look in the forum for this kind of problem and the possible solutions people had for this.
Iāll also look, but for the moment I have no good idea what might have happened or what to look at next.
One thing you can try:
journalctl -f
in a terminal
and in another terminal, try to run, for instance
sudo pacman -Syu
and watch the output in the first terminal - it will print messages for new events, it will āfollowā and show you only recent events as they are happening in real time.
That might yield a clue.
I already did that and you have the result in the previous message.
ā¦ right - I did expect to see at least some error messages logged - but nothing
I know that there will be messages when I (successfully) use sudo.
I didnāt expect nothing to be logged when sudo was not successful.
Do you get any response when you use sudo some_command and it doesnāt work?
Or just nothing? ā¦
sudo pacman -Syyu
[sudo] password for mlpbcn:
Sorry, try again.
[sudo] password for mlpbcn:
Sorry, try again.
[sudo] password for mlpbcn:
sudo: 3 incorrect password attempts
I have noticed that after a while the problem disappears, but if I restart it reappears.
Do you mean that sudo suddenly begins to work then, after a while?
That sounds very strange - but I have heard/read something in relation to fingerprint sensors to have been the culprit.
Gnome Desktop Environment ā¦
ā¦ just hearsay, from what I believe is my memory (as opposed to phantasy/delusion 
)
[sudo] contraseƱa para mlpbcn:
Lo siento, pruebe otra vez.
[sudo] contraseƱa para mlpbcn:
Lo siento, pruebe otra vez.
[sudo] contraseƱa para mlpbcn:
sudo: 3 incorrect password attempts
[mlpbcn@mlpbcn-systemproductname ~]$ nordvpn c spain
Connecting to Spain #182 (es182.nordvpn.com)
You are connected to Spain #182 (es182.nordvpn.com)!
[mlpbcn@mlpbcn-systemproductname ~]$ sudo pacman -Syyu
[sudo] contraseƱa para mlpbcn:
Lo siento, pruebe otra vez.
[sudo] contraseƱa para mlpbcn:
sudo: timed out reading password
sudo: 1 incorrect password attempt
[mlpbcn@mlpbcn-systemproductname ~]$ sudo pacman -Syyu
[sudo] contraseƱa para mlpbcn:
:: Sincronizando las bases de datos de los paquetes...
core 169,1 KiB 591 KiB/s 00:00 [#######################################################################################] 100%
extra 1854,2 KiB 10,4 MiB/s 00:00 [#######################################################################################] 100%
community 6,9 MiB 27,9 MiB/s 00:00 [#######################################################################################] 100%
multilib 182,0 KiB 3,56 MiB/s 00:00 [#######################################################################################] 100%
:: Iniciando actualizaciĆ³n completa del sistema...
advertencia: lib32-mesa: la versiĆ³n instalada (22.0.0-1) es mĆ”s nueva que multilib (21.3.8-2)
advertencia: python-pyqt5: la versiĆ³n instalada (5.15.6-7.1) es mĆ”s nueva que extra (5.15.6-7)
...el sistema ya estĆ” actualizado.
[```ā¦ that is strange indeed.
I only have the hunch I already shared - fingerprint sensor related.
tip - so that everyone can read what I believe is portugese
start your command with:
LANG=C
like:
LANG=C sudo pacman -Syu
so the output will be english
Itās Spanish, next time Iāll do lol you suggest me.
But, I donāt have a fingerprint sensor, my pc is not a laptop.
Thank you.
I will keep looking - but as of now Iām out of ideas.
Your profile says your DE is KDE.
Is that correct?
I do not have KDE, but use Xfce instead - but there should not be any difference when it comes to command line and sudo.
If you are KDE, I will also be tried to find out what is happening. Thank you for your help and everyone.
The line %wheel ALL=(ALL:ALL) ALL was commented out in the sudoers file, I uncommented it, but it didnāt fix the problem. I thought that if it was commented out, users in the wheel group couldnāt use the sudo command, but even if it was commented out, my user could use the sudo command, although as I said, some time after logging in.
the wheel group is allowed/enabled in the other file
so it is ok that it was not enabled in /etc/sudoers
and that is why it worked
I havenāt solved the problem yet, but Iām still investigating.
Do you have a script running from time to time that runs sudo? It would ask for a password but being a script canāt get it and times out, (or piped a wrong password into it).
Thereās nothing about sudo on the journal output above. Could you retry?
In the end Iām going to reinstall Manjaro, because besides the problem with sudo, Iāve run out of space on the root partition and my file system is xfs. Search how to increase the size of the partition, but being xfs, I found it very complicated, so I will fix two problems at once.
Thank you all for your time and your help.