Bug 666002 - [abrt] openoffice.org-calc-1:3.3.0-17.2.fc14: Process /usr/lib/openoffice.org3/program/scalc.bin was killed by signal 6 (SIGABRT)
Summary: [abrt] openoffice.org-calc-1:3.3.0-17.2.fc14: Process /usr/lib/openoffice.org...
Keywords:
Status: CLOSED DUPLICATE of bug 650170
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:fad16655af190f7ebe34b8a89a6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-28 11:07 UTC by flashl
Modified: 2010-12-29 07:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-29 07:08:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (106.02 KB, text/plain)
2010-12-28 11:08 UTC, flashl
no flags Details

Description flashl 2010-12-28 11:07:48 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/scalc.bin -calc file:///home/flash/.cache/evolution/tmp/evolution-flash-fSwYRy/C&A%20Sites.xls
component: openoffice.org
crash_function: __gnu_cxx::__verbose_terminate_handler()
executable: /usr/lib/openoffice.org3/program/scalc.bin
kernel: 2.6.35.10-72.fc14.i686.PAE
package: openoffice.org-calc-1:3.3.0-17.2.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/scalc.bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1293491961
uid: 500

How to reproduce
-----
1. Message occurred after software installation (new kernel and other products) and reboot
2.
3.

Comment 1 flashl 2010-12-28 11:08:03 UTC
Created attachment 470942 [details]
File: backtrace

Comment 2 David Tardon 2010-12-29 07:00:03 UTC
Can you reproduce the crash? Did it happen during start of openoffice.org, or after some action (like opening a file)? Could you attach a list of extensions you have there (run unopkg list)?

Comment 3 David Tardon 2010-12-29 07:08:00 UTC
Ah, forget it... I see XIOError in threads 12 and 13, which means this is most probably another remainder of bug 650170. The version you have now contains the fix, so there should not be any crash after the next update.

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


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