Bug 36497 - LibO does not start on OpenSuse 11.4 (libpng12.so.0 missing)
Summary: LibO does not start on OpenSuse 11.4 (libpng12.so.0 missing)
Status: CLOSED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Petr Mladek
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-22 09:43 UTC by André Schnabel
Modified: 2011-05-20 03:25 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description André Schnabel 2011-04-22 09:43:43 UTC 
a fresh installation of LibO 3.4 beta 2 fails to start on OpenSuse 11.4 giving the error message:

/opt/libreoffice/program/oosplash.bin: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory


manual installation of libpng12 fixes the problem.

The correct version of libpng should be defined as requirement in the rpms.
Comment 1 Luboš Luňák 2011-04-28 06:07:32 UTC 
The openSUSE-provided packaged from the LibreOffice: repositories do not install under /opt.
Comment 2 Petr Mladek 2011-05-11 03:41:15 UTC 
Hmm, the packages are supposed to work on every distro. I am not sure if the provides and requires are standardized on all distributions.

One solution would be to bundle libpng with LO. I am not sure if it is a good idea. There were often security updates for this library :-(

Anyone has a better idea, opinion?
Comment 3 Michael Meeks 2011-05-17 04:33:15 UTC 
Urk - it looks like I broke this with:

PKG_CHECK_MODULES( LIBPNG, libpng, ENABLE_QUICKSTART_LIBPNG="TRUE", ENABLE_QUICKSTART_LIBPNG="" )

We need to be able to disable using libpng for the quickstarter; I should add back a --disable-quickstart-libpng thing - and we should use that for our release distro-config I guess.


Hmm.
Comment 4 Michael Meeks 2011-05-17 07:25:15 UTC 
Andre - the work around is to just run 'soffice.bin' manually incidentally.

I've committed the fix to master - it missed review for RC1 I think - should be in RC2.

Thanks !