Bug 678629 - [abrt] openoffice.org-calc-1:3.2.0-12.35.fc13: rtl_cache_magazine_clear: Process /usr/lib64/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-calc-1:3.2.0-12.35.fc13: rtl_cache_magazine_clear: Proc...
Keywords:
Status: CLOSED DUPLICATE of bug 655686
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 13
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9acc4c8bc0ddc0d9871928c1022...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-18 16:50 UTC by Max E
Modified: 2011-02-18 19:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-18 19:58:39 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (30.88 KB, text/plain)
2011-02-18 16:50 UTC, Max E 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Max E 2011-02-18 16:50:45 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/scalc.bin -calc
component: openoffice.org
crash_function: rtl_cache_magazine_clear
executable: /usr/lib64/openoffice.org3/program/scalc.bin
kernel: 2.6.34.7-66.fc13.x86_64
package: openoffice.org-calc-1:3.2.0-12.35.fc13
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1298045670
uid: 500

How to reproduce
-----
1.Was working on two spreadsheets
2. Closed one of the spreadsheets
3. OO Calc crashed
Comment 1 Max E 2011-02-18 16:50:48 UTC 
Created attachment 479568 [details]
File: backtrace
Comment 2 Caolan McNamara 2011-02-18 19:58:39 UTC 
Probably something of a generic bug with some singleton getting released at the wrong time. I've high hopes that the LibreOffice work we've done will resolve these, or at least flush them out easier

*** 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.