Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi Chris and others, On Mon, 2021-03-08 at 22:38 -0700, Chris Murphy wrote: > Do any of the bugs in this thread need to be proposed as blockers or > freeze exceptions, for beta or final? > > This looks like it might have been lost in process because it got > closed due to a fix for Fedora 33

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Do any of the bugs in this thread need to be proposed as blockers or freeze exceptions, for beta or final? This looks like it might have been lost in process because it got closed due to a fix for Fedora 33 instead of staying open until the F34 fix goes stable.

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Matthew Miller wrote: > On Sun, Mar 07, 2021 at 10:26:50AM +0100, Björn Persson wrote: > > > It can, but most people don't have a good setup for even local mail > > > delivery. Out of the box, we don't really do anything useful. > > It wouldn't take much. Install Postfix, and when Anaconda

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Sun, 2021-03-07 at 08:55 -0600, Michael Catanzaro wrote: > On Sun, Mar 7, 2021 at 11:28 am, Björn Persson > wrote: > >  Do the ECC-less Intel processors also lack > > all other MCE support? > > No, ABRT used to regularly warn me about thermal events from MCE when > I > didn't have a good

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Dnia Sun, Mar 07, 2021 at 12:55:21PM -0500, Matthew Miller napisał(a): > On Sun, Mar 07, 2021 at 10:26:50AM +0100, Björn Persson wrote: > > > It can, but most people don't have a good setup for even local mail > > > delivery. Out of the box, we don't really do anything useful. > > It wouldn't take

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Sun, Mar 07, 2021 at 10:26:50AM +0100, Björn Persson wrote: > > It can, but most people don't have a good setup for even local mail > > delivery. Out of the box, we don't really do anything useful. > It wouldn't take much. Install Postfix, and when Anaconda creates the > first user account,

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Sun, Mar 07, 2021 at 10:00:56AM +0100, Hans de Goede wrote: > > running commands to look back in the logs for problems is a common > > diagnostic step. This could be better, of course. > But for MCE exceptions, specifically ECC errors I would expect the kernel to > log these > through dmesg

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Sun, Mar 7, 2021 at 11:28 am, Björn Persson wrote: Do the ECC-less Intel processors also lack all other MCE support? No, ABRT used to regularly warn me about thermal events from MCE when I didn't have a good enough CPU fan. That was an Intel machine. I fixed it by replacing the CPU

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Sun, Mar 07, 2021 at 10:00:56AM +0100, Hans de Goede wrote: > Hi, > > On 3/5/21 4:17 PM, Matthew Miller wrote: > > On Fri, Mar 05, 2021 at 03:05:00PM +0100, Hans de Goede wrote: > >>> mcelog.service loaded active running > >>> Machine Check Exception Logging

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hans de Goede wrote: > But for MCE exceptions, specifically ECC errors I would expect the kernel to > log these > through dmesg anyways and then the mcelog service has very little added value > IMHO > (I have no experience with machines with ECC RAM). > > Esp. given that ECC RAM is something

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Matthew Miller wrote: > On Fri, Mar 05, 2021 at 05:12:34PM +0100, Tomasz Torcz wrote: > > smartd even sends emails – that's how I was informed > > about one of my disks dying, few weeks ago, I thought it would send email, but then I noticed that it's started with "--capabilities", which breaks

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On 3/5/21 4:17 PM, Matthew Miller wrote: > On Fri, Mar 05, 2021 at 03:05:00PM +0100, Hans de Goede wrote: >>> mcelog.service loaded active running >>> Machine Check Exception Logging Daemon >> This is another one for which it is questionable to have it

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Sat, Mar 06, 2021 at 01:21:15PM -0500, Matthew Miller wrote: > On Sat, Mar 06, 2021 at 06:04:33PM +, Zbigniew Jędrzejewski-Szmek wrote: > > Maybe we could make this work with some filter list. Right now there's > > just *so* much noise. But a lot of it is repeatable. We want/need to keep >

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Sat, Mar 06, 2021 at 06:04:33PM +, Zbigniew Jędrzejewski-Szmek wrote: > Maybe we could make this work with some filter list. Right now there's > just *so* much noise. But a lot of it is repeatable. We want/need to keep > the warnings for developers, but for users, we could just show

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Sat, Mar 06, 2021 at 12:00:39PM -0500, Matthew Miller wrote: > On Fri, Mar 05, 2021 at 05:25:40PM +, Zbigniew Jędrzejewski-Szmek wrote: > > Once we reach the noble goal of having 0 warnings during boot by default, > > we could just issue a notification whenever anything pops up. We do that

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Fri, Mar 05, 2021 at 05:25:40PM +, Zbigniew Jędrzejewski-Szmek wrote: > Once we reach the noble goal of having 0 warnings during boot by default, > we could just issue a notification whenever anything pops up. We do that > for kernel oops already. Right??? It might be worthwhile sometime

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Fri, 2021-03-05 at 18:28 +, Tom Seewald wrote: > > Could you modify fprintd.service, to set G_MESSAGES_DEBUG=all[1] > > and > > then grab a log of that? > > Here's what I see from systemctl status fprintd.service: > > Getting authorization to perform Polkit action >

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

> Could you modify fprintd.service, to set G_MESSAGES_DEBUG=all[1] and > then grab a log of that? Here's what I see from systemctl status fprintd.service: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify Authorization granted to AuthenTec AES2550/AES2810 to

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Fri, 2021-03-05 at 17:20 +, Tom Seewald wrote: > > Can you please provide output of `authselect current`? > # authselect current > Profile ID: sssd > Enabled features: > - with-fingerprint > - with-silent-lastlog > > # authselect check > Current configuration is valid. > > I have verified

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Fri, Mar 05, 2021 at 11:35:37AM -0500, Matthew Miller wrote: > On Fri, Mar 05, 2021 at 05:12:34PM +0100, Tomasz Torcz wrote: > > > > This is another one for which it is questionable to have it running, or > > > > is this a machine with > > > > ECC RAM ? And even then I'm not sure if it adds a

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

> Can you please provide output of `authselect current`? # authselect current Profile ID: sssd Enabled features: - with-fingerprint - with-silent-lastlog # authselect check Current configuration is valid. I have verified that both sssd and fprintd are running, and are not logging any errors.

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Fri, Mar 05, 2021 at 05:12:34PM +0100, Tomasz Torcz wrote: > > > This is another one for which it is questionable to have it running, or > > > is this a machine with > > > ECC RAM ? And even then I'm not sure if it adds a lot of value, or if > > > just like smartd it > > > just logs some

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Dnia Fri, Mar 05, 2021 at 10:17:17AM -0500, Matthew Miller napisał(a): > On Fri, Mar 05, 2021 at 03:05:00PM +0100, Hans de Goede wrote: > > > mcelog.service loaded active running > > > Machine Check Exception Logging Daemon > > This is another one for which it is

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Fri, Mar 05, 2021 at 03:05:00PM +0100, Hans de Goede wrote: > > mcelog.service loaded active running > > Machine Check Exception Logging Daemon > This is another one for which it is questionable to have it running, or is > this a machine with > ECC RAM ? And

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Fri, Mar 05, 2021 at 12:56:57PM +, Zbigniew Jędrzejewski-Szmek wrote: > I think there's still plenty of stuff to improve that will apply everywhere. > homed, alsactl, geoclue, colord just shouldn't need to be there all the time. firewalld, too. For most users it's just putting a static

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On 3/5/21 1:56 PM, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Mar 04, 2021 at 07:50:11PM +0100, Hans de Goede wrote: >>> I am not sure about this. What services are you seeing which are >>> extraneous? I do see ps aux is going on miles and miles, but of the 218 >>> processes I see from

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On 3/5/21 11:59 AM, Pavel Březina wrote: > On 3/4/21 5:11 PM, Hans de Goede wrote: >> Hi, >> >> On 3/4/21 11:50 AM, Pavel Březina wrote: >>> On 3/3/21 6:11 PM, Hans de Goede wrote: Hi, On 3/2/21 5:20 PM, Pavel Březina wrote: > On 3/2/21 4:25 PM, Ray Strode wrote: >> Hi,

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Thu, Mar 04, 2021 at 07:50:11PM +0100, Hans de Goede wrote: > > I am not sure about this. What services are you seeing which are > > extraneous? I do see ps aux is going on miles and miles, but of the 218 > > processes I see from startup time on my workstation, I see 165 of them are > >

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On 3/4/21 9:11 PM, Tom Seewald wrote: On rawhide I upgraded to authselect-1.2.2-3.fc35 yet I am still encountering the issue of gdm repeatedly complaining about authentication via fingerprint. I've checked and authselect is using the 'ssd' profile. Can you please provide output of

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On 3/4/21 5:11 PM, Hans de Goede wrote: Hi, On 3/4/21 11:50 AM, Pavel Březina wrote: On 3/3/21 6:11 PM, Hans de Goede wrote: Hi, On 3/2/21 5:20 PM, Pavel Březina wrote: On 3/2/21 4:25 PM, Ray Strode wrote: Hi, Ahh, okay. On Tue, Mar 2, 2021 at 9:31 AM Hans de Goede wrote: sudo

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

> I think there's probably three things: Great summary Matthew, a big +1 from the peanut gallery. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Thu, Mar 04, 2021 at 02:43:26PM -0500, Stephen John Smoogen wrote: > > I have actually been considering doing a Fedora workstation light spin for > > budget x86 machines with 1G / 2G of RAM and an eMMC. > > > I agree and think that a spin would be needed. There is going to be an > audience for

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

> The problem is that every time this conversation starts... you end up with > 200 people all wanting some other program to be stopped/not run/removed but > not something they actually think is essential. And instead we end up > finding we needed to add one or two things because a lot of users

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On rawhide I upgraded to authselect-1.2.2-3.fc35 yet I am still encountering the issue of gdm repeatedly complaining about authentication via fingerprint. I've checked and authselect is using the 'ssd' profile. ___ devel mailing list --

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Thu, 4 Mar 2021 at 13:50, Hans de Goede wrote: > Hi, snip > > IIRC a default GNOME workstation install consumes about 700-800MB of RAM > when logged into the desktop on a 1G RAM system. After I've done a bunch of > hacks / tweaks to remove a long list of unnecessary (1) processes I have

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On 3/4/21 12:55 PM, Pavel Březina wrote: > On 3/3/21 11:02 AM, Pavel Březina wrote: >> On 3/2/21 10:21 PM, Ray Strode wrote: >>> Hi, >>> >>> On Tue, Mar 2, 2021, 11:20 AM Pavel Březina wrote: Can you reiterate the problem? The snippet above don't tell me much. >>> Sorry, let me

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

> Given that I can halve the base processes RAM set with some hacks I > think that it is fair to say that there are still way too much things > starting by default. > > I have actually been considering doing a Fedora workstation light spin > for budget x86 machines with 1G / 2G of RAM and an eMMC.

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On 3/4/21 5:38 PM, Stephen John Smoogen wrote: > > > On Thu, 4 Mar 2021 at 11:21, Hans de Goede > wrote: > > Hi, > > > > It has very limited functionality by design. If you do not want to use > SSSD, you can keep using sssd profile and just disable

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On Thu, 4 Mar 2021 at 11:21, Hans de Goede wrote: > Hi, > > > > It has very limited functionality by design. If you do not want to use > SSSD, you can keep using sssd profile and just disable the service. It will > keep working. The minimal profile is there for users that also want to > remove

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On 3/4/21 11:50 AM, Pavel Březina wrote: > On 3/3/21 6:11 PM, Hans de Goede wrote: >> Hi, >> >> On 3/2/21 5:20 PM, Pavel Březina wrote: >>> On 3/2/21 4:25 PM, Ray Strode wrote: Hi, Ahh, okay. On Tue, Mar 2, 2021 at 9:31 AM Hans de Goede wrote: > sudo authselect

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On 3/3/21 11:02 AM, Pavel Březina wrote: On 3/2/21 10:21 PM, Ray Strode wrote: Hi, On Tue, Mar 2, 2021, 11:20 AM Pavel Březina wrote: Can you reiterate the problem? The snippet above don't tell me much. Sorry, let me summarize (but also see Benjamin's email). Right now, if fingerprint auth

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On 3/3/21 6:11 PM, Hans de Goede wrote: Hi, On 3/2/21 5:20 PM, Pavel Březina wrote: On 3/2/21 4:25 PM, Ray Strode wrote: Hi, Ahh, okay. On Tue, Mar 2, 2021 at 9:31 AM Hans de Goede wrote: sudo authselect select minimal sudo authselect apply-changes Which results in the following

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On 3/2/21 5:20 PM, Pavel Březina wrote: > On 3/2/21 4:25 PM, Ray Strode wrote: >> Hi, >> >> Ahh, okay. >> >> On Tue, Mar 2, 2021 at 9:31 AM Hans de Goede wrote: >>> sudo authselect select minimal >>> sudo authselect apply-changes >>> >>> Which results in the following

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On 3/2/21 10:21 PM, Ray Strode wrote: Hi, On Tue, Mar 2, 2021, 11:20 AM Pavel Březina wrote: Can you reiterate the problem? The snippet above don't tell me much. Sorry, let me summarize (but also see Benjamin's email). Right now, if fingerprint auth is disabled in authselect, it's not

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On Tue, Mar 2, 2021, 11:20 AM Pavel Březina wrote: > Can you reiterate the problem? The snippet above don't tell me much. Sorry, let me summarize (but also see Benjamin's email). Right now, if fingerprint auth is disabled in authselect, it's not disabling fingerprint auth at the graphical

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On Tue, 2021-03-02 at 15:31 +0100, Hans de Goede wrote: > On 3/1/21 9:15 PM, Ray Strode wrote: > > [...] > > > Any debugging options which I can enable somewhere to show the > > > pam_fprintd error ? > > you can put "debug" on the ends of the lines that say > > pam_fprintd.so > > in

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

On 3/2/21 4:25 PM, Ray Strode wrote: Hi, Ahh, okay. On Tue, Mar 2, 2021 at 9:31 AM Hans de Goede wrote: sudo authselect select minimal sudo authselect apply-changes Which results in the following /etc/pam.d/fingerprint-auth file: [hans@x1 linux]$ sudo cat /etc/pam.d/fingerprint-auth #

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, Ahh, okay. On Tue, Mar 2, 2021 at 9:31 AM Hans de Goede wrote: > sudo authselect select minimal > sudo authselect apply-changes > > Which results in the following /etc/pam.d/fingerprint-auth file: > > [hans@x1 linux]$ sudo cat /etc/pam.d/fingerprint-auth > # Generated by authselect on Tue

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On 3/1/21 9:15 PM, Ray Strode wrote: > Hi, > > On Sun, Feb 28, 2021 at 9:46 AM Hans de Goede wrote: >>> https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1683 >>> >>> seems like this is already in updates.

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On Sun, Feb 28, 2021 at 9:46 AM Hans de Goede wrote: > > https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1683 > > > > seems like this is already in updates. you definitely have the gnome-shell > > 40.beta

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On 2/27/21 9:16 PM, Ray Strode wrote: > Hi, > > On Sat, Feb 27, 2021, 2:56 PM Ray Strode > wrote: > > ah i think we need to pull in  > > https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1683 >

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

I'll add that I just hit this today on an old laptop running rawhide. I didn't spend much time debugging the problem, but I did not see any obvious errors being reported in the journal and simply disabling fprintd did not resolve the issue with gdm. Masking fprintd, as Hans noted, is the big

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

Hi, On Sat, Feb 27, 2021, 2:56 PM Ray Strode wrote: > ah i think we need to pull in > > https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1683 > seems like this is already in updates. you definitely have the gnome-shell 40.beta installed? could be a pam_fprintd is returning a

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

ah i think we need to pull in https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1683 Ray On Sat, Feb 27, 2021, 2:31 PM Hans de Goede wrote: > Hi Benjamin, Ray, > > I noticed this problem while dogfooding F34, I'm fully up2date as of today. > > Today's gdm update did help in making