Bug 595590 - [abrt] crash in openoffice.org-calc-1:3.1.1-19.28.fc12: Process /usr/lib64/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in openoffice.org-calc-1:3.1.1-19.28.fc12: Process /usr/lib64/op...
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c4dc658a9eb715936860af822af...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-25 06:04 UTC by Lari Tanase
Modified: 2010-05-30 07:48 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-05-30 07:48:32 UTC


Attachments (Terms of Use)
File: backtrace (69.51 KB, text/plain)
2010-05-25 06:04 UTC, Lari Tanase
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 355198 None None None Never

Description Lari Tanase 2010-05-25 06:04:44 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/scalc.bin -calc file:///tmp/Disponibil%20UNIPART%2024.05.2010.xls
component: openoffice.org
crash_function: cppu::OInterfaceIteratorHelper::OInterfaceIteratorHelper
executable: /usr/lib64/openoffice.org3/program/scalc.bin
global_uuid: c4dc658a9eb715936860af822afc2a4df71ad0ee
kernel: 2.6.32.12-115.fc12.x86_64
package: openoffice.org-calc-1:3.1.1-19.28.fc12
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 Lari Tanase 2010-05-25 06:04:52 UTC
Created attachment 416278 [details]
File: backtrace

Comment 2 Caolan McNamara 2010-05-25 07:53:27 UTC
Are you able to reproduce this ? Perhaps it happened with a particular document, if so could you attach that document here.

Comment 3 Caolan McNamara 2010-05-30 07:48:32 UTC
I think we really need the document that triggers this crash to be able to be sure we could fix this. If you can provide that document, feel free to attach it here and reopen this issue


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