Bug 649358 - [abrt] openoffice.org-brand-1:3.3.0-9.3.fc14: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-brand-1:3.3.0-9.3.fc14: Process /usr/lib/openoffice.org...
Keywords:
Status: CLOSED DUPLICATE of bug 610103
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:17bfc2748cac01a87b167ea5a23...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-03 15:49 UTC by Jussi Eloranta
Modified: 2010-11-03 16:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-03 16:14:07 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (40.98 KB, text/plain)
2010-11-03 15:49 UTC, Jussi Eloranta 		no flags Details
View All

Description Jussi Eloranta 2010-11-03 15:49:46 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
component: openoffice.org
crash_function: icu_44::RBBIRuleScanner::findSetFor
executable: /usr/lib/openoffice.org3/program/soffice.bin
kernel: 2.6.35.6-48.fc14.i686.PAE
package: openoffice.org-brand-1:3.3.0-9.3.fc14
rating: 3
reason: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1288797878
uid: 500

How to reproduce
-----
1. Tried to start oowriter on a doc file (produced with FC13 version of OO). Note, however, that starting it again right after that worked fine. Timing problem?
2.
3.
Comment 1 Jussi Eloranta 2010-11-03 15:49:48 UTC 
Created attachment 457479 [details]
File: backtrace
Comment 2 David Tardon 2010-11-03 16:14:07 UTC 
the last frame is some brain fart in gdb...

*** This bug has been marked as a duplicate of bug 610103 ***
Note You need to log in before you can comment on or make changes to this bug.