Bug 703847

Summary: [abrt] lyx-2.0.0-0.21.rc3.fc14: lyx::lyx_exit: Process /usr/bin/lyx was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Stefan <sjansevanrensburg>
Component: lyxAssignee: Rex Dieter <rdieter>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jamatos, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:139dbae53577fb4a8c074a77f0dd01abd8139871
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:12:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Stefan 2011-05-11 12:54:44 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 24253 bytes
cmdline: lyx
component: lyx
Attached file: coredump, 63131648 bytes
crash_function: lyx::lyx_exit
executable: /usr/bin/lyx
kernel: 2.6.35.13-91.fc14.i686
package: lyx-2.0.0-0.21.rc3.fc14
rating: 4
reason: Process /usr/bin/lyx was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1305118163
uid: 500

How to reproduce
-----
1. Was working with branches.
2. Added a table inside an activated branch.
3. Started writing a paragraph outside the table when it suddently crashed.

Comment 1 Stefan 2011-05-11 12:54:48 UTC
Created attachment 498282 [details]
File: backtrace

Comment 2 José Matos 2011-05-26 09:04:47 UTC
There was a bug with tables in rc3 that was fixed in the 2.0.0.

Could you check to see if this bug persists.

LyX 2.0.0 is available through the updates.

Comment 3 Stefan 2011-05-26 11:55:30 UTC
Yes. It is fixed now that I have upgraded to the stable LyX 2.0.0.

Comment 4 Fedora End Of Life 2012-08-16 15:12:42 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 José Matos 2012-09-27 15:24:44 UTC
Just for the record this bug was fixed but I forgot to close it. Doing it now. :-)