Bug 687977

Summary: [abrt] lyx-2.0.0-0.11.beta3.fc14: std::_Rb_tree_decrement: Process /usr/bin/lyx was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: marcelo.marucho
Component: lyxAssignee: Rex Dieter <rdieter>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jamatos, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:497462ad6fc04ac89c4dccf7dafe85f24630efc3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-14 17:15:46 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 marcelo.marucho 2011-03-15 21:52:55 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 32255 bytes
cmdline: lyx
component: lyx
Attached file: coredump, 47702016 bytes
crash_function: std::_Rb_tree_decrement
executable: /usr/bin/lyx
kernel: 2.6.35.11-83.fc14.x86_64
package: lyx-2.0.0-0.11.beta3.fc14
rating: 4
reason: Process /usr/bin/lyx was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300224703
uid: 500

How to reproduce
-----
1.
2.
3.
?
Comment 1 marcelo.marucho 2011-03-15 21:52:57 UTC 
Created attachment 485611 [details]
File: backtrace
Comment 2 José Matos 2011-03-16 09:22:33 UTC 
Do you have any recipy to reproduce the bug? What were you doing when lyx crashed?

In any case could you update lyx to the latest version to see if the bug persists?

If you feel comfortable with command line it should be enough to run as root:

#  yum --enablerepo=updates-testing update lyx

If not let us wait a few more days and this version will be available as a normal update.