Bug 542514

Summary: [abrt] crash detected in openoffice.org-writer-1:3.1.1-19.14.fc12
Product: [Fedora] Fedora Reporter: Marcelo Torres <lu9fcx>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: caolanm, dtardon
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:a7144d9ae7641f871f1015247f33d52b90aa5dd3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-01 08:14:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Marcelo Torres 2009-11-30 01:25:29 UTC
abrt detected a crash.

Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer file:///mnt/xp4/programabertone/documentos/precios.odt
component: openoffice.org
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.31.5-127.fc12.x86_64
package: openoffice.org-writer-1:3.1.1-19.14.fc12
rating: 3
reason: Process was terminated by signal 11

Comment 1 Marcelo Torres 2009-11-30 01:25:34 UTC
Created attachment 374655 [details]
File: backtrace

Comment 2 Caolan McNamara 2009-11-30 09:49:21 UTC
That's a rather interesting crash, what were you doing at the time ?, just loading a particular document ?

Comment 3 Marcelo Torres 2009-11-30 14:36:12 UTC
I notice that mistake the tool for automatic notification of errors in fedora 12.
There was only open for a new openoffice document.
He had not noticed that there was a crash.
Sorry about my English. Use the google translator.
(In reply to comment #2)
> That's a rather interesting crash, what were you doing at the time ?, just
> loading a particular document ?

Comment 4 Caolan McNamara 2009-12-01 08:14:25 UTC
Slightly different from bug 541876, but I believe its the same thing. Some thread still going after exit and accessing what it shouldn't.

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