Apache OpenOffice (AOO) Bugzilla – Issue 16931
Startup Crashes on SuSE 8.1
Last modified: 2013-08-07 15:00:19 UTC
soffice segfault soon afters startup. Immediately after clicking on File -> Open soffice segfaults as per the following: Fatal exception: Signal 11 Stack: /opt/OpenOffice.org/program/libsal.so.3[0x40baee2a] /opt/OpenOffice.org/program/libsal.so.3[0x40baefb4] /opt/OpenOffice.org/program/libsal.so.3[0x40baf07a] /lib/libpthread.so.0[0x4114012b] /lib/libc.so.6[0x412c4d68] /opt/OpenOffice.org/program/soffice.bin(_ZN7desktop7Desktop9ExceptionEt+0x7b)[0x8062f55] /opt/OpenOffice.org/program/libvcl645li.so(_ZN23ImplVCLExceptionHandler6signalEP13oslSignalInfo+0xb2)[0x400e712a] /opt/OpenOffice.org/program/libvos3gcc3.so(_ZN3vos28_cpp_OSignalHandler_FunctionEPvP13oslSignalInfo+0x18)[0x40b17a9e] /opt/OpenOffice.org/program/libvos3gcc3.so(_Z24_OSignalHandler_FunctionPvP13oslSignalInfo+0x26)[0x40b17a7e] /opt/OpenOffice.org/program/libsal.so.3[0x40baeed4] /opt/OpenOffice.org/program/libsal.so.3[0x40baf05b] /lib/libpthread.so.0[0x4114012b] /lib/libc.so.6[0x412c4d68] /lib/libpthread.so.0(raise+0x2b)[0x411405eb] /lib/libc.so.6(abort+0x199)[0x412c64d9] /opt/OpenOffice.org/program/libstdc++.so.5[0x4127e424] /opt/OpenOffice.org/program/libstdc++.so.5[0x4127e471] /opt/OpenOffice.org/program/libstdc++.so.5[0x4127e5e5] /opt/OpenOffice.org/program/libi18npool645li.so[0x43be67c9] /opt/OpenOffice.org/program/libi18npool645li.so[0x43be72e9] /opt/OpenOffice.org/program/libi18npool645li.so[0x43be21cd] /opt/OpenOffice.org/program/libvcl645li.so(_ZNK12OutputDevice16ImplGetTextLinesER21ImplMultiTextLineInfolRK6Stringt+0x4fa)[0x401654be] /opt/OpenOffice.org/program/libvcl645li.so(_ZNK12OutputDevice11GetTextRectERK9RectangleRK6StringtP12TextRectInfo+0x103)[0x401690cf] /opt/OpenOffice.org/program/libvcl645li.so(_ZN14HelpTextWindow11SetHelpTextERK6String+0x25e)[0x400d88c2] /opt/OpenOffice.org/program/libvcl645li.so(_ZN14HelpTextWindowC1EP6WindowRK6Stringtt+0x1dd)[0x400d83a7] /opt/OpenOffice.org/program/libvcl645li.so(_Z18ImplShowHelpWindowP6WindowttRK6StringS3_RK5PointPK9Rectangle+0x20e)[0x400d90c4] /opt/OpenOffice.org/program/libvcl645li.so(_ZN4Help11ShowBalloonEP6WindowRK5PointRK6String+0x51)[0x400d7c63] /opt/OpenOffice.org/program/libvcl645li.so[0x401d929a] /opt/OpenOffice.org/program/libvcl645li.so(_ZN13MenuBarWindow11RequestHelpERK9HelpEvent+0x9f)[0x401e4f5f] /opt/OpenOffice.org/program/libvcl645li.so[0x40221bc2] /opt/OpenOffice.org/program/libvcl645li.so(_Z20ImplHandleMouseEventP6Windowthllmtt+0x10e3)[0x40222eb5] /opt/OpenOffice.org/program/libvcl645li.so(_Z19ImplWindowFrameProcPvP8SalFrametPKv+0x16a)[0x402256c0] /opt/OpenOffice.org/program/libvcl645li.so(_ZN12SalFrameData16HandleMouseEventEP7_XEvent+0x445)[0x40283ec5] /opt/OpenOffice.org/program/libvcl645li.so(_ZN12SalFrameData8DispatchEP7_XEvent+0x123)[0x40285ce9] /opt/OpenOffice.org/program/libvcl645li.so(_ZN10SalDisplay8DispatchEP7_XEvent+0x28f)[0x402b1919] /opt/OpenOffice.org/program/libvcl645li.so(_ZN10SalDisplay5YieldEh+0xf1)[0x402b1667] /opt/OpenOffice.org/program/libvcl645li.so[0x402ad647] /opt/OpenOffice.org/program/libvcl645li.so(_ZN7SalXLib5YieldEh+0x426)[0x402ac21a] /opt/OpenOffice.org/program/libvcl645li.so(_ZN11SalInstance5YieldEh+0x34)[0x402b4f70] /opt/OpenOffice.org/program/libvcl645li.so(_ZN11Application5YieldEv+0x61)[0x400e23c9] /opt/OpenOffice.org/program/libvcl645li.so(_ZN11Application7ExecuteEv+0x35)[0x400e22db] /opt/OpenOffice.org/program/soffice.bin(_ZN7desktop7Desktop4MainEv+0x1acc)[0x8064eac] /opt/OpenOffice.org/program/libvcl645li.so(_Z6SVMainv+0x49)[0x400e7197] /opt/OpenOffice.org/program/libvcl645li.so(main+0x1c)[0x402aab7c] /lib/libc.so.6(__libc_start_main+0xa2)[0x412b34a2] /opt/OpenOffice.org/program/soffice.bin(_ZN6Window11RequestHelpERK9HelpEvent+0x3d)[0x805e311] Aborted
Hi Philipp, I can't reproduce on Suse 8.0 or 8.2. Can you find something in the stack?
pl->hdu: seems either OutputDevice::ImplGetTextLines or i18n fails
Yep, looks like the i18n's BreakIterator fails. Cannot reproduce it though. I'd love to have a stack from a debug build for this one. HDU->US: Can you reproduce it.
This looks identical to issue 16872. Shall we declare this one a duplicate?
Yes, it is a dupe. No, we can also not reproduce it. Setting to duplicate to issue 16872. *** This issue has been marked as a duplicate of 16872 ***
Closing Issue.