Bug 1114263

Summary: [abrt] lyx: lyx::to_utf8(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&)(): lyx killed by SIGSEGV
Product: [Fedora] Fedora Reporter: meah
Component: lyxAssignee: Rex Dieter <rdieter>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: jamatos, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/21bd1e1d43e2cb4bbec51b837614d7fce3aa10ec
Whiteboard: abrt_hash:525ba0df4d2a2f295509a828d3556cb853705baa
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 01:03:51 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description meah 2014-06-29 10:38:43 UTC
Version-Release number of selected component:
lyx-2.1.0-2.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        lyx
crash_function: lyx::to_utf8(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&)
executable:     /usr/bin/lyx
kernel:         3.14.3-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 lyx::to_utf8(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&)
 #1 lyx::Paragraph::write(std::ostream&, lyx::BufferParams const&, unsigned long&) const
 #2 lyx::Text::write(std::ostream&) const
 #3 lyx::Tabular::write(std::ostream&) const
 #4 lyx::Paragraph::write(std::ostream&, lyx::BufferParams const&, unsigned long&) const
 #5 lyx::Text::write(std::ostream&) const
 #6 lyx::Paragraph::write(std::ostream&, lyx::BufferParams const&, unsigned long&) const
 #7 lyx::Text::write(std::ostream&) const
 #8 lyx::Buffer::write(std::ostream&) const
 #9 lyx::Buffer::writeFile(lyx::support::FileName const&) const

Comment 1 meah 2014-06-29 10:38:48 UTC
Created attachment 913149 [details]
File: backtrace

Comment 2 meah 2014-06-29 10:38:50 UTC
Created attachment 913150 [details]
File: cgroup

Comment 3 meah 2014-06-29 10:38:52 UTC
Created attachment 913151 [details]
File: core_backtrace

Comment 4 meah 2014-06-29 10:38:55 UTC
Created attachment 913152 [details]
File: dso_list

Comment 5 meah 2014-06-29 10:38:57 UTC
Created attachment 913153 [details]
File: environ

Comment 6 meah 2014-06-29 10:38:59 UTC
Created attachment 913154 [details]
File: exploitable

Comment 7 meah 2014-06-29 10:39:01 UTC
Created attachment 913155 [details]
File: limits

Comment 8 meah 2014-06-29 10:39:03 UTC
Created attachment 913156 [details]
File: maps

Comment 9 meah 2014-06-29 10:39:05 UTC
Created attachment 913157 [details]
File: open_fds

Comment 10 meah 2014-06-29 10:39:08 UTC
Created attachment 913158 [details]
File: proc_pid_status

Comment 11 meah 2014-06-29 10:39:09 UTC
Created attachment 913159 [details]
File: var_log_messages

Comment 12 meah 2014-06-29 10:47:49 UTC
- should be the same Lyx-Bugtracker Ticket #9049 (new defect) 
- it happens during the saving of the document
- the saved file is destroyed! -> document loss

Comment 13 José Matos 2014-06-29 10:57:21 UTC
Ouch. :-(

lyx-2.1.1 is in the testing stage to be release soon.

I will report this bug to developers mailing list to see if this helps to shed light on the problem.

Thank you for the report.

Comment 14 José Matos 2014-06-29 14:50:50 UTC
What is the content of the truncated document?
Does it end as reported in the lyx bug you referred above?

Comment 15 meah 2014-06-29 15:37:21 UTC
(In reply to José Matos from comment #14)
> What is the content of the truncated document?
> Does it end as reported in the lyx bug you referred above?

Unfortunately I haven't look in this file, but I expected the same structure.  
  This was not the first time, where it happens. But it was on another machine without the possibility of the automatical bug reports. This was the first time after a long period without this abort. I checked this at begin of the aborts and I noted thas this is same issue.

Comment 16 Fedora End Of Life 2015-05-29 12:15:12 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 17 Fedora End Of Life 2015-06-30 01:03:51 UTC
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.