Given the current situation (described here), I’ve tried doing that and nothing changed.
This actually had not effect. I did this, and when went back, I was locked out for 10min because of fingerprint
I’ve tried this but it did not help. I ended up removing the fprintd and libfprint packages and now I no longer have this issue.
Exactly as here: Gnome wants fingerprint and password after update
Followed this page and some applied to my case. Changing passwords did not help, checked the following:
ls -ld /etc/pam.d
ls -l /etc/pam.d/sudo
cat /etc/pam.d/sudo
Output:
[manjaro etc]# ls -ld /etc/pam.d
drwxr-xr-x 2 root root 4096 jul 20 15:44 /etc/pam.d
[manjaro etc]# ls -l /etc/pam.d/sudo
-rw-r--r-- 1 root root 243 jul 19 18:31 /etc/pam.d/sudo
[manjaro etc]# cat /etc/pam.d/sudo
#%PAM-1.0
auth required pam_env.so
# auth sufficient pam_fprintd.so
# auth sufficient pam_unix.so try_first_pass likeauth nullok
auth required pam_deny.so
auth include system-auth
account include system-auth
session include system-auth
Mine looks different, it still is unchanged as provided by sudo
package:
$ cat /etc/pam.d/sudo
#%PAM-1.0
auth include system-auth
account include system-auth
session include system-auth
Could you show me the output of your groups
and sudo -l
?
I think that I might be missing something.
Also to note that I’ve installed the Gnome minimal version and not the “full” one. What I did today:
- Install minimal version in VM and recreate the sudo issue
- Install full version in VM and recreate the sudo issue
In both test cases, I had no issues with sudo, leaving me to believe that either fingerprint was messing all of this, or my download .iso was corrupted, although has the was correct
Also, my USB is somehow faulty, as when formatting it, it takes lots of time (64GB Kingston, USB3.0)
Ok, after attempting again to just continue with my issues, after a restart I was not longer able to login agian. My username was not displayed on the login window, and when I typed my username and password I got the message that password was not correct (I could not even login from a TTY). I then proceeded to:
- Download a new full manjaro .iso (not the minimal version as I previously did)
- Burn on the same USB
- Wipe and install laptop
After doing these steps, was able to login into my user and sudo was working ok. For now I won’t be upgrading since the extension is broken with the current version of Gnome (dash-to-dock) since it breaks my workflow. Given my previous issues with fingerprint I decided to not install any updates/upgrades and leave the system be (proceeded only to install the packages that I needed). Although to avoid any future issues with fingerprint, I did the following (as per archwiki):
Before file change:
cat /etc/pam.d/system-local-login
#%PAM-1.0
auth include system-login
account include system-login
password include system-login
session include system-login
cat /etc/pam.d/sudo
#%PAM-1.0
auth required pam_env.so
auth sufficient pam_fprintd.so
auth sufficient pam_unix.so try_first_pass likeauth nullok
auth required pam_deny.so
auth include system-auth
account include system-auth
session include system-auth
After file change:
/etc/pam.d/system-local-login
← remained the same
cat /etc/pam.d/sudo
#%PAM-1.0
auth required pam_env.so
# auth sufficient pam_fprintd.so
# auth sufficient pam_unix.so try_first_pass likeauth nullok
auth required pam_deny.so
auth include system-auth
account include system-auth
session include system-auth
Also removed the packages:
sudo pacman -R fprintd libfprint
- Restart
- Login into user → sucess
- Try
sudo -i
→ Got incorrect password - Removed previously added
#
to/etc/pam.d/sudo
- Restart
- Login into user → sucess
- Try
sudo -i
→ sucess
So apparently, those two lines were most probably the ones that did not allow me to use sudo
in terminal. All this happened on the following version:
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=21.0.7
DISTRIB_CODENAME=Ornara
Edit: Fixed typos and made text more clear. Will report back in a couple of days if all goes well, and accept this as solution.
Edit 2: So 3 days later and I’m not experiencing any issues whatsoever. I still haven’t upgraded (and probably will not for the next several months). I’ll accept this as a solution.
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.