-
-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No way to get Howdy to start authentication at system start with Ubuntu 24.04 #927
Comments
Im sorry my comment won't be useful, I just want to say I just came to this repo to open the exact same issue I'm facing with Ubuntu 24.04. I'm also very frustrated. I can add and test face, but I'm not able to make it work when typing sudo nor in login screen (gdm). |
Now it works. I have a Laptop with the lid closed.
By default it was set to true. |
This worked for me as well! Thank you for sharing. Since I'm on a fresh install, I also had to install numpy and opencv:
Then I got an indentation error in I also had to add Finally, I edited Moral of the story is that if anything goes wrong, |
Thanks for the additional step by step instructions. This is how it should be. I think we now have a very good overview and help for anyone who has the same issue. |
Thank you so much! It has fixed my issue on my Dell xps 9500 |
这里我按你的做了也不行,
启动登陆和shell下的sudo 都可以用了。 sudo mv /usr/lib/python3.12/EXTERNALLY-MANAGED /usr/lib/python3.12/EXTERNALLY-MANAGED.BAK (安装完howdy后我又改回去了) |
Thanks for the great advice, followed it all & ended up with the issue:
I found numpy 2.0.0 released yesterday... The fix I found was: sudo pip3 uninstall numpy sudo pip3 install numpy==1.26.4 |
Did you try the workaround for the ConfigParser Error? Howdy didn't work for me too on a fresh Ubuntu 24 install and after the configparser fix it tried to use the face recognition. Also make sure to add a face model (obvious I know but I just wanted to make sure you don't forget it) |
I was able to get Howdy running for login screens and console login using this method, thing is I add the line "auth |
The Keyring prompt has nothing to do with howdy. It pops up because passwords which got saved in the keyring are protected with a password. And usually by logging in with your password this keyring does get unlocked automatically, but since you don't enter any password with howdy the keyring remains locked. You can either set the password to nothing or just type the password one time each session. |
Yes, I now understand that the two keyring prompt at startup (should have been one) is an Ubuntu issue. But I still get password only prompts for app installations through snap store or opening timeshift, which was in 22.04, could be authorised by Howdy too. |
I was able to get it working by doing the following: Add repo: Update: Install: First install should error, install again: Create link: Tell cli.py the new working directory: add after “import sys” Install numpy: Install opencv: Install dlib: Install v4-utils: Set device path in howdy config.ini: Edit sudo file to use howdy: After #%PAM-1.0 comment
Fix pam: Above config.read(os.path.dirname(os.path.abspath(file)) + "/config.ini") add:
Get rid of any info logs if you are seeing them by adding this to your ~/.bashrc: Hope this helps! |
For the path you did, just to change as follows that would be more better:
|
I have done all this and still get log message No module named "ConfigParser", how to fix this? |
I got a module not found for |
How to fix these errors? /lib/security/howdy/compare.py:57: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
"Date: " + datetime.datetime.utcnow().strftime("%Y/%m/%d %H:%M:%S UTC"),
Traceback (most recent call last):
File "/lib/security/howdy/compare.py", line 175, in <module>
make_snapshot("FAILED")
File "/lib/security/howdy/compare.py", line 55, in make_snapshot
snapshot.generate(snapframes, [
File "/usr/lib/security/howdy/snapshot.py", line 54, in generate
os.makedirs(abpath + "/snapshots")
File "<frozen os>", line 225, in makedirs
PermissionError: [Errno 13] Permission denied: '/usr/lib/security/howdy/snapshots'
Unknown error: 1 |
@JoelScarinius you can trun off snapshots in the config file and should fix the issue |
Thanks @Cerkal, now it works as it should! |
I have been folk for fix in Ubuntu 24.04, please try:
Content of md file for help install howdy:Install for ubuntu 24.04 KDE1. install dlib by source# install lib
sudo apt-get update
sudo apt-get install build-essential cmake libgtk-3-dev libboost-all-dev
sudo apt-get update && sudo apt-get install -y python3 python3-pip python3-setuptools python3-wheel cmake make build-essential libpam0g-dev libinih-dev libevdev-dev python3-dev libopencv-dev
# clone
git clone https://github.com/davisking/dlib.git
cd dlib
python3.11 -m venv venv
python3.11 -m venv venv
./venv/bin/python -m build --wheel
./venv/bin/python -m build --wheel
# install dlib which buit:
./venv/bin/pip install dist/dlib-19.24.99-cp312-cp312-linux_x86_64.whl
# test module
sudo python3.11 show dlib
2. install howdy
sudo apt install howdy
# install some lib that lost when `apt install howdy` error before this step:
python3.11 -m pip install numpy opencv-python-headless opencv-python ConfigParser config:sudo cp howdy.sh /lib/security/howdy/howdy
chmod +x /lib/security/howdy/howdy
sudo ln /lib/security/howdy/howdy /usr/local/bin/howdy
sudo cp -f compare.py /lib/security/howdy/
sudo cp -f pam.py /lib/security/howdy/
## edit /lib/security/howdy/config.ini for video device and something for work
edit /etc/pam.dcat /etc/pam.d/sudo
#%PAM-1.0
# Set up user limits from /etc/security/limits.conf.
### for howdy face detection
auth sufficient pam_python.so /lib/security/howdy/pam.py cat /etc/pam.d/sddm | head -n 5
#%PAM-1.0
# added howdy
auth sufficient pam_python.so /lib/security/howdy/pam.py
cat /etc/pam.d/common-auth
## for howdy face detection
auth [success=1 default=ignore] pam_python.so /lib/security/howdy/pam.py Testing# add face
sudo howdy add
# test video detect
sudo howdy test
# test login
sudo <some command > |
It should be |
Is there a way to skip the "login" button like in Ubuntu 22 / i.e. popos? |
Thanks, @simonchen! I actually had to do this to get it to finally work for me. Thank you so much! |
I really need help. I am very frustrated.
Ubuntu 24.04 and Howdy is a major pain in the ass for me.
I use the release version 2.6.1 and I use Ubuntu 24.04 with all updates and upgrades until today.
This is what I did so far:
But I got
error: externally-managed-environment ... bla bla ...
I had to do
Then it installed some more files and said it has finished.
Yes! (so I thought)
I tried to start howdy, but no howdy was found
sudo ln /lib/security/howdy/cli.py /usr/local/bin/howdy
fixed this issue.I tried to start howdy again, but unfortunately I was welcomed with
ModuleNotFoundError: No module named 'cli'
Well, I did
sudo nano /usr/lib/security/howdy/cli.py
and I addedsys.path.append('/lib/security/howdy')
in cli.py after import sysFixed!!
But then - really??!! - I got
ModuleNotFoundError: No module named 'dlib'
I had to do
sudo pip install dlib --break-system-packages
to overcome this.I hated to possibly break system packages but it seemed there was no other way.
Finally I called
sudo howdy config
and added the correct path to the video devicesudo howdy add
worked fine and it added my facesudo howdy test
worked. However, my face had a red circle. Don't know if this is an issue.I checked
sudo-pam-auth-update
and howdy is selected. OK.I checked
sudo nano /etc/pam.d/common-auth
and this is inside:Looks good.
Someone said you have to:
sudo chmod -R a+x /lib/security/howdy
which I did.(Not sure if this is necessary, but it won't hurt)
I checked the log file and
sudo cat /var/log/auth.log
said that there is an issue with ConfigParserSo I patched /usr/lib/security/howdy/pam.py like this:
And now ladies and gentlemen I am at the end of my capabilities.
Howdy does not start at login and I still have to manually enter my password.
Any other ideas?
The text was updated successfully, but these errors were encountered: