n3rdopolis

There is decent discussion in https://gitlab.gnome.org/GNOME/gdm/-/issues/884 on this matter, A key binding is pressed, logind should emit org.freedesktop.login1.SAK and then the login manager decides what to do I still need...

Changing it to Ctrl+Alt+Esc probably more logical I might need help getting this to be acceptable

> > I am thinking perhaps press and _holding_ Ctrl+Alt+Esc since KDE does start the application killier with a quick Ctrl+Alt+Esc press, perhaps if it is _held down_ since logind...

ctrl+alt+shift+s makes sense to me. A lot of keys, but they are all easy to press with one hand, I don't think there are many conflicts there, and most keyboards...

although, argh that would cause logind to get woken up every time "s" is hit. Ctrl+Alt+_Shift_+Esc doesn't conflict with KDE

> An easy way to pick a SAK that definitely won't conflict with anything is to involve the power button: Ctrl+Alt+Power, or Shift+Power, or similar That's a clever idea, although...

That doesn't factor in multiseat though. You can have a system with two GPUs, and two display servers running separately, so you would need to know what device the SAK...

Although, those are some good points, I am not sure how much of the security is guaranteed to call it SecureAttentionSequence Should I call it LoginAttentionSequence instead?

I still think a manual invocation is still going to be something that is neeed. Display servers are complex, they might be able to respond to the watchdog, but maybe...

I admit that this is my experience with SDDM, although I thought I saw GDM doing this on a test install I had on my VM. Maybe I was wrong...