GNOME Bugzilla – Bug 683537
after updating the shell today I get random stuck grabs or something
Last modified: 2017-01-16 01:17:37 UTC
After updating the shell today I get random stuck grabs or something. I saw one after clicking a search result. And then saw it two or three times again after doing nothing but fast user switching back to the session. I can still use the overview or any item in the top bar. However, I can not use any app or type anything including alt-f2. There are no messages on stderr or stdout. Any idea how to debug this?
It could be a regression from 5a259dd6b0e51c8185f814545bbd9e75432de739, which would link it to notifications (in particular from telepathy chats). Try reverting it, and see if it still happens.
Still locks up after reverting.
i saw a commit go by in clutter that changes input focus behavior: http://git.gnome.org/browse/clutter/commit/?id=3398f3acdfcbb727db12abac30b4f09629edef1d (haven't looked at it closely)
That shouldn't have anything to do with grabs.
I don't know if it has to do with grabs or not.
In case it happens again, here are some commands for lg (assuming the lg is usable) that will help debugging. log(Main.modalActorFocusStack.map(function(e) { return String(e.actor) }).join(',')) log(Main.messageTray._grabHelper._grabStack.map(function(e) { return String(e.actor); }).join(',')) They both log to stderr, so copy-pasting is possible. PS: unrelated to the GrabHelper or the modal stack, ClutterText and ShellEntryMenus seem to have their own set of problems, as even trying to copy-paste these two commands from the lg prompt I got the shell completely stuck twice.
Ok so this is starting to make more sense. I am running a jhbuild shell on F17 GDM. The stuckness only happens after some time. I'm guessing that is the screen lock timeout. What happened before was that a shield would come down and I'd have to restart the shell because it could not talk to GDM. What is happening now is that I can still interact with some stuff. This is pretty bad for me and also a possible security problem. Here is what I saw on stderr: JS ERROR: !!! Failed to open reauthentication channel JS ERROR: !!! message = '"GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.224" (uid=1001 pid=14785 comm="gnome-shell --replace ") interface="org.gnome.DisplayManager.Manager" member="OpenReauthenticationChannel" error name="(unset)" requested_reply="0" destination=":1.12" (uid=0 pid=962 comm="/usr/sbin/gdm-binary -nodaemon ")"' JS ERROR: !!! fileName = '"/opt/gnome/share/gnome-shell/js/gdm/util.js"' JS ERROR: !!! lineNumber = '146' JS ERROR: !!! stack = '"0 anonymous("result" = [object _private_Gio_SimpleAsyncResult], "client" = [object _private_Gdm_Client])@/opt/gnome/share/gnome-shell/js/gdm/util.js:146 1 wrapper([object _private_Gdm_Client], [object _private_Gio_SimpleAsyncResult])@/opt/gnome/share/gjs-1.0/lang.js:204 "' JS LOG: [0x22b61e0 StWidget "screenShieldGroup"] JS LOG: [0x22b61e0 StWidget "screenShieldGroup"]
Ouch! I didn't even think of the screenshield. Try the patch in bug 683060. You should have the shield fall, and a failure notification when you unlock. If it works, then this bug is a duplicate.
Unfortunately even with that patch I still get the hangs. I'll try to get more debug.
Also getting some stuff like: Window manager warning: Log level 8: gtk_im_context_reset: assertion `GTK_IS_IM_CONTEXT (context)' failed Window manager warning: Log level 8: gtk_im_context_set_client_window: assertion `GTK_IS_IM_CONTEXT (context)' failed
Yeah, that's just ShellIMText destroying the GtkIMContext improperly.
I have been noticing this with GNOME Shell 3.6.1. I haven't identified a particular trigger, but it seems to happen when I attempt to use keyboard-accessible things with the keyboard. For example, I used Ctrl+Alt+Tab to open the message tray and I was flipping through notifications (including chat notifications) using the arrow keys. At some point I was still able to do that but input anywhere else was completely ignored and there was no way out. Eventually it developed to the point that I was also unable to open the items in the message tray (I guess because I'd unfocused that part of the message tray and there was no way to get it back with input all stuck), but there was still a prelight if I hovered over them with the mouse. I was able to interact with most of the Shell's chrome exactly as specified in the bug description, with an interesting exception that notifications absolutely would not open. Interestingly, when I switched to a vterm, ran killall gnome-shell and then switched back, Ubuntu's kernel panicked. I assume that's an issue in Ubuntu, but perhaps it's worth mentioning.
Have you been seeing this at all lately, Jon?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
Hello Florian, This bug seems have come back in latest Gnome Shell 3.22.1. Here is some activity around it too https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666 I am lucky because I have a touchscreen, and can move around using it. I have tried to execute those commands up there and they had the following output: > log(Main.modalActorFocusStack.map(function(e) { return String(e.actor) }).join(',')) undefined > log(Main.messageTray._grabHelper._grabStack.map(function(e) { return String(e.actor); }).join(',')) Main.messageTray._grabHelper is undefined The sympthoms are the same: * Only clicks on the topbar/menus work * No clicks nor scrolls work, but the four finger gesture to move desktop works * Going to a getty screen and back solves the problem * killall -HUP gnome-shell also solved the problem In my case, I have no screensaver, and this happens while I am using it, I think is something related to the clicks themselves that trigger this. Finally, I am using wayland here, so I cannot restart with alt+f2 r...
just press control+alt+fn+F1, control+alt+fn+F8: problem solved temporarily! So why cannot normal people change bug status?