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
Created attachment 880230 [details] File: backtrace
Created attachment 880231 [details] File: cgroup
Created attachment 880232 [details] File: core_backtrace
Created attachment 880233 [details] File: dso_list
Created attachment 880234 [details] File: environ
Created attachment 880235 [details] File: limits
Created attachment 880236 [details] File: maps
Created attachment 880237 [details] File: open_fds
Created attachment 880238 [details] File: proc_pid_status
Created attachment 880239 [details] File: var_log_messages
Does this happen everytime, or was it a one time thing ?
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.