Bug 620086 - [abrt] crash in openoffice.org-writer-1:3.1.1-19.34.fc12: SwNumRule::Get: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
[abrt] crash in openoffice.org-writer-1:3.1.1-19.34.fc12: SwNumRule::Get: Pro...
Status: CLOSED DUPLICATE of bug 617615
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Caolan McNamara
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-31 16:15 EDT by Reinhard
Modified: 2010-07-31 18:24 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-31 18:24:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (61.21 KB, text/plain)
2010-07-31 16:15 EDT, Reinhard
no flags Details

  None (edit)
Description Reinhard 2010-07-31 16:15:01 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer file:///home/reinhard/workspace/developers/gandalf/plugins/aggregate/aggregate_manual.odt
component: openoffice.org
crash_function: SwNumRule::Get
executable: /usr/lib64/openoffice.org3/program/swriter.bin
global_uuid: 02156fb42ca82779d951540b99dbd62b0f8720ed
package: openoffice.org-writer-1:3.1.1-19.34.fc12
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1. don't know; fideling around with image files included into writer document
Comment 1 Reinhard 2010-07-31 16:15:04 EDT
Created attachment 435795 [details]
File: backtrace
Comment 2 Caolan McNamara 2010-07-31 18:24:44 EDT
rats, if you can figure out how you got it to happen that would be great

*** This bug has been marked as a duplicate of bug 617615 ***

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