Red Hat Bugzilla – Bug 977860
[abrt] grace-5.1.23-1.fc18: bugwarn: Process /usr/bin/xmgrace was killed by signal 6 (SIGABRT)
Last modified: 2014-02-05 16:57:25 EST
Description of problem:
This problem is intermittent. It can usually be reproduced by clicking on any of the GUI menu items or drop boxes.
Version-Release number of selected component:
cmdline: xmgrace Halpha_He_abd_var.agr
runlevel: N 5
var_log_messages: Jun 25 15:19:01 dhcp-17-126 abrt: Saved core dump of pid 2709 (/usr/bin/xmgrace) to /var/tmp/abrt/ccpp-2013-06-25-15:19:01-2709 (25219072 bytes)
Thread no. 1 (10 frames)
#2 bugwarn at utils.c:414
#3 actOnSignal at utils.c:465
#5 _XmInputInGadget at GadgetUtil.c:51
#6 _XmInputForGadget at GadgetUtil.c:93
#7 MenuProcEntry at RowColumn.c:2034
#8 DoSelect at CascadeBG.c:1316
#9 input_dispatch at CascadeBG.c:1765
#10 _XmDispatchGadgetInput at GadgetUtil.c:284
#11 _XmMenuBtnUp at RowColumn.c:3282
#12 HandleActions at TMstate.c:645
Potential duplicate: bug 827738
Created attachment 765081 [details]
Created attachment 765082 [details]
Created attachment 765083 [details]
Created attachment 765084 [details]
Created attachment 765085 [details]
Created attachment 765086 [details]
Created attachment 765087 [details]
Created attachment 765088 [details]
Created attachment 765089 [details]
was working on two sets of data with xmgrace.
evaluate expressions dialog was open and I double clicked
on the graph. then the program crushed
cmdline: xmgrace Pictures/magnetic-field-homogeniety.dat
reason: Process /usr/bin/xmgrace was killed by signal 6 (SIGABRT)
runlevel: N 5
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora
'version' of '18'.
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 prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 to Fedora 18's end of life.
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.
Does this problem still persists?
I have not seen this using Fedora 20.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.