Description of problem: I am not sure what happened but I have been experiencing a lot of Gnome shell crashes over the last couple of months or so. Various different Gnome components fail on session login (Gnome settings daemon, Gnome Clocks etc). Sometimes applications fail to start when launched from the quick launch bar (mostly the terminal). In this particular case I was using Virtual Machine Manager to start a Windows 10 VM on a remote KVM host. I had connected to the host and started the VM. The last thing I did was click the VM console window when the Gnome shell crashed and restarted with the session login prompt. Version-Release number of selected component: gnome-shell-3.28.3-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_wayland_surface_ping executable: /usr/bin/gnome-shell journald_cursor: s=57a44481334b421185f31a307705c36e;i=30e5c9;b=ddd3e23a838d403f9e9f71feec57d458;m=597fe41f;t=572ead0b834f9;x=640159f224987363 kernel: 4.17.11-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 meta_wayland_surface_ping at wayland/meta-wayland-surface.c:1389 #1 ffi_call_unix64 at ../src/x86/unix64.S:76 #2 ffi_call at ../src/x86/ffi64.c:525 #3 gjs_invoke_c_function(JSContext*, Function*, JS::HandleObject, JS::HandleValueArray const&, mozilla::Maybe<JS::MutableHandle<JS::Value> >, GIArgument*) at gi/function.cpp:1088 #4 function_call(JSContext*, unsigned int, JS::Value*) at /usr/include/c++/8/new:169 #5 js::CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), JS::CallArgs const&) at /usr/src/debug/mozjs52-52.9.0-1.fc28.x86_64/jscntxtinlines.h:239 #6 js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) at /usr/src/debug/mozjs52-52.9.0-1.fc28.x86_64/vm/Interpreter.cpp:447 #7 js::CallFromStack(JSContext*, JS::CallArgs const&) at /usr/src/debug/mozjs52-52.9.0-1.fc28.x86_64/vm/Interpreter.cpp:2922 #8 Interpret(JSContext*, js::RunState&) at /usr/src/debug/mozjs52-52.9.0-1.fc28.x86_64/vm/Interpreter.cpp:2922 #9 js::RunScript(JSContext*, js::RunState&) at /usr/src/debug/mozjs52-52.9.0-1.fc28.x86_64/vm/Interpreter.cpp:405
Created attachment 1474274 [details] File: backtrace
Created attachment 1474275 [details] File: cgroup
Created attachment 1474276 [details] File: core_backtrace
Created attachment 1474277 [details] File: cpuinfo
Created attachment 1474278 [details] File: dso_list
Created attachment 1474279 [details] File: environ
Created attachment 1474280 [details] File: exploitable
Created attachment 1474281 [details] File: limits
Created attachment 1474282 [details] File: maps
Created attachment 1474283 [details] File: mountinfo
Created attachment 1474284 [details] File: open_fds
Created attachment 1474285 [details] File: proc_pid_status
Created attachment 1474286 [details] File: var_log_messages
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Do you still have a core dump? (check with coredumpctl, it should say 'present' next to gnome-shell) If so, can you run: coredumpctl gdb <pid-of-crashed-gnome-shell> then in gdb, run: frame 1 print *window and post here what it said.
Sorry, was meant to post to https://bugzilla.redhat.com/show_bug.cgi?id=1754148.