Bug 1045007

Summary: [abrt] libreoffice-core: Process /usr/lib64/libreoffice/program/soffice.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: lray+redhatbugzilla
Component: libreofficeAssignee: Caolan McNamara <caolanm>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: caolanm, dtardon, erack, lray+redhatbugzilla, ltinkl, mstahl, sbergman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f25861563e6e585ee6cab1c699cad7675b8c6792
Whiteboard: abrt_hash:642f3aeb25d6e23ddac7c1e0975383e9419cd507
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-06 12:26: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:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description lray+redhatbugzilla 2013-12-19 12:44:07 UTC 
Version-Release number of selected component:
libreoffice-core-4.1.3.2-8.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/lib64/libreoffice/program/soffice.bin --writer --splash-pipe=5
executable:     /usr/lib64/libreoffice/program/soffice.bin
kernel:         3.11.10-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ??
 #1 SfxItemSet::~SfxItemSet at /usr/src/debug/libreoffice-4.1.3.2/svl/source/items/itemset.cxx:319
 #2 ~SfxAllItemSet at /usr/src/debug/libreoffice-4.1.3.2/include/svl/itemset.hxx:166
 #3 SfxAllItemSet::~SfxAllItemSet at /usr/src/debug/libreoffice-4.1.3.2/include/svl/itemset.hxx:166
 #4 ~SfxRequest_Impl at /usr/src/debug/libreoffice-4.1.3.2/sfx2/source/control/request.cxx:85
 #5 SfxRequest_Impl::~SfxRequest_Impl at /usr/src/debug/libreoffice-4.1.3.2/sfx2/source/control/request.cxx:85
 #6 SfxRequest::~SfxRequest at /usr/src/debug/libreoffice-4.1.3.2/sfx2/source/control/request.cxx:130
 #7 SfxDispatchController_Impl::dispatch at /usr/src/debug/libreoffice-4.1.3.2/sfx2/source/control/unoctitm.cxx:738
 #8 SfxOfficeDispatch::dispatch at /usr/src/debug/libreoffice-4.1.3.2/sfx2/source/control/unoctitm.cxx:369
 #9 framework::MenuBarManager::Select at /usr/src/debug/libreoffice-4.1.3.2/framework/source/uielement/menubarmanager.cxx:1121
Comment 1 lray+redhatbugzilla 2013-12-19 12:44:12 UTC 
Created attachment 838959 [details]
File: backtrace
Comment 2 lray+redhatbugzilla 2013-12-19 12:44:20 UTC 
Created attachment 838960 [details]
File: cgroup
Comment 3 lray+redhatbugzilla 2013-12-19 12:44:26 UTC 
Created attachment 838961 [details]
File: core_backtrace
Comment 4 lray+redhatbugzilla 2013-12-19 12:44:28 UTC 
Created attachment 838962 [details]
File: dso_list
Comment 5 lray+redhatbugzilla 2013-12-19 12:44:32 UTC 
Created attachment 838963 [details]
File: environ
Comment 6 lray+redhatbugzilla 2013-12-19 12:44:34 UTC 
Created attachment 838964 [details]
File: exploitable
Comment 7 lray+redhatbugzilla 2013-12-19 12:44:36 UTC 
Created attachment 838965 [details]
File: limits
Comment 8 lray+redhatbugzilla 2013-12-19 12:44:39 UTC 
Created attachment 838966 [details]
File: maps
Comment 9 lray+redhatbugzilla 2013-12-19 12:44:46 UTC 
Created attachment 838967 [details]
File: open_fds
Comment 10 lray+redhatbugzilla 2013-12-19 12:44:48 UTC 
Created attachment 838968 [details]
File: proc_pid_status
Comment 11 lray+redhatbugzilla 2013-12-19 12:44:50 UTC 
Created attachment 838969 [details]
File: var_log_messages
Comment 12 David Tardon 2014-01-06 11:40:10 UTC 
This comes from a click in a menu. Can you reproduce the crash?
Comment 13 lray+redhatbugzilla 2014-01-06 12:15:28 UTC 
Hi David,
the bug was automatically reported, and I had several crashes during December. I can not remember when that happened and what user interaction in detail produced this crash.
Regs, Lennart