GNOME Bugzilla – Bug 786574
Crashes after clicking "Deny" on shortcut inhibition for totem
Last modified: 2017-08-21 19:27:17 UTC
mutter-3.25.90-1.fc27.x86_64 gnome-shell-3.25.90-2.fc27.x86_64 1. Launch totem 2. Dismiss error about browsing from tracker, sigh 3. Dialogue pops up saying: "Videos wants to inhibit shortcuts You can restore shortcuts by pressing Shift+Ctrl+Escape" 4. Click "Deny" 5. gnome-shell crashes Stack trace of thread 1666: #0 0x00007f870e29cfa5 g_hash_table_lookup_node (libglib-2.0.so.0) #1 0x00007f870c844f40 meta_wayland_surface_inhibit_shortcuts (libmutter-1.so.0) #2 0x00007f870c84bfdf inhibit_shortcuts_dialog_response_cb (libmutter-1.so.0) #3 0x00007f870e5878cd g_closure_invoke (libgobject-2.0.so.0) #4 0x00007f870e59b19e signal_emit_unlocked_R (libgobject-2.0.so.0) #5 0x00007f870e5a30e3 g_signal_emitv (libgobject-2.0.so.0) #6 0x00007f870d298381 n/a (libgjs.so.0) #7 0x00007f87052e93d8 _ZN2js6InvokeEP9JSContextN2JS8CallArgsENS_14MaybeConstructE (libmozjs-38.so) #8 0x00007f87052df2cd _ZL9InterpretP9JSContextRN2js8RunStateE (libmozjs-38.so) #9 0x00007f87052e9054 _ZN2js9RunScriptEP9JSContextRNS_8RunStateE (libmozjs-38.so) #10 0x00007f87052e9344 _ZN2js6InvokeEP9JSContextN2JS8CallArgsENS_14MaybeConstructE (libmozjs-38.so) #11 0x00007f87055eae43 _Z12js_fun_applyP9JSContextjPN2JS5ValueE (libmozjs-38.so) #12 0x00007f87052e93d8 _ZN2js6InvokeEP9JSContextN2JS8CallArgsENS_14MaybeConstructE (libmozjs-38.so) #13 0x00007f87052e9f73 _ZN2js6InvokeEP9JSContextRKN2JS5ValueES5_jPS4_NS2_13MutableHandleIS3_EE (libmozjs-38.so) #14 0x00007f870543c6a5 _ZN2js3jitL14DoCallFallbackEP9JSContextPNS0_13BaselineFrameEPNS0_15ICCall_FallbackEjPN2JS5ValueENS7_13MutableHandleIS8_EE (libmozjs-38.so) #15 0x00007f870f01e510 n/a (ld-linux-x86-64.so.2) #16 0x0000001c04e94020 n/a (n/a) #17 0x00007f870f018811 n/a (ld-linux-x86-64.so.2) #18 0x00007f87053d4223 _ZL13EnterBaselineP9JSContextRN2js3jit12EnterJitDataE (libmozjs-38.so) #19 0x00007f87053db963 _ZN2js3jit19EnterBaselineMethodEP9JSContextRNS_8RunStateE (libmozjs-38.so) #20 0x00007f87052e8df6 _ZL9InterpretP9JSContextRN2js8RunStateE (libmozjs-38.so) #21 0x00007f87052e9054 _ZN2js9RunScriptEP9JSContextRNS_8RunStateE (libmozjs-38.so) #22 0x00007f87052e9344 _ZN2js6InvokeEP9JSContextN2JS8CallArgsENS_14MaybeConstructE (libmozjs-38.so) #23 0x00007f87052e9f73 _ZN2js6InvokeEP9JSContextRKN2JS5ValueES5_jPS4_NS2_13MutableHandleIS3_EE (libmozjs-38.so) #24 0x00007f87055b3d52 _Z20JS_CallFunctionValueP9JSContextN2JS6HandleIP8JSObjectEENS2_INS1_5ValueEEERKNS1_16HandleValueArrayENS1_13MutableHandleIS6_EE (libmozjs-38.so) #25 0x00007f870d2b2e36 gjs_call_function_value (libgjs.so.0) #26 0x00007f870d28ab65 gjs_closure_invoke (libgjs.so.0) #27 0x00007f870d2a4e7e n/a (libgjs.so.0) #28 0x00007f870e5878cd g_closure_invoke (libgobject-2.0.so.0) #29 0x00007f870e59b19e signal_emit_unlocked_R (libgobject-2.0.so.0) #30 0x00007f870e5a3cc5 g_signal_emit_valist (libgobject-2.0.so.0) #31 0x00007f870e5a462f g_signal_emit (libgobject-2.0.so.0) #32 0x00007f870bd19f24 st_button_button_release (libst-1.0.so) #33 0x00007f870cff35cb _clutter_marshal_BOOLEAN__BOXED (libmutter-clutter-1.so) #34 0x00007f870e5878cd g_closure_invoke (libgobject-2.0.so.0) #35 0x00007f870e59abf0 signal_emit_unlocked_R (libgobject-2.0.so.0) #36 0x00007f870e5a365f g_signal_emit_valist (libgobject-2.0.so.0) #37 0x00007f870e5a462f g_signal_emit (libgobject-2.0.so.0) #38 0x00007f870cf5411c clutter_actor_event (libmutter-clutter-1.so) #39 0x00007f870cf94663 _clutter_process_event (libmutter-clutter-1.so) #40 0x00007f870cfaa948 _clutter_stage_process_queued_events (libmutter-clutter-1.so) #41 0x00007f870cf967c9 clutter_clock_dispatch (libmutter-clutter-1.so) #42 0x00007f870e2aec17 g_main_dispatch (libglib-2.0.so.0) #43 0x00007f870e2aefc0 g_main_context_iterate (libglib-2.0.so.0) #44 0x00007f870e2af2d2 g_main_loop_run (libglib-2.0.so.0) #45 0x00007f870c80024c meta_run (libmutter-1.so.0) #46 0x0000001c0369a227 main (gnome-shell) #47 0x00007f870c17e0fa __libc_start_main (libc.so.6) #48 0x0000001c0369a33a _start (gnome-shell) I have no idea why totem would trigger this dialogue.
Likely a duplicate of bug 786385
How about the reason why the dialogue shows up in the first place? If I'm in doubt and I'm the author and maintainer of the application, you can see why I'd be surprised about it.
You are reporting a crash here. Please let's keep any general discussion about whether and when to show this dialog to bug 786146.
The problem is that totem makes the shell crash. The dialogue showing up is part of the problem. I don't know why it shows up. Do you want me to file a separate bug about it?
Oh, that's likely a GTK+ bug that was fixed. I'll dig out the bug reference when I'm at a real keyboard ...
(In reply to Florian Müllner from comment #5) > Oh, that's likely a GTK+ bug that was fixed. I'll dig out the bug reference > when I'm at a real keyboard ... Looks like: https://bugzilla.gnome.org/show_bug.cgi?id=786480 I'll close it as a dupe of the crasher fix. Would be great to get those 2 fixes in RPMs soon, makes totem (at least) unusable. *** This bug has been marked as a duplicate of bug 786146 ***
(In reply to Bastien Nocera from comment #6) > (In reply to Florian Müllner from comment #5) > > Oh, that's likely a GTK+ bug that was fixed. I'll dig out the bug reference > > when I'm at a real keyboard ... > > Looks like: https://bugzilla.gnome.org/show_bug.cgi?id=786480 Yeah, that's the one. > Would be great to get those 2 fixes in RPMs soon I cannot speak for gtk, but I'll do a .91 mutter tarball/package later today.