Bug 702004

Summary: [abrt] [fix available] openoffice.org-brand-3.2.1-19.6.el6_0.5: const: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
Product: Red Hat Enterprise Linux 6 Reporter: Siddharth <swaikar>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: desktop-bugs <desktop-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 6.2CC: dtardon, vgaikwad
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-12 10:38:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Backtrace, Dissassembly none

Description Siddharth 2011-05-04 14:20:42 UTC 
Description of problem:
abrt version: 1.1.13
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
component: openoffice.org
crash_function: const
executable: /usr/lib64/openoffice.org3/program/soffice.bin
kernel: 2.6.32-71.24.1.el6.x86_64
rating: 0
reason: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
time: 1303992286
uid: 500 


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 6.0 (Santiago)
openoffice.org-brand-3.2.1-19.6.el6_0.5
architecture: x86_64


How reproducible:
random crash

Steps to Reproduce:
1.
2.
3.
  
Actual results:
openoffice crashed

Expected results:
openoffice should not crashed

Additional info:
Comment 1 Siddharth 2011-05-04 14:22:47 UTC 
Created attachment 496803 [details]
Backtrace, Dissassembly
Comment 3 David Tardon 2011-05-04 15:27:13 UTC 
This happens if you update oo.o while quickstarter is running and then try to use it. We are able to fix it, but it's not easy to get it right and I'm not convinced it's necessary, given the frequency of oo.o updates in RHEL.
Comment 4 RHEL Program Management 2011-05-05 06:01:36 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 5 David Tardon 2011-05-12 10:38:06 UTC 

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