| Summary: | [abrt] crash in openoffice.org-writer-1:3.2.0-12.35.fc13: Window::~Window: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ivan <Psimer> | ||||
| Component: | openoffice.org | Assignee: | Caolan McNamara <caolanm> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 13 | CC: | caolanm, dtardon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:1a0b30dafe3e6ffaa87d1e1a9ce6452c53e1de4c | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-06-17 15:31:53 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
Ivan
2011-04-18 02:56:58 UTC
Created attachment 492790 [details]
File: backtrace
The stack trace suggests that OO.o showed recovery dialog and crashed after you dismissed it, right? Нет, диалога восстановления отсутствовал Сразу после запуска openoffice writer открывается окно об этой ошибке. Может быть могут проблемы в ext3, вечером run partition hdd fsck. (In reply to comment #3) No, there was no dialogue, reconstruction Immediately after the launch openoffice writer opens the bug. Perhaps the problem may in ext3, evening run partition hdd fsck. We're coming from IntroWindow::IntroWindow which means the main loop hasn't started yet. I'd say that this is a busted configuration or something else horribly wrong detected during configuration loading, which causes it to try and stick up an error dialog, but because the vcl main loop isn't up and running yet this is an epic fail. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 |