Bug 665546
| Summary: | [abrt] lyx-2.0.0-0.10.beta2.fc14: lyx::lyx_exit: Process /usr/bin/lyx was killed by signal 6 (SIGABRT) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | biswajit ransingh <bransingh> | ||||
| Component: | lyx | Assignee: | Rex Dieter <rdieter> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 14 | CC: | jamatos, rdieter | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:1cac30b9c9560292cb4f5967a7bc80d66dc02260 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-03-20 16:50:27 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
biswajit ransingh
2010-12-24 16:08:00 UTC
Created attachment 470630 [details]
File: backtrace
Package: lyx-2.0.0-0.10.beta2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.while saving -> viewing the pdf in lyx 2. 3. Can you still reproduce this crash with the latest versions of lyx available? rc1 (release candidate 1) is available at updates-testing.Can you still reproduce this crash with the latest versions of lyx available? *** Bug 665551 has been marked as a duplicate of this bug. *** Backtrace analysis found this bug to be similar to bug #680236, closing as duplicate. Bugs which were found to be similar to this bug: bug #574106, bug #589943, bug #596741, bug #602031, bug #649893, bug #664632, bug #680236 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 680236 *** |