Bug 697288 - [abrt] openoffice.org-brand-1:3.3.0-20.5.fc14: SvxNumPositionTabPage::InitControls killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-brand-1:3.3.0-20.5.fc14: SvxNumPositionTabPage::InitCon...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8b58e72873e8b5cface90462078...
: 672084 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-17 14:08 UTC by BartS
Modified: 2011-05-23 07:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-23 07:58:50 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (81.72 KB, text/plain)
2011-04-17 14:09 UTC, BartS 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description BartS 2011-04-17 14:08:59 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 83677 bytes
cmdline: /usr/lib/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
component: openoffice.org
Attached file: coredump, 117981184 bytes
crash_function: SvxNumPositionTabPage::InitControls
executable: /usr/lib/openoffice.org3/program/soffice.bin
kernel: 2.6.35.12-88.fc14.i686
package: openoffice.org-brand-1:3.3.0-20.5.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1303049189
uid: 500

How to reproduce
-----
1. Tried to bring up numbers and bullets on a paragraph that had "magically lost" it's leading "-"
2.
3.
Comment 1 BartS 2011-04-17 14:09:02 UTC 
Created attachment 492702 [details]
File: backtrace
Comment 2 Caolan McNamara 2011-04-17 20:00:53 UTC 
*** Bug 672084 has been marked as a duplicate of this bug. ***
Comment 3 Caolan McNamara 2011-04-17 20:02:20 UTC 
This has been reported before, but we couldn't reproduce it. Are you able to get it to happen again, e.g. a specific document where it happens ?
Comment 4 David Tardon 2011-05-23 07:58:50 UTC 
Feel free to reopen if you can answer Caolan's question.
Note You need to log in before you can comment on or make changes to this bug.