[SOLVED] Touchpad click doesn't work with autologin, GNOME + GDM

1ptb3b · 2024-05-23 02:01:36

I'm trying to debug why my touchpad click doesn't work.

I tried running

$ sudo libinput debug-events
-event6   POINTER_BUTTON          +0.006s       BTN_LEFT (272) pressed, seat count: 1
 event6   POINTER_BUTTON          +0.129s       BTN_LEFT (272) released, seat count: 0
 event6   POINTER_MOTION          +0.143s         0.00/ -0.32 ( +0.00/ -1.00)
 event6   POINTER_MOTION          +0.150s        -0.79/ -3.16 ( -1.00/ -4.00)
 event6   POINTER_MOTION          +0.157s        -0.88/ -4.39 ( -1.00/ -5.00)
 event6   POINTER_BUTTON          +4.603s       BTN_LEFT (272) pressed, seat count: 1
 event6   POINTER_BUTTON          +4.842s       BTN_LEFT (272) released, seat count: 0

It seems like the click events are being detected. I can also move the mouse cursor—but the clicks don't do anything. I have tap-to-click enabled and taps don't do anything. Actual clicks don't do anything either.

I've noticed in the past that Firefox will change the color of tabs when you hover the mouse over them. Currently with my broken touchpad, I'm noticing that the background color on tabs is not changing. So that tells me that Firefox can't see the cursor hovering over the tab.

Clicks aren't working on any apps, Gnome, Firefox, or otherwise. Again, I can move the cursor, just the clicks don't work.

Here's some version info.

$ gnome-shell --version
GNOME Shell 46.1
$ libinput --version
1.25.0
$ echo $XDG_SESSION_TYPE 
wayland

$ gsettings get org.gnome.desktop.peripherals.touchpad send-events
'enabled'

$ sudo lshw
...
  *-input:2
       product: PIXA3854:00 093A:0274 Touchpad
       physical id: 5
       logical name: input10
       logical name: /dev/input/event6
       logical name: /dev/input/mouse1
       capabilities: i2c
...

I tried restarting my laptop, but that didn't help.

I have a Framework 13 laptop.

I have automatic login enabled for GDM. I edited `/etc/gdm/custom.conf`.

# GDM configuration storage

[daemon]
# Uncomment the line below to force the login screen to use Xorg
#WaylandEnable=false
AutomaticLoginEnable=True
AutomaticLogin=me

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
#Enable=true

Last edited by 1ptb3b (2024-05-28 03:19:22)

1ptb3b · 2024-05-23 04:20:45

OK, I found some workarounds.

Workaround 1: Disable autologin
For some reason, if I disable autologin, my touchpad clicks work once again. I'm still using a Wayland session. Everything just works now.

Workaround 2: Logout, log back in
Let's say I keep autologin enabled. Well, once I'm on my desktop I can use the keyboard to open the terminal and run this command.

gnome-session-quit --logout --no-prompt

This makes my screen flash briefly, but then I'm back on my desktop. NOW the trackpad works like normal.

Interestingly, I noticed that XDG_SESSION_TYPE=x11 after running the command above.

Some more notes:
With autologin enabled, after I enter my LUKS password, GDM puts me on the desktop. Once on the desktop, the entire screen darkens, and I'm presented with a dialog box that says: "Authentication required The login keyring did not get unlocked when you logged into your computer". I can enter my password in this dialog box—and click "Unlock"! However, after the dialog box goes away, my trackpad click stops working.

Is the trackpad click some how related to my login keychain or something?

1ptb3b · 2024-05-23 06:26:26

I tried another experiment. I found this link in the wiki that talks about GDM and LUKS for autologin. So I decided to see if I could get the autologin to unlock my login keyring and maybe that would "fix" the issue?

# I changed my /etc/mkinitcpio.conf to this.
HOOKS=(base systemd autodetect microcode modconf kms keyboard sd-vconsole block sd-encrypt filesystems fsck)
# Regenerated my initramfs

# And I set the appropriate kernel parameters too.
rd.luks.name=device-UUID=dmname

source

I turned on autologin at /etc/gdm/custom.conf and rebooted...

Now I'm not seeing the dialog box that says "Authentication required"! Although... now neither my keyboard nor my trackpad clicks work... this change made things worse.

I also tried making my login keyring password blank, but that had no effect.

Also, I guess since the keyboard stops working I can't switch to another TTY.

Last edited by 1ptb3b (2024-05-23 06:40:19)

seth · 2024-05-23 07:20:49

https://wiki.archlinux.org/title/GDM#Automatic_login - what if you use a timedlogin to give the system a second or two before gnome starts?

1ptb3b · 2024-05-28 03:23:19

Aaaah, of course.

[daemon]
TimedLoginEnable=true
TimedLogin=username
TimedLoginDelay=1

This solves the keyboard and mouse not working issue, which is 99% of the problem. On the other hand, the login is a little less "automatic" now.
After I enter my LUKS password, GDM loads, I have to press Enter to select my user, and then wait and stare at the password prompt for 1 or 2 seconds—then I'm put on the desktop.

Better than losing my keyboard and mouse, but the autologin is less worth it now... ¯\_(ツ)_/¯

Anyway, thanks for pointing this out!

seth · 2024-05-28 05:58:37

Does the input work if you skip GDM and just https://wiki.archlinux.org/title/GNOME#Manually from https://wiki.archlinux.org/title/Getty# … al_console (nb. the screenlocker caveats of that approach) - there's apparently some race condition here, but the question is whether it's the input devices not being available during gnome startup (so it doesn't find them but also misses their addition) or GDM failing to hand over their control (since apparently disabling autologin allows you to use them in GDM)

1ptb3b · 2024-05-29 04:50:05

OK, first I disabled GDM like this.

$ sudo systemctl disable gdm.service

Then I restarted my laptop.

The computer started up again, I unlocked my LUKS partition, then I landed on a
console login screen. No GDM. I logged into my account, then ran this command.

XDG_SESSION_TYPE=wayland dbus-run-session gnome-session

This started GNOME and put me on my desktop... but the mouse and keyboard didn't
work... just like with the autologin...

Next I tried to setup the autologin with a tty... this one I had trouble with.
I created this file.

Next I tried Automatic login to virtual console, but
this one I had trouble with.

I created this file. (Why is the first ExecStart blank?)

[Service]
ExecStart=
ExecStart=-/sbin/agetty -o '-p -f -- \\u' --noclear --autologin me %I $TERM

But after restarting and unlocking LUKS, I got this error.

System is booting up. Unprivileged users are not permitted to log in yet. Please come back later. For technical details, see pam_nologin(8).

Authentication failure

seth · 2024-05-29 08:35:12

The first ExecStart= erases the field.

https://man.archlinux.org/man/core/pam/pam_nologin.8.en
The original problem could be a degraed session, so logind doesn't grant you access to input devices.
You could try to add yourself to the "input" group, but that's workign around the actual problem

=> audit the nologin files to see what creates and removes them and also see your journal for why that maybe takes so long.
https://wiki.archlinux.org/title/Users_ … emd_groups
https://wiki.archlinux.org/title/Audit_ … ies_access

Arch Linux

#1 2024-05-23 02:01:36

[SOLVED] Touchpad click doesn't work with autologin, GNOME + GDM

#2 2024-05-23 04:20:45

Re: [SOLVED] Touchpad click doesn't work with autologin, GNOME + GDM

#3 2024-05-23 06:26:26

Re: [SOLVED] Touchpad click doesn't work with autologin, GNOME + GDM

#4 2024-05-23 07:20:49

Re: [SOLVED] Touchpad click doesn't work with autologin, GNOME + GDM

#5 2024-05-28 03:23:19

Re: [SOLVED] Touchpad click doesn't work with autologin, GNOME + GDM

#6 2024-05-28 05:58:37

Re: [SOLVED] Touchpad click doesn't work with autologin, GNOME + GDM

#7 2024-05-29 04:50:05

Re: [SOLVED] Touchpad click doesn't work with autologin, GNOME + GDM

#8 2024-05-29 08:35:12

Re: [SOLVED] Touchpad click doesn't work with autologin, GNOME + GDM

Board footer