Arch Linux

Mr. Shell

Member

Registered: 2012-03-08

Posts: 4

systemd-login trying to login with all keyboard input

Hello,

I'm using LightDM-GTK3 and XFCE4 and an up-to-date ArchLinux. I did observe in journalctl that system-login produces many errors. It seems that it tries to login with every (!) keyboard input after I've logged into the machine. And I mean every keyboard input, even URL's from Firefox, also all input in Bash, etc.

Example after using the Bash:

May 20 09:47:01 thinkpad login[1819]: pam_unix(login:auth): check pass; user unknown
May 20 09:47:01 thinkpad login[1819]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost=
May 20 09:47:03 thinkpad login[1819]: FAILED LOGIN 2 FROM tty1 FOR exit, Authentication failure

Example for an URL in Firefox:

May 20 09:51:02 thinkpad login[1947]: pam_tally(login:auth): pam_get_uid; no such user
May 20 09:51:05 thinkpad login[1947]: pam_unix(login:auth): check pass; user unknown
May 20 09:51:05 thinkpad login[1947]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost=
May 20 09:51:07 thinkpad login[1947]: FAILED LOGIN 1 FROM tty1 FOR qen.wikipedia.org, Authentication failure

Here I did log into the ArchLinux BBS:

May 20 09:49:30 thinkpad login[1850]: pam_tally(login:auth): pam_get_uid; no such user
May 20 09:49:51 thinkpad login[1850]: pam_unix(login:auth): check pass; user unknown
May 20 09:49:51 thinkpad login[1850]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost=
May 20 09:49:54 thinkpad login[1850]: FAILED LOGIN 2 FROM tty1 FOR Mr. Shell, Authentication failure

Why does the systemd-login keep track of all my keyboard inputs and tries to use them all for login? How do I fix this?

Thanks in advance! :-)

Mr. Shell

Member

Registered: 2012-03-08

Posts: 4

Re: systemd-login trying to login with all keyboard input

I think this has to do with LightDM, because I've now configured my ~/.xinitrc to start XFCE4 and disabled LightDM. Restarted, logged into the shell and used startx. Everything runs fine and the "keylogger" seems to be gone, at least journalctl doesn't show the input any more. So I guess this is because of some wrong interaction of LightDM and systemd-login? But how to fix it?

Edit: Yes, it seems like a conflict between systemd-login and LightDM. systemd-login is still receiving keyboard input after the login using LightDM. But I have no clue how to fix this...

Last edited by Mr. Shell (2015-05-20 12:10:15)

melanopsis

Member

Registered: 2015-07-02

Posts: 1

Re: systemd-login trying to login with all keyboard input

I'm in the same boat as you. Any chance you found a solution?

killozap

Member

Registered: 2015-07-14

Posts: 16

Re: systemd-login trying to login with all keyboard input

Same here, using up to date Arch, LightDM, XFCE... any news on that matter?

Edit: This only happens when my laptop is booted with the A/C unplugged.  However, if I start the machine with the power line plugged in, everything works fine. Plugging/unplugging after startup does not "fix" or cause problems. I'm on a Thinkpad x230.
Also, with the battery, the laptop shows a blank screen after lock screen (xflock4), but ONLY if at startup the AC plug was not connected.

Last edited by killozap (2015-07-14 21:41:56)

killozap

Member

Registered: 2015-07-14

Posts: 16

Re: systemd-login trying to login with all keyboard input

Hmm... just realized that the problem was caused by enabling overlayfs in /etc/psd.conf for the profile sync daemon (which decreased startup time, on the other hand).

When starting, the lightdm-gtk-greeter flashes up for a second, then the terminal login prompt is shown, then the lightdm greeter for a second time.
With the USE_OVERLAYFS="yes", the greeter shows up just once. In that case the journal for startup WITH AC plug shows that the lightdm-greeter creates a session c1 for user lightdm, which is then closed (->lightdm fails). A new session c2 is created, until I log in. The errors mentioned in #1 don't occur. When overlayfs is disabled, the behavior is the same, with battery or AC plug.
In the case of booting with the battery only and with USE_OVERLAYFS, the first lightdm-greeter session is kept (as it should be!?), but the journal is spammed with above errors...

note: I'm quite new to Arch, switched in order to learn. ;-)

I attach the journals of both cases, plug and battery. Here the overlayfs option was enabled.
w/o AC (-> errors): http://pastebin.com/EyzK1449
AC: http://pastebin.com/fmiWSZ77

Regards,
david

Edit: Got it... simply forgot 'modprobe overlay'... no idea though how this interfered with lightdm.
Edit2: Well, error returned, wasn't that... haha.

Last edited by killozap (2015-07-15 14:03:58)

jackjackk

Member

Registered: 2010-07-21

Posts: 40

Re: systemd-login trying to login with all keyboard input

same problem here.
any new findings?
thanks

killozap

Member

Registered: 2015-07-14

Posts: 16

Re: systemd-login trying to login with all keyboard input

I reinstalled arch from scratch (wanted to do that anyway) and the error did not show up again, with psd and overlay enabled.
However I never figured out where this initially came from.