Bug 697357 - [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)
Summary: [abrt] crash in openoffice.org-writer-1:3.2.0-12.35.fc13: Window::~Window: Pr...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1a0b30dafe3e6ffaa87d1e1a9ce...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-18 02:56 UTC by Ivan
Modified: 2011-06-17 15:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-17 15:31:53 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (98.07 KB, text/plain)
2011-04-18 02:57 UTC, Ivan
no flags Details

Description Ivan 2011-04-18 02:56:58 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer
component: openoffice.org
crash_function: Window::~Window
executable: /usr/lib/openoffice.org3/program/swriter.bin
global_uuid: 1a0b30dafe3e6ffaa87d1e1a9ce6452c53e1de4c
kernel: 2.6.33.5-112.fc13.i686
package: openoffice.org-writer-1:3.2.0-12.35.fc13
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.Open oowriter
2. crash
3.

Comment 1 Ivan 2011-04-18 02:57:03 UTC
Created attachment 492790 [details]
File: backtrace

Comment 2 David Tardon 2011-04-18 07:06:08 UTC
The stack trace suggests that OO.o showed recovery dialog and crashed after you dismissed it, right?

Comment 3 Ivan 2011-04-18 07:28:51 UTC
Нет, диалога восстановления отсутствовал
Сразу после запуска openoffice writer открывается окно об этой ошибке.
Может быть могут проблемы в ext3, вечером run partition hdd fsck.

Comment 4 Ivan 2011-04-18 07:29:52 UTC
(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.

Comment 5 Caolan McNamara 2011-04-18 08:38:34 UTC
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.

Comment 6 Bug Zapper 2011-05-30 10:40:25 UTC
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


Note You need to log in before you can comment on or make changes to this bug.