sudo not good enough to access /root ?

English Applications
1

The /root directory has these permissions:

drwx------   1 root      root   682 Jun 10 12:30 root/

This is the result of using sudo on /root:

sudo /usr/bin/ls /root/.local/share/backintime/takesnapshot_*.log
-bash: /usr/bin/ls /root/.local/share/backintime/takesnapshot_*.log: No such file or directory

I tried adding “–user=root” just to be sure. No joy.
Aside from changing the permissions of /root, is there a way use “sudo” to access /root?

2
  1. you use the bash-completion with TAB?
  2. why not using su -l to get root?
  3. is the file avaible there?
3
  1. you use the bash-completion with TAB?

I do not know what you mean. bash-completion is enabled. What is TAB? Acronym? Horizontal tab character?

  1. why not using su -l to get root?
$ su -l root "/usr/bin/ls /root/.local/share/backintime/takesnapshot_*.log"
Password: 
-bash: /usr/bin/ls /root/.local/share/backintime/takesnapshot_*.log: No such file or directory

Same result with “sudo -i” and “sudo --user=root”.

  1. is the file available there?

Yes.

$ su
Password:
$ /usr/bin/ls /root/.local/share/backintime/takesnapshot_*.log
/root/.local/share/backintime/takesnapshot_.log
4

You are probably using “pam_kwallet”. There’s a bug report on that. It breaks “sudo” and it may break login to root.

If you can still use Yast, then uninstall pam_kwallet, and that will fix everything. If you are prompted for a kwallet password, it will be the same as your login password.

5

You are probably using “pam_kwallet”.

No. pam_kwallet is not installed.

6

The indications are that a problem with “libgcrypt” is involved, and indirectly affects things via pam_kwallet. But maybe it affects other things.

Checkout this mailing list thread

That thread is for Tumbleweed. But it links to a bug report that in turn connects with a bug report on Leap 15.1. They are probably all related.