Bug 58165 - : soffice.bin[15283]: segfault at 1 ip 00007f4ccd95f7a6 sp 00007fff67168be0 error 4 in libgcc_s.so.1[7f4ccd958000+d000]
Summary: : soffice.bin[15283]: segfault at 1 ip 00007f4ccd95f7a6 sp 00007fff67168be0 e...
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
4.0.0.0.beta1
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2012-12-11 23:52 UTC by Jose Gómez
Modified: 2013-03-22 15:08 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jose Gómez 2012-12-11 23:52:07 UTC
Problem description: 

swriter crashes on startup with the following error in /var/log/syslog:

Dec 11 23:46:44 adlerG1 kernel: [66735.836508] soffice.bin[15283]: segfault at 1 ip 00007f4ccd95f7a6 sp 00007fff67168be0 error 4 in libgcc_s.so.1[7f4ccd958000+d000]

A file like OSL_PIPE_1000_SingleOfficeIPC_555dbf675fa438399cbfb95623351f1 is created in /var/tmp.

I couldn't locate any core.

Steps to reproduce:
1. Execute swriter

Current behavior:

  Segfault

Expected behavior:

  LibreOffice starts.
Operating System: Ubuntu
Last worked in: 3.6.4.3 release
Comment 1 Michael Stahl (allotropia) 2012-12-12 14:39:53 UTC
did you install the optional libreoffice*-stdlibs package?
(i.e. do you have a libgcc_s.so.1 in the LO installation)

iirc this package should not be installed on modern Linux distros
because it can cause conflicts with system libraries.
Comment 2 Jose Gómez 2012-12-12 19:01:58 UTC
Yes, I had the package lodev4.0-stdlibs_4.0.0.0.beta1-11_amd64.deb installed.

After uninstalling it, now the program starts perfectly.

This deb was installed following the instructions in the README:

  Change directory to the "DEBS" directory.

  sudo dpkg -i *.deb

Maybe this deb should be in a separate folder, in order to avoid confusion?
Comment 3 Michael Stahl (allotropia) 2012-12-12 19:56:22 UTC
is there still a good reason to ship the stdlibs on Linux at all?

didn't we want to drop them at some point, or do i remember that wrong?
Comment 4 Fridrich Strba 2012-12-12 22:24:05 UTC
(In reply to comment #3)
> is there still a good reason to ship the stdlibs on Linux at all?

As soon as you people start to provide the RHEL5 based builds, it is ok to drop them. For the time being, if they are not packaged, the packaging process will fail, since the RHEL4 stdlibs will be called and not the custom compiler ones.

> didn't we want to drop them at some point, or do i remember that wrong?

Yup, you get it right, just that above-mentioned snafus is preventing us from doing so now :(
Comment 5 LeMoyne Castle 2012-12-29 15:07:40 UTC
Confirmed so marked as New though according to discussion this is a known  problem from custom versions of standard C libraries that are required for packaging but do not work out so well after install.
Comment 6 Fridrich Strba 2013-03-22 15:08:29 UTC
This if fixed since the LibreOffice 4.0.1 release. We don't ship the standard libraries anymore starting with that version.