Bug 587896 - [abrt] crash in openoffice.org-impress-1:3.1.1-19.28.fc12: Process /usr/lib64/openoffice.org3/program/simpress.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in openoffice.org-impress-1:3.1.1-19.28.fc12: Process /usr/lib64...
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org   
(Show other bugs)
Version: 12
Hardware: x86_64 Linux
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5f6e877f2d8b55121f5d533b413...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-01 13:36 UTC by Misha Shnurapet
Modified: 2010-05-02 12:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-02 12:23:37 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Misha Shnurapet 2010-05-01 13:36:05 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
cmdline: /usr/lib64/openoffice.org3/program/simpress.bin -impress file:///home/jayrome/%D0%A0%D0%B0%D0%B1%D0%BE%D1%87%D0%B8%D0%B9%20%D1%81%D1%82%D0%BE%D0%BB/%D0%AD%D1%82%D0%BE%D1%82%20%D0%B4%D0%B5%D0%BD%D1%8C%20%D0%BC%D1%8B%20%D0%BF%D1%80%D0%B8%D0%B1%D0%BB%D0%B8%D0%B6%D0%B0%D0%BB%D0%B8%20%D0%BA%D0%B0%D0%BA%20%D0%BC%D0%BE%D0%B3%D0%BB%D0%B8!.pptx
component: openoffice.org
executable: /usr/lib64/openoffice.org3/program/simpress.bin
kernel: 2.6.32.11-99.fc12.x86_64
package: openoffice.org-impress-1:3.1.1-19.28.fc12
reason: Process /usr/lib64/openoffice.org3/program/simpress.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Comment 1 David Tardon 2010-05-02 12:12:50 UTC
In normal situation abrt creates a stack trace and attaches it to the bug report; it seems something went wrong this time and none was created. Do you remember what did you do at the time of the crash?

Comment 2 Misha Shnurapet 2010-05-02 12:23:37 UTC
I didn't have enough space in / so it failed to create the report.


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