GNOME Bugzilla – Bug 772476
[wayland] sometimes all keyboard input is displayed on vt1 when shutting down
Last modified: 2017-09-18 11:58:02 UTC
I cannot duplicate this bug by trying, so I normally wouldn't file the bug, but this seems fairly serious. When logging out on a couple of occasions I've noticed that all of the text I've typed as been present on vt1, including passwords and GPG prompts. I have not found a way to reliably reproduce this, and I have only seen it happen once.
That would be mutter more than gnome-shell here.
Hm, I had this bug occur in the other direction some time ago, don't know if this is related: https://bugzilla.redhat.com/show_bug.cgi?id=1054764
I've seen this too with GNOME Ubuntu 17.04 uisng wayland (mutter/gnome-shell/etc 3.24). I've also seen another issue where Alt+F2 doesn't bring up the Run dialog but takes me to tty2 instead. The most annoying is with a gnome-terminal, occasionally 'ctrl+c' (something that one does remarkably frequently in a terminal) kills gnome-shell. I wonder if both of these are because keyboard input is being sent to the wrong place (especially the ctrl+c going to the shell/mutter)?
"The most annoying is with a gnome-terminal, occasionally 'ctrl+c' (something that one does remarkably frequently in a terminal) kills gnome-shell" I forgot to mention, since this is GNOME/wayland, because restarting the shell is not supported on wayland (https://fedoraproject.org/wiki/Wayland_features#Restarting_gnome-shell), when this happens, the whole session is gone. :\
(In reply to James Strandboge from comment #3) > I've also seen another issue where Alt+F2 doesn't bring up the Run dialog > but takes me to tty2 instead. The most annoying is with a gnome-terminal, > occasionally 'ctrl+c' (something that one does remarkably frequently in a > terminal) kills gnome-shell. I wonder if both of these are because keyboard > input is being sent to the wrong place (especially the ctrl+c going to the > shell/mutter)? This seems unrelated to the bug report here. Can you please report a separate bug and attach a backtrace?
FYI, I could never find a proper reproducer and I hadn't seen this issue after recent 3.24 updates, but curiously, it came up again for another person with recent 3.26: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1710637. I've not seen this yet personally with 3.26.