Ask Your Question
2

Erroneous "failed login attempts" in gdm

asked 2014-01-28 10:44:32 -0600

mightyflea gravatar image

updated 2014-09-16 10:44:18 -0600

mether gravatar image

Hi all,

Whenever I log into my gnome session, gdm tells me there have been n failed login attempts since my last login; yet the last logins were all successful I am reasonably certain that my machine is not under constant attack, so I am wondering where these error messages come from. I thought I'd ask here first before opening a bug report.

Searching through the journal brought up nothing obvious to me, except for possibly lines like these: Jan 28 11:31:51 briar gdm[2594]: GdmManager: could not fetch uid of session 'c6': No such file or directory Jan 28 11:31:51 briar gdm[2594]: GdmSlave: could not fetch type of session 'c6': No such file or directory

Has anybody else seen behaviour like this, or knows what is up there?

edit retag flag offensive close merge delete

Comments

1

I have only messages about "Last login was...." but not for failed login attempts. Maybe a terminal failed login is rerecorded as well ? do you remember if you gave a wrong password via sudo or login as root user in terminal ?

NickTux gravatar imageNickTux ( 2014-01-28 13:27:39 -0600 )edit

Hi, thanks for the reply! I can rule out wrong passwords, because it just does not align with the amounts of failed attempts that gdm gives me.

I played around in a virtual machine a bit now and this is what I found: Directly after the install (Gnome desktop) everything was normal, after the update to the latest packages it still was. After I installed the xguest package the "failed login attempts" in gdm started to appear in the virtual machine also; so I can probably link it to xguest, or one of its dependencies. So I might play around with this some more and then maybe report it as a bug.

mightyflea gravatar imagemightyflea ( 2014-02-02 09:01:49 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
3

answered 2014-02-13 07:11:23 -0600

mightyflea gravatar image

updated 2014-02-27 17:23:44 -0600

Heh, answering my own question now. I was on the wrong track with blaming xguest; reverting the install did not change anything.

It seems I was bit by a bug in gdm and fingerprint authentication (which I do not use). here is the link to the bug: Bug 1047077

The workaround described there works for me, I quote it here: Finally it is fingerprint reader related, authconfig doesn't entirely disable fingerprint on gdm. I disabled it using dconf, in a new file: /etc/dconf/db/gdm.d/99-local

[org/gnome/login-screen]
enable-fingerprint-authentication=false

then running "dconf update"

Edit: This was only half the fix, as it turns out: I still had failed login counts correlated to the number of times I unlocked the screen saver.

So I installed dconf-editor and disabled fingerprint authentication not only on a system level (see above) but also in my own user session: In dconf-editor I navigated to Org - Gnome - login-screen and unchecked the enable-fingerprint-authentication check box.

This seems to have done the trick this time.

edit flag offensive delete link more

Comments

Hi I'm experiencing the same failed login messages but when I naviage to /etc/dconf/db/gdm.d there is no 99-local folder. Can you help me fix this? I downloaded d-config and disabled finger print authentication but I need to do the first part of your answer.

Penguins Have Knees gravatar imagePenguins Have Knees ( 2014-06-19 03:30:02 -0600 )edit

Sorry for the long time till I replied. Is this still relevant?

It did not exist on my machine either, I had to create it with the content from above in it.

I am actually going to turn on fingerprint authentication now, since in the bug report it now says the problem only exists when fingerprint authentication is turned on but no fingerprints have been enrolled.

mightyflea gravatar imagemightyflea ( 2014-11-22 03:34:37 -0600 )edit

Question Tools

3 followers

Stats

Asked: 2014-01-28 10:44:32 -0600

Seen: 2,263 times

Last updated: Feb 27 '14