Bug 922405

Summary: [abrt] libreoffice-core-3.6.5.2-6.fc18: sdr::overlay::OverlayManager::impApplyRemoveActions: Process /usr/lib64/libreoffice/program/soffice.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: mark_a_rodriguez
Component: libreofficeAssignee: Caolan McNamara <caolanm>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: caolanm, dtardon, erack, ltinkl, mstahl, sbergman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b006f28c105c0a325a3ba557343964cdebebd23d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-12 11:42:08 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
File: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description mark_a_rodriguez 2013-03-16 18:00:22 UTC 
Version-Release number of selected component:
libreoffice-core-3.6.5.2-6.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/lib64/libreoffice/program/soffice.bin --calc --splash-pipe=6
crash_function: sdr::overlay::OverlayManager::impApplyRemoveActions
executable:     /usr/lib64/libreoffice/program/soffice.bin
kernel:         3.8.2-206.fc18.x86_64
uid:            502

Truncated backtrace:
Thread no. 1 (2 frames)
 #0 sdr::overlay::OverlayManager::impApplyRemoveActions at /usr/src/debug/libreoffice-3.6.5.2/svx/source/sdr/overlay/overlaymanager.cxx:227
 #1 sdr::overlay::OverlayManager::remove at /usr/src/debug/libreoffice-3.6.5.2/svx/source/sdr/overlay/overlaymanager.cxx:324
Comment 1 mark_a_rodriguez 2013-03-16 18:00:26 UTC 
Created attachment 711122 [details]
File: backtrace
Comment 2 mark_a_rodriguez 2013-03-16 18:00:28 UTC 
Created attachment 711123 [details]
File: build_ids
Comment 3 mark_a_rodriguez 2013-03-16 18:00:30 UTC 
Created attachment 711124 [details]
File: cgroup
Comment 4 mark_a_rodriguez 2013-03-16 18:00:32 UTC 
Created attachment 711125 [details]
File: core_backtrace
Comment 5 mark_a_rodriguez 2013-03-16 18:00:36 UTC 
Created attachment 711126 [details]
File: dso_list
Comment 6 mark_a_rodriguez 2013-03-16 18:00:38 UTC 
Created attachment 711127 [details]
File: environ
Comment 7 mark_a_rodriguez 2013-03-16 18:00:40 UTC 
Created attachment 711128 [details]
File: limits
Comment 8 mark_a_rodriguez 2013-03-16 18:00:42 UTC 
Created attachment 711129 [details]
File: maps
Comment 9 mark_a_rodriguez 2013-03-16 18:00:45 UTC 
Created attachment 711130 [details]
File: open_fds
Comment 10 mark_a_rodriguez 2013-03-16 18:00:48 UTC 
Created attachment 711131 [details]
File: proc_pid_status
Comment 11 mark_a_rodriguez 2013-03-16 18:00:50 UTC 
Created attachment 711132 [details]
File: var_log_messages
Comment 12 David Tardon 2013-03-25 10:28:15 UTC 
Unfortunately, the stack trace is useless. Unless you can reproduce the crash, there is nothing we can do.