Fedora Account System
Red Hat Associate
Red Hat Customer
Version-Release number of selected component: gnome-shell-3.28.2-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: xkb_keymap_ref executable: /usr/bin/gnome-shell journald_cursor: s=4b1f7cbdccb64d17990dca3397f9396d;i=f3a88;b=eaaeefde6a3a41949b8194aafe39e15a;m=2b34504925;t=56c794d62ce65;x=137b187d36eff8d4 kernel: 4.16.5-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 xkb_keymap_ref at src/keymap.c:59 #1 clutter_evdev_set_keyboard_map at evdev/clutter-device-manager-evdev.c:2399 #2 meta_backend_native_set_keymap at backends/native/meta-backend-native.c:427 #3 ffi_call_unix64 at ../src/x86/unix64.S:76 #4 ffi_call at ../src/x86/ffi64.c:525 #5 gjs_invoke_c_function(JSContext*, Function*, JS::HandleObject, JS::HandleValueArray const&, mozilla::Maybe<JS::MutableHandle<JS::Value> >, GIArgument*) at gi/function.cpp:1088 #6 function_call(JSContext*, unsigned int, JS::Value*) at /usr/include/c++/8/new:169 #7 js::CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), JS::CallArgs const&) at /usr/src/debug/mozjs52-52.7.3-1.fc28.x86_64/jscntxtinlines.h:239 #8 js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) at /usr/src/debug/mozjs52-52.7.3-1.fc28.x86_64/vm/Interpreter.cpp:447 #9 InternalCall(JSContext*, js::AnyInvokeArgs const&) at /usr/src/debug/mozjs52-52.7.3-1.fc28.x86_64/vm/Interpreter.cpp:504 Potential duplicate: bug 1507656
Created attachment 1438491 [details] File: backtrace
Created attachment 1438492 [details] File: cgroup
Created attachment 1438493 [details] File: core_backtrace
Created attachment 1438494 [details] File: cpuinfo
Created attachment 1438495 [details] File: dso_list
Created attachment 1438496 [details] File: environ
Created attachment 1438497 [details] File: exploitable
Created attachment 1438498 [details] File: limits
Created attachment 1438499 [details] File: maps
Created attachment 1438500 [details] File: mountinfo
Created attachment 1438501 [details] File: open_fds
Created attachment 1438502 [details] File: proc_pid_status
Created attachment 1438503 [details] File: var_log_messages
*** Bug 1613980 has been marked as a duplicate of this bug. ***
Similar problem has been detected: The system has been running, logged in, for about a week with gnome-shell on wayland. Each time firefox shows a notification from a website, the system had been locking up for periods of time which were getting longer each time. Eventually, one time when firefox attempted to show a notification, gnome-shell hung for about 10-15 seconds then crashed. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: xkb_keymap_ref executable: /usr/bin/gnome-shell journald_cursor: s=674770e2e7cb49ff814226d3f040e7c5;i=5a1a36;b=ed37dc9206bb4db197ba5c3f5ae950d9;m=8d6158de28;t=5741c1f836497;x=e68776a7fabb131d kernel: 4.17.14-202.fc28.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I found one potential cause. I had the Random Walls gnome shell extension installed. I disabled and removed that shell extension, disabling wasn't enough, but I still had some weird screen tearing. I installed the NVidia proprietary video card drivers and that seemed to resolve the shell crash issues.
After some more time I think I found the pattern behind my crashes: they might be related to notifications displayed when switching WiFi networks failed. The crashes usually occurred when the connection was weak or I was moving. Right after getting back to the login screen when gnome-shell crashed, a "failed to activate network connection" notification was displayed. There might also be some extensions involved, e.g. the "Do Not Disturb Button". Here's my full list of installed and enabled extensions: (K)StatusNotifierItem/AppIndicator Support by 3v1n0 AppKeys by franziskus Background Logo (System extension) Caffeine by eon Clipboard Indicator by Tudmotu Disconnect Wifi by kgshank Do Not Disturb Button by nls1729 No Topleft Hot Corner by azuri Proxy Switcher by flannable Refresh Wifi Connections by kgshank Removable Drive Menu by fmuellner Remove Dropdown Arrows by mpdeimos Sensory Perception by HarlemSquirrel TopIcons Plus by phocean Touchpad Indicator by user501254 User Themes by fmuellner WindowOverlay Icons by sustmi Disabled Extensions: AlternateTab by fmuellner (System extension) Applications Menu by fmuellner (System extension) Launch new instance by fmuellner (System extension) Places Status Indicator by fmuellner (System extension) Window List by fmuellner (System extension)
I'd disable TopIcons, Caffeine, and the WiFi extensions. Then I'd try enabling each extension, starting with TopIcons, and see which extension causes the instability.
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.