Nothing is happening on Fedora 36 and Gnome #711

RenardFute · 2022-10-12T21:33:57Z

There is no error shown, because it's seams like nothing is running.
I well added my face, howdy test works but when I do sudo or on the lock screen nothing is happening.

I've searched for similar issues and already gave all permissions to howdy files (777), restarted my computer and reinstalling everything.

Linux distribution : Fedora 36

Howdy version : 2.6.1

RenardFute · 2022-10-13T08:27:43Z

There is no mention of howdy in my journalctl SYSLOG_FACILITY=10

hys0star · 2022-10-23T14:04:36Z

I have the same problem.

yi-ge · 2022-10-28T14:21:21Z

I have the same problem.

boltgolt · 2022-10-31T14:38:34Z

@RenardFute @hys0star @yi-ge anything in tail /var/log/auth.log?

RenardFute · 2022-10-31T16:06:00Z

There is no auth.log on fedora that's why I said journalctl SYSLOG_FACILITY=10 was empty.

yi-ge · 2022-11-01T09:38:31Z

@boltgolt The problem has been resolved. python3 environment config caused the error.

More: https://www.wyr.me/post/702

swinzy · 2022-11-03T05:57:46Z

@boltgolt The problem has been resolved. python3 environment config caused the error.

More: https://www.wyr.me/post/702

I've tried the python3 solution but have got no luck.

swinzy · 2022-11-08T03:06:24Z

To everyone using Fedora 36 and GNOME,
I've solved the issue on my Surface Laptop Studio.
To be clear, I was always able to create a face model and was able to sudo howdy test.
Basically I just followed this link: https://copr.fedorainfracloud.org/coprs/principis/howdy/

In summary, this is what I did:

Give execute permission to everyone (not sure if needed)

sudo chmod -R o+x /lib64/security/howdy

Configure `sudo` to use Howdy

Open /etc/pam.d/sudo and add these to the top:

auth       sufficient   pam_python.so /lib64/security/howdy/pam.py

Configure gdm (if you're using GNOME) to use Howdy to login

Open /etc/pam.d/gdm-password and add these to the second line (after the first line):

auth        sufficient    pam_python.so /lib64/security/howdy/pam.py

Configure SELinux to allow Howdy to access cameras when logging in

(To me, otherwise it will show "unknown error 1" at login)
Create a file at ~ named howdy.te and add the following codes:

module howdy 1.0;

require {
    type lib_t;
    type xdm_t;
    type v4l_device_t;
    type sysctl_vm_t;
    class chr_file map;
    class file { create getattr open read write };
    class dir add_name;
}

#============= xdm_t ==============
allow xdm_t lib_t:dir add_name;
allow xdm_t lib_t:file { create write };
allow xdm_t sysctl_vm_t:file { getattr open read };
allow xdm_t v4l_device_t:chr_file map;

Then execute the following command:

checkmodule -M -m -o howdy.mod howdy.te
semodule_package -o howdy.pp -m howdy.mod
semodule -i howdy.pp

Hopefully this helps.
Stephen

RenardFute · 2022-11-08T08:40:53Z

To everyone using Fedora 36 and GNOME, I've solved the issue on my Surface Laptop Studio. To be clear, I was always able to create a face model and was able to sudo howdy test. Basically I just followed this link: https://copr.fedorainfracloud.org/coprs/principis/howdy/

In summary, this is what I did:

Give execute permission to everyone (not sure if needed)

sudo chmod -R o+x /lib64/security/howdy

Configure sudo to use Howdy

Open /etc/pam.d/sudo and add these to the top:
auth       sufficient   pam_python.so /lib64/security/howdy/pam.py
Configure gdm (if you're using GNOME) to use Howdy to login

Open /etc/pam.d/gdm-password and add these to the second line (after the first line):
auth        sufficient    pam_python.so /lib64/security/howdy/pam.py
Configure SELinux to allow Howdy to access cameras when logging in

(To me, otherwise it will show "unknown error 1" at login) Create a file at ~ named howdy.te and add the following codes:
module howdy 1.0;

require {
    type lib_t;
    type xdm_t;
    type v4l_device_t;
    type sysctl_vm_t;
    class chr_file map;
    class file { create getattr open read write };
    class dir add_name;
}

#============= xdm_t ==============
allow xdm_t lib_t:dir add_name;
allow xdm_t lib_t:file { create write };
allow xdm_t sysctl_vm_t:file { getattr open read };
allow xdm_t v4l_device_t:chr_file map;
Then execute the following command:
checkmodule -M -m -o howdy.mod howdy.te
semodule_package -o howdy.pp -m howdy.mod
semodule -i howdy.pp
Hopefully this helps. Stephen

Thanks you so much it worked instantly after doing this !

ChrisErnovsky · 2022-11-08T22:18:00Z

@m1nicrusher, HUGE thanks for this solution!
Works like a charm (Fedora 37 beta, Gnome 43, Lenovo IdeaPad 5 Pro camera + IR).

swinzy · 2022-11-09T14:29:23Z

For the convenience of anyone in the future, I made a bash script for Fedora + GNOME.
https://gist.github.com/m1nicrusher/35e79b20553c8863e0c642f8d801da7f
Feel free to point out any error as I have minimal experience working with bash scripts.

Stephen

RenardFute · 2022-11-09T15:43:28Z

For the convenience of anyone in the future, I made a bash script for Fedora + GNOME. https://gist.github.com/m1nicrusher/35e79b20553c8863e0c642f8d801da7f Feel free to point out any error as I have minimal experience working with bash scripts.

Stephen

Maybe a pr would be helpful for futures users

swinzy · 2022-11-11T16:17:35Z

As for this:

Maybe a pr would be helpful for futures users

So far it seems like the issue is Fedora specific, and I see no similar issue report on other distros. So I'm not sure if it's needed to edit the code.
Plus, I believe the author is (or is planning to) making a newer GUI version. Maybe the fix could be applied then.

EDIT: For the moment I've added this issue in our Wiki. Feel free to improve.

Cheers
Stephen

RedBoardDev · 2022-12-22T10:41:46Z

I have the same problem but nothing work

swinzy · 2022-12-23T10:37:55Z

I have the same problem but nothing work

Have you tried the above script? 👇

https://gist.github.com/m1nicrusher/35e79b20553c8863e0c642f8d801da7f

RedBoardDev · 2022-12-23T12:14:11Z

I have the same problem but nothing work

Have you tried the above script? point_down

https://gist.github.com/m1nicrusher/35e79b20553c8863e0c642f8d801da7f

I have try and I have the same. Nothing working and my webcam is off when I want to unlock

RenardFute · 2022-12-23T18:33:49Z

What does it do when you try howdy test

RedBoardDev · 2022-12-23T18:38:50Z

What does it do when you try howdy test

It shows me my face and what the webcam sees. The webcam flashes red, and the iameg on the webcam also flashes. She is black and white

swinzy · 2022-12-24T10:50:17Z

What does it do when you try howdy test

It shows me my face and what the webcam sees. The webcam flashes red, and the iameg on the webcam also flashes. She is black and white

Seems like the webcam is configured correctly and working fine.

RedBoardDev · 2022-12-24T12:13:55Z

Yes, so I don't know where is the problem. My webcam is not active when I want to unlock my computer. But when I try howdy test, I see the light

RenardFute · 2022-12-24T18:24:57Z

Yes, so I don't know where is the problem. My webcam is not active when I want to unlock my computer. But when I try howdy test, I see the light

It might come from a permission issue check that there is at least execute permissions for every one.
I personally put all the howdy directory as 777 but I think it's not recommended 🤷‍♂️

maxjamchuk · 2023-06-01T15:17:48Z

I've tried all ways above, however it still not working.

howdy test shows my IR camera, but sudo -i still asks password.

I noticed that I just don't have /usr/lib64/security/pam_python.so file.

PS
journalctl SYSLOG_FACILITY=10 shows:

polkitd[824]: Loading rules from directory /etc/polkit-1/rules.d
polkitd[824]: Loading rules from directory /usr/share/polkit-1/rules.d
polkitd[824]: Finished loading, compiling and executing 15 rules
polkitd[824]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
(systemd)[1083]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Could not activate remote peer: activation request failed: unknown unit.
(systemd)[1083]: pam_unix(systemd-user:session): session opened for user gdm(uid=42) by (uid=0)
gdm-launch-environment][1051]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=42) by (uid=0)
polkitd[824]: Registered Authentication Agent for unix-session:c1 (system bus name :1.35 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
gdm-password][1894]: PAM unable to dlopen(/usr/lib64/security/pam_python.so): /usr/lib64/security/pam_python.so: cannot open shared object file: No such file or directory
gdm-password][1894]: PAM adding faulty module: /usr/lib64/security/pam_python.so
gdm-password][1894]: gkr-pam: unable to locate daemon control file
gdm-password][1894]: gkr-pam: stashed password to try later in open session
(systemd)[1919]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Could not activate remote peer: activation request failed: unknown unit.
(systemd)[1919]: pam_unix(systemd-user:session): session opened for user maks(uid=1000) by (uid=0)
gdm-password][1894]: pam_unix(gdm-password:session): session opened for user maks(uid=1000) by (uid=0)
gdm-password][1894]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
polkitd[824]: Registered Authentication Agent for unix-session:2 (system bus name :1.89 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
gdm-launch-environment][1051]: pam_unix(gdm-launch-environment:session): session closed for user gdm
polkitd[824]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.35, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
sudo[5691]: PAM unable to dlopen(/usr/lib64/security/pam_python.so): /usr/lib64/security/pam_python.so: cannot open shared object file: No such file or directory
sudo[5691]: PAM adding faulty module: /usr/lib64/security/pam_python.so
sudo[5691]:     maks : PWD=/root ; USER=root ; COMMAND=/bin/bash
sudo[5691]: pam_unix(sudo-i:session): session opened for user root(uid=0) by (uid=1000)
sudo[5691]: pam_unix(sudo-i:session): session closed for user root

stephanlamoureux · 2023-07-02T21:03:50Z

Is there a workaround for KDE? I used the bash script previously for GNOME but now I can't find anything for Plasma.

cachapa · 2023-07-27T09:06:49Z

I tried all configurations described here and managed to get things mostly working:

Executing sudo on a terminal works
1st login after rebooting works (it still asks to unlock the keyring after logging in, but that's ok)

However I can't unlock the screen after locking it. The camera never turns on and "Unknown error: 1" appear below the password field.

It also doesn't seem to have any effect when unlocking Settings (i.e. Users, Printers). The camera doesn't turn on and nothing is shown in the UI.

This is Fedora 38 / Gnome 44.3

1040170566 · 2024-05-14T14:23:39Z

To everyone using Fedora 36 and GNOME, I've solved the issue on my Surface Laptop Studio. To be clear, I was always able to create a face model and was able to sudo howdy test. Basically I just followed this link: https://copr.fedorainfracloud.org/coprs/principis/howdy/

In summary, this is what I did:

Give execute permission to everyone (not sure if needed)

sudo chmod -R o+x /lib64/security/howdy

Configure sudo to use Howdy

Open /etc/pam.d/sudo and add these to the top:
auth       sufficient   pam_python.so /lib64/security/howdy/pam.py
Configure gdm (if you're using GNOME) to use Howdy to login

Open /etc/pam.d/gdm-password and add these to the second line (after the first line):
auth        sufficient    pam_python.so /lib64/security/howdy/pam.py
Configure SELinux to allow Howdy to access cameras when logging in

(To me, otherwise it will show "unknown error 1" at login) Create a file at ~ named howdy.te and add the following codes:
module howdy 1.0;

require {
    type lib_t;
    type xdm_t;
    type v4l_device_t;
    type sysctl_vm_t;
    class chr_file map;
    class file { create getattr open read write };
    class dir add_name;
}

#============= xdm_t ==============
allow xdm_t lib_t:dir add_name;
allow xdm_t lib_t:file { create write };
allow xdm_t sysctl_vm_t:file { getattr open read };
allow xdm_t v4l_device_t:chr_file map;
* Then execute the following command:
checkmodule -M -m -o howdy.mod howdy.te
semodule_package -o howdy.pp -m howdy.mod
semodule -i howdy.pp
Hopefully this helps. Stephen

Verrrrrrrry good! I tried so many methods but only yours works. Thank you! Mine is Ubuntu22.04.4 and Gnome.

Muhd-Mairaj · 2024-07-18T23:10:47Z

@stephanlamoureux

Is there a workaround for KDE? I used the bash script previously for GNOME but now I can't find anything for Plasma.

I got it to work on kde by changing the GDM_CFG="/etc/pam.d/gdm-password" in the script to GDM_CFG="/etc/pam.d/kde".

It may be worth noting that running the script as provided did solve all other related issues, but it was not working on login. Changing that one line also fixed that issue.

Here is an modifed script for fedora with kde:
https://gist.github.com/Muhd-Mairaj/52e6f8d16b42c64c5ac61ea89987a1e5

boltgolt added bug Something isn't working distro: fedora labels Oct 31, 2022

zsxboli mentioned this issue Jan 12, 2023

Nothing has happend on Debian Testing #742

Closed

saidsay-so added the v2 Old version of Howdy (2.*) label Apr 13, 2024

mihailigoshin mentioned this issue Jul 21, 2024

Fedora 40 Unknown error: 1 #942

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Nothing is happening on Fedora 36 and Gnome #711

Nothing is happening on Fedora 36 and Gnome #711

RenardFute commented Oct 12, 2022

RenardFute commented Oct 13, 2022

hys0star commented Oct 23, 2022

yi-ge commented Oct 28, 2022

boltgolt commented Oct 31, 2022

RenardFute commented Oct 31, 2022

yi-ge commented Nov 1, 2022

swinzy commented Nov 3, 2022 •

edited

Loading

swinzy commented Nov 8, 2022 •

edited

Loading

RenardFute commented Nov 8, 2022

Give execute permission to everyone (not sure if needed)

Configure `sudo` to use Howdy

Configure gdm (if you're using GNOME) to use Howdy to login

Configure SELinux to allow Howdy to access cameras when logging in

ChrisErnovsky commented Nov 8, 2022

swinzy commented Nov 9, 2022

RenardFute commented Nov 9, 2022

swinzy commented Nov 11, 2022 •

edited

Loading

RedBoardDev commented Dec 22, 2022

swinzy commented Dec 23, 2022

RedBoardDev commented Dec 23, 2022

RenardFute commented Dec 23, 2022

RedBoardDev commented Dec 23, 2022

swinzy commented Dec 24, 2022

RedBoardDev commented Dec 24, 2022 •

edited

Loading

RenardFute commented Dec 24, 2022

maxjamchuk commented Jun 1, 2023

stephanlamoureux commented Jul 2, 2023

cachapa commented Jul 27, 2023

1040170566 commented May 14, 2024

Give execute permission to everyone (not sure if needed)

Configure `sudo` to use Howdy

Configure gdm (if you're using GNOME) to use Howdy to login

Configure SELinux to allow Howdy to access cameras when logging in

Muhd-Mairaj commented Jul 18, 2024 •

edited

Loading

Nothing is happening on Fedora 36 and Gnome #711

Nothing is happening on Fedora 36 and Gnome #711

Comments

RenardFute commented Oct 12, 2022

RenardFute commented Oct 13, 2022

hys0star commented Oct 23, 2022

yi-ge commented Oct 28, 2022

boltgolt commented Oct 31, 2022

RenardFute commented Oct 31, 2022

yi-ge commented Nov 1, 2022

swinzy commented Nov 3, 2022 • edited Loading

swinzy commented Nov 8, 2022 • edited Loading

Give execute permission to everyone (not sure if needed)

Configure sudo to use Howdy

Configure gdm (if you're using GNOME) to use Howdy to login

Configure SELinux to allow Howdy to access cameras when logging in

RenardFute commented Nov 8, 2022

Give execute permission to everyone (not sure if needed)

Configure sudo to use Howdy

Configure gdm (if you're using GNOME) to use Howdy to login

Configure SELinux to allow Howdy to access cameras when logging in

ChrisErnovsky commented Nov 8, 2022

swinzy commented Nov 9, 2022

RenardFute commented Nov 9, 2022

swinzy commented Nov 11, 2022 • edited Loading

RedBoardDev commented Dec 22, 2022

swinzy commented Dec 23, 2022

RedBoardDev commented Dec 23, 2022

RenardFute commented Dec 23, 2022

RedBoardDev commented Dec 23, 2022

swinzy commented Dec 24, 2022

RedBoardDev commented Dec 24, 2022 • edited Loading

RenardFute commented Dec 24, 2022

maxjamchuk commented Jun 1, 2023

stephanlamoureux commented Jul 2, 2023

cachapa commented Jul 27, 2023

1040170566 commented May 14, 2024

Give execute permission to everyone (not sure if needed)

Configure sudo to use Howdy

Configure gdm (if you're using GNOME) to use Howdy to login

Configure SELinux to allow Howdy to access cameras when logging in

Muhd-Mairaj commented Jul 18, 2024 • edited Loading

swinzy commented Nov 3, 2022 •

edited

Loading

swinzy commented Nov 8, 2022 •

edited

Loading

Configure `sudo` to use Howdy

Configure `sudo` to use Howdy

swinzy commented Nov 11, 2022 •

edited

Loading

RedBoardDev commented Dec 24, 2022 •

edited

Loading

Configure `sudo` to use Howdy

Muhd-Mairaj commented Jul 18, 2024 •

edited

Loading