Bug 53830 - : libpng12 missing on Suse 12.1 x64
Summary: : libpng12 missing on Suse 12.1 x64
Status: RESOLVED DUPLICATE of bug 44203
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
3.6.1.1 rc
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-20 09:22 UTC by Laurent Balland
Modified: 2012-10-11 06:22 UTC (History)
0 users

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 Laurent Balland 2012-08-20 09:22:53 UTC
Problem description: Installation failed

Steps to reproduce:
1. Download Linux RPM x64 file LibO 3.6.1 RC1
2. unzip
3. install with YaST2
4. launch LibO 3.6

Current behavior: nothing happen. From terminal, you get a message of missing libpng12

Expected behavior: LibO should start

Workaround: install libpng12. libpng14 is already there

Platform (if different from the browser): Suse 12.1 x64. LibO 3.5.4 from Suse was NOT removed before installation. No other installation of LibO was done before.
              
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Comment 1 bougler 2012-10-10 18:20:09 UTC
I confirm under fedora 17 libreoffice 3.6.2.2
/ opt/libreoffice3.6/program/swriter
/ opt/libreoffice3.6/program/soffice.bin: error while loading shared libraries: libpng12.so.0: can not open shared object file: No such file or directory

yum search libpng12
No available package libpng12
Comment 2 bougler 2012-10-10 18:21:57 UTC
I confirm under fedora 17 libreoffice 3.6.2.2
no error in the installation but with yum

/ opt/libreoffice3.6/program/swriter
/ opt/libreoffice3.6/program/soffice.bin: error while loading shared libraries: libpng12.so.0: can not open shared object file: No such file or directory

yum search libpng12
No available package libpng12

Gérard
Comment 3 Laurent Balland 2012-10-11 06:22:38 UTC
*** This bug has been marked as a duplicate of bug 44203 ***