Bug 1031332

Summary: [abrt] nedit-5.5-30.fc20: helpCB: Process /usr/bin/nedit was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Mark van Rossum <mvanross>
Component: neditAssignee: Jindrich Novy <novyjindrich>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: novyjindrich, redhat-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/24ad9e7a3e73c753850a64c1e1f96bb30c24c444
Whiteboard: abrt_hash:8ecfae428c9ab68555ace017c8ffc94696a37394
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 03:02:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Mark van Rossum 2013-11-16 22:48:01 UTC
Description of problem:
Open any item in helpmenu

Version-Release number of selected component:
nedit-5.5-30.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        nedit Speeches_that_Shook_the_World.txt
crash_function: helpCB
executable:     /usr/bin/nedit
kernel:         3.11.7-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1005

Truncated backtrace:
Thread no. 1 (10 frames)
 #5 helpCB at menu.c:1260
 #6 XtCallCallbackList at Callback.c:625
 #7 ButtonUp at PushB.c:1331
 #8 HandleActions at TMstate.c:645
 #9 HandleSimpleState at TMstate.c:884
 #10 _XtTranslateEvent at TMstate.c:1101
 #11 XtDispatchEventToWidget at Event.c:906
 #12 _XtDefaultDispatcher at Event.c:1367
 #13 XtDispatchEvent at Event.c:1423
 #14 XtAppProcessEvent at NextEvent.c:1397

Comment 1 Mark van Rossum 2013-11-16 22:48:08 UTC
Created attachment 824987 [details]
File: backtrace

Comment 2 Mark van Rossum 2013-11-16 22:48:11 UTC
Created attachment 824988 [details]
File: cgroup

Comment 3 Mark van Rossum 2013-11-16 22:48:14 UTC
Created attachment 824989 [details]
File: core_backtrace

Comment 4 Mark van Rossum 2013-11-16 22:48:17 UTC
Created attachment 824990 [details]
File: dso_list

Comment 5 Mark van Rossum 2013-11-16 22:48:20 UTC
Created attachment 824991 [details]
File: environ

Comment 6 Mark van Rossum 2013-11-16 22:48:22 UTC
Created attachment 824992 [details]
File: limits

Comment 7 Mark van Rossum 2013-11-16 22:48:25 UTC
Created attachment 824993 [details]
File: maps

Comment 8 Mark van Rossum 2013-11-16 22:48:28 UTC
Created attachment 824994 [details]
File: open_fds

Comment 9 Mark van Rossum 2013-11-16 22:48:32 UTC
Created attachment 824995 [details]
File: proc_pid_status

Comment 10 Mark van Rossum 2013-11-16 22:48:35 UTC
Created attachment 824996 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2015-05-29 09:46:44 UTC
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'
of '20'.

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.

Comment 12 Mark van Rossum 2015-05-29 09:50:45 UTC
STill there in fc22/fc21.

Simply start nedit and go to 'help'-> Getting started

Comment 13 Fedora End Of Life 2015-11-04 11:45:01 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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.

Comment 14 Fedora End Of Life 2015-12-02 03:02:33 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.