First I removed kerberos auth, which did not seem to have had an effect.
Then I saw that fprintd was showing errors and fprintd-list was throwing the same error as in the logs.
I removed it and after that it worked.
So it seems like a bug in sssd related to fingerprint auth, when that is not working properly.
Regarding evdi - as you wrote, can be addressed separately. As I wrote , it does NOT work properly for me, not the beta driver, not even on 5.13 with beta driver. I just installed 5.12 kernel and latest release driver because the beta does not work properly on my system - I use a D6000 Dell dock.
Regarding this bug - I will try to see if I can get frintd to work. I still have Ubuntu sessions showing that do not work, not sure where they came from, this is even after I purged gnome gnome-shell and gnome-session. can login now with gdm3 and gnome session.
I tracked down the cause, it has to do with sssd and how gdm3 handles it. /bugzilla. redhat. com/show_ bug.cgi? id=1534873
Similar issue:
https:/
First I removed kerberos auth, which did not seem to have had an effect.
Then I saw that fprintd was showing errors and fprintd-list was throwing the same error as in the logs.
I removed it and after that it worked.
So it seems like a bug in sssd related to fingerprint auth, when that is not working properly.
Regarding evdi - as you wrote, can be addressed separately. As I wrote , it does NOT work properly for me, not the beta driver, not even on 5.13 with beta driver. I just installed 5.12 kernel and latest release driver because the beta does not work properly on my system - I use a D6000 Dell dock.
Regarding this bug - I will try to see if I can get frintd to work. I still have Ubuntu sessions showing that do not work, not sure where they came from, this is even after I purged gnome gnome-shell and gnome-session. can login now with gdm3 and gnome session.
Is there anything else you need to pursue this ?