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
Created attachment 913149 [details] File: backtrace
Created attachment 913150 [details] File: cgroup
Created attachment 913151 [details] File: core_backtrace
Created attachment 913152 [details] File: dso_list
Created attachment 913153 [details] File: environ
Created attachment 913154 [details] File: exploitable
Created attachment 913155 [details] File: limits
Created attachment 913156 [details] File: maps
Created attachment 913157 [details] File: open_fds
Created attachment 913158 [details] File: proc_pid_status
Created attachment 913159 [details] File: var_log_messages
- 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
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.
What is the content of the truncated document? Does it end as reported in the lyx bug you referred above?
(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.
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.
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.