Bug 1082267

Summary: [abrt] libreoffice-core: lock(): soffice.bin killed by SIGABRT
Product: [Fedora] Fedora Reporter: Gus Wirth <gwirth79>
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, gwirth79, ltinkl, mstahl, sbergman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8db34eca7611565ef2a112d49d5f494ef213b8c0
Whiteboard: abrt_hash:d7a7ef5cced274d02e8bc587a067dee3bec0e0ea
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-07 09:01:43 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: 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 Gus Wirth 2014-03-30 01:36:17 UTC 
Description of problem:
Attempted to start Libre Office Base

Application crashed immediately

Version-Release number of selected component:
libreoffice-core-4.2.2.1-7.fc20

Additional info:
reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/lib64/libreoffice/program/soffice.bin --splash-pipe=5
crash_function: lock
executable:     /usr/lib64/libreoffice/program/soffice.bin
kernel:         3.13.7-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #6 lock at /usr/src/debug/libreoffice-4.2.2.1/framework/inc/threadhelp/readguard.hxx:113
 #7 ReadGuard at /usr/src/debug/libreoffice-4.2.2.1/framework/inc/threadhelp/readguard.hxx:79
 #8 framework::LayoutManager::WindowEventListener at /usr/src/debug/libreoffice-4.2.2.1/framework/source/layoutmanager/layoutmanager.cxx:1412
 #9 Call at /usr/src/debug/libreoffice-4.2.2.1/include/tools/link.hxx:123
 #10 VclEventListeners::Call at /usr/src/debug/libreoffice-4.2.2.1/vcl/source/app/vclevent.cxx:67
 #11 Window::CallEventListeners at /usr/src/debug/libreoffice-4.2.2.1/vcl/source/window/window.cxx:5316
 #12 Window::ImplCallEventListeners at /usr/src/debug/libreoffice-4.2.2.1/vcl/source/window/window.cxx:5287
 #13 Window::~Window at /usr/src/debug/libreoffice-4.2.2.1/vcl/source/window/window.cxx:4300
 #14 ToolBox::~ToolBox at /usr/src/debug/libreoffice-4.2.2.1/vcl/source/window/toolbox.cxx:1698
 #15 VCLXDevice::DestroyOutputDevice at /usr/src/debug/libreoffice-4.2.2.1/toolkit/source/awt/vclxdevice.cxx:56
Comment 1 Gus Wirth 2014-03-30 01:36:22 UTC 
Created attachment 880230 [details]
File: backtrace
Comment 2 Gus Wirth 2014-03-30 01:36:23 UTC 
Created attachment 880231 [details]
File: cgroup
Comment 3 Gus Wirth 2014-03-30 01:36:25 UTC 
Created attachment 880232 [details]
File: core_backtrace
Comment 4 Gus Wirth 2014-03-30 01:36:27 UTC 
Created attachment 880233 [details]
File: dso_list
Comment 5 Gus Wirth 2014-03-30 01:36:28 UTC 
Created attachment 880234 [details]
File: environ
Comment 6 Gus Wirth 2014-03-30 01:36:30 UTC 
Created attachment 880235 [details]
File: limits
Comment 7 Gus Wirth 2014-03-30 01:36:34 UTC 
Created attachment 880236 [details]
File: maps
Comment 8 Gus Wirth 2014-03-30 01:36:35 UTC 
Created attachment 880237 [details]
File: open_fds
Comment 9 Gus Wirth 2014-03-30 01:36:36 UTC 
Created attachment 880238 [details]
File: proc_pid_status
Comment 10 Gus Wirth 2014-03-30 01:36:38 UTC 
Created attachment 880239 [details]
File: var_log_messages
Comment 11 Caolan McNamara 2014-04-01 09:03:16 UTC 
Does this happen everytime, or was it a one time thing ?
Comment 12 Gus Wirth 2014-04-01 19:38:39 UTC 
This seems to have been a one-time thing. It was the very first time I ever tried to start it and I recall that there was some message about the wrong Java even though I have a stock Fedora 20 install without any extras.

I just tried starting it up a and shutting down a couple of times and it seems to be behaving itself.

I filed the bug report because it came up on the abrt and thought it should at least be documented in case it became significant later.

If nothing happens in the next month I'd say close it out unless it happens to someone else also.