| 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: | lyx | Assignee: | Rex Dieter <rdieter> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | jamatos, rdieter | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:cfb4771d8ee3e49f1678d059c6194ddccf79866d | ||||||
| Fixed In Version: | 2.0.0 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-08-16 15:12:29 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
Stefan
2011-04-22 08:53:12 UTC
Created attachment 494140 [details]
File: backtrace
Package: lyx-2.0.0-0.21.rc3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Tried deleting a table in a document. Table was inside an activated branch. 2. Received a message that Lyx caught an exception, something about string-s??? (Could not copy the message.) 3. Package: lyx-2.0.0-0.21.rc3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Attempted to copy a table in one part of the document to another. 2. 3. I think that this kind of error was fixed for 2.0.0. (it was one of the last major bugs) Could you try the final lyx-2.0.0 version and see if the problem persist, if it does we will report it upstream. As root it should be enough: # yum update --enablerepo=updates-testing lyx Thank you. Yes, the new version has resolved the issue. Thank you. 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 Just for the record this bug was fixed but I forgot to close it. Doing it now. :-) |