Red Hat Bugzilla – Bug 1316397
[abrt] gnome-shell: update_clock(): gnome-shell killed by SIGSEGV
Last modified: 2017-08-08 09:06:57 EDT
Description of problem:
gnome-shell took >50% CPU usage and crashed.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 update_clock at gnome-wall-clock.c:345
#1 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1794
#2 _g_closure_invoke_va at gclosure.c:867
#5 g_settings_real_change_event at gsettings.c:386
#6 ffi_call_unix64 at ../src/x86/unix64.S:76
#7 ffi_call at ../src/x86/ffi64.c:525
#8 g_cclosure_marshal_generic_va at gclosure.c:1604
#9 _g_closure_invoke_va at gclosure.c:867
#12 settings_backend_path_changed at gsettings.c:461
#13 g_settings_backend_invoke_closure at gsettingsbackend.c:267
Potential duplicate: bug 1253029
Created attachment 1134719 [details]
Created attachment 1134720 [details]
Created attachment 1134721 [details]
Created attachment 1134722 [details]
Created attachment 1134723 [details]
Created attachment 1134724 [details]
Created attachment 1134725 [details]
Created attachment 1134726 [details]
Created attachment 1134727 [details]
Created attachment 1134728 [details]
Created attachment 1134729 [details]
Created attachment 1134730 [details]
Created attachment 1134731 [details]
Similar problem has been detected:
boot the laptop
after a short amount of time the desktop works as expected
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor: Fedora Project
reason: gnome-shell killed by SIGSEGV
reproducible: Not sure how to reproduce the problem
runlevel: N 5
*** Bug 1361957 has been marked as a duplicate of this bug. ***
I found this bugzilla through ABRT's reporting of the gnome-shell crash. For me, it is triggered almost every time Evolution tries to pop up a calendar appointment alarm. The evolution popup doesn't appear after gnome-shell is auto-restarted, and the meeting/appointment shows up in the list the next time a successful popup appears.
This is with evolution-3.20.5-1.fc24.x86_64.
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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
Thank you for reporting this bug and we are sorry it could not be fixed.