Red Hat Bugzilla – Bug 1477709
[abrt] gnome-shell: meta_monitor_manager_kms_read_current(): gnome-shell killed by signal 11
Last modified: 2018-05-03 04:27:07 EDT
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (8 frames)
#0 meta_monitor_manager_kms_read_current at backends/native/meta-monitor-manager-kms.c:1199
#1 meta_monitor_manager_read_current_state at backends/meta-monitor-manager.c:1719
#2 meta_monitor_manager_constructed at backends/meta-monitor-manager.c:433
#3 g_object_new_internal at gobject.c:1823
#6 create_monitor_manager at backends/meta-backend.c:308
#7 meta_backend_real_post_init at backends/meta-backend.c:320
#8 meta_backend_native_post_init at backends/native/meta-backend-native.c:381
#9 meta_init at core/main.c:569
Created attachment 1308366 [details]
Created attachment 1308367 [details]
Created attachment 1308368 [details]
Created attachment 1308369 [details]
Created attachment 1308370 [details]
Created attachment 1308371 [details]
Created attachment 1308372 [details]
Created attachment 1308373 [details]
Created attachment 1308374 [details]
Created attachment 1308375 [details]
Created attachment 1308376 [details]
Created attachment 1308377 [details]
Similar problem has been detected:
Mutter crashes with a segfault 4 error. Not able to reproduce but happend after updating to the new kernel 4.13.5
reason: gnome-shell killed by SIGSEGV
runlevel: N 5
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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'
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 26 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.