Red Hat Bugzilla – Bug 1031246
[abrt] gnome-shell-3.10.2-1.fc20: _g_log_abort: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT)
Last modified: 2015-06-29 08:56:40 EDT
Description of problem:
Using Fedora 20 GNOME 3.10.1 after I restored from a backup evolution reminders displays to me my missed items. After I dismiss them from the pop up menu that I get I go to notifications because the reminders I dismissed earlier are still being displayed in notifications bar. I bring up the list of events and the second I do this this error message showed up.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#2 _g_log_abort at gmessages.c:255
#5 window_backed_app_get_window at shell-app.c:149
#6 shell_app_launch at shell-app.c:1203
#7 shell_app_activate_full at shell-app.c:636
#8 ffi_call_unix64 at ../src/x86/unix64.S:76
#9 ffi_call at ../src/x86/ffi64.c:522
#10 gjs_invoke_c_function at gi/function.c:894
#11 function_call at gi/function.c:1203
#12 CallJSNative at /usr/src/debug/mozjs17.0.0/js/src/jscntxtinlines.h:372
#13 js::InvokeKernel at /usr/src/debug/mozjs17.0.0/js/src/jsinterp.cpp:345
Created attachment 824792 [details]
Created attachment 824793 [details]
Created attachment 824794 [details]
Created attachment 824795 [details]
Created attachment 824796 [details]
Created attachment 824797 [details]
Created attachment 824798 [details]
Created attachment 824799 [details]
Created attachment 824800 [details]
Created attachment 824801 [details]
This is a repeat one. Using GNOME shell 3.10.1 in the notifications bar in the bottom there may be evolution reminders. Attempting to click on one to dismiss it crashes gnome-shell.
reason: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT)
runlevel: N 5
Another user experienced a similar problem:
RIght-clicked on an icon in the notification area.
reason: gnome-shell killed by SIGABRT
runlevel: N 5
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.