Bug 621620 - [abrt] crash in openoffice.org-writer-1:3.2.0-12.25.fc13: Dialog::Execute: 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.25.fc13: Dialog::Execute: Pr...
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:466ad104cb10739bfafbd3f93a2...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-05 16:42 UTC by Luis Garza
Modified: 2010-08-08 16:39 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2010-08-08 16:39:02 UTC

Attachments (Terms of Use)
File: backtrace (47.23 KB, text/plain)
2010-08-05 16:42 UTC, Luis Garza
no flags Details

Description Luis Garza 2010-08-05 16:42:24 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer
component: openoffice.org
crash_function: Dialog::Execute
executable: /usr/lib/openoffice.org3/program/swriter.bin
global_uuid: 466ad104cb10739bfafbd3f93a25a91c2fd2a9ac
package: openoffice.org-writer-1:3.2.0-12.25.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. Created new document from a template I've used many times with previous versions

Comment 1 Luis Garza 2010-08-05 16:42:27 UTC
Created attachment 436908 [details]
File: backtrace

Comment 2 David Tardon 2010-08-06 07:11:26 UTC
Is it reproducible? If yes, is it just that one template?

Comment 3 Luis Garza 2010-08-07 00:03:51 UTC
Couldn't reproduce it, happened only that once with that one template...so...unless somebody else shows up, I'd guess you can kill this one as a freak accident.

Comment 4 Caolan McNamara 2010-08-08 16:39:02 UTC
Hmm, I'll close this out then, hopefully we'll get a reproducer for this eventually

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