Bug 664546 - [abrt] openoffice.org-writer-1:3.3.0-17.2.fc14: rtl_cache_slab_free: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-writer-1:3.3.0-17.2.fc14: rtl_cache_slab_free: Process ...
Keywords:
Status: CLOSED DUPLICATE of bug 655686
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:8468f1f4c8022f9ee36b18cb8db...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-20 18:29 UTC by 03
Modified: 2010-12-21 12:31 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-21 12:31:23 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (42.25 KB, text/plain)
2010-12-20 18:30 UTC, 03 		no flags Details
View All

Description 03 2010-12-20 18:29:59 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer file:///home/sly/Desktop/scoala/CSS150%20-%20Introduction%20to%20Computer%20Security/CSS150%20-%20Introduction%20to%20Computer%20Security%20-%203IP.odt
component: openoffice.org
crash_function: rtl_cache_slab_free
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.35.9-64.fc14.i686
package: openoffice.org-writer-1:3.3.0-17.2.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: I closed a file that I had open, and when I opened OOo again it gave me the crash allert.
time: 1292868644
uid: 500
Comment 1 03 2010-12-20 18:30:01 UTC 
Created attachment 469829 [details]
File: backtrace
Comment 2 David Tardon 2010-12-20 19:26:27 UTC 
Probably a duplicate of bug 655686.
Comment 3 Caolan McNamara 2010-12-21 12:31:23 UTC 

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