Reliably coredumps when using fingerprint

[Jackaed]

Using latest HEAD gtklock reliably coredumps if I attempt to login by using my fingerprint but using the wrong finger to make it fail the authentication. Possibly related to #40.

[DevDotDev]

Looking through journalctl, I believe this is what is happening to me as well. My entire screen goes red and the only other thing visible is the mouse. I am on arch running Hyprland. Swaylock and hyprland both have similar issues open as well. Unsure of exactly what is to blame.

[Jackaed]

So far, I have had luck with both Swaylock and (what I'm currently using) Hyprlock. The conversation here may be relevant for you.

[tv42]

I trigger this way too often when I have worn/callused/wet fingertips and run out of tries. The screen goes red and gtklock is no more.

For anyone else stumbling on this, to recover from the (very useful!) ext-session-lock-v1 lockout, you can

• switch to a different console: ctrl-alt-f2
• log in there
• run gtklock again: WAYLAND_DISPLAY=wayland-1 exec gtklock (that'll log out of tty2 automatically as soon as you unlock)
• now your wayland session is "normally locked", out of the red screen
• switch to it with alt-f1, and try unlocking again

[mochaaP]

Should be (partially) fixed by #95.
There was still a chance of getting ext_session_lock_surface_v1@xxx: error 2: committed surface dimensions do not match last acked configure

[mochaaP]

the latter one is probably a gtk-session-lock issue (see lock-surface.c:lock_surface_handle_configure), cc'ing @Cu3PO42

[jovanlanik]

Should be fixed by #95 and e0e7f6d.