Bug 86088 - libreoffice start script fails due to symlink
Summary: libreoffice start script fails due to symlink
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.1.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: needsKDE
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-10 04:09 UTC by Richard Chonak
Modified: 2015-09-04 03:00 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Chonak 2014-11-10 04:09:32 UTC
I'm running openSuSE 13.1 in a recent install.

Invoking libreoffice in a bash window produces this error message:

> libreoffice 
/usr/lib64/qt4/bin/libreoffice: line 49: cd: ../lib64/libreoffice/program: No such file or directory
/usr/lib64/qt4/bin/libreoffice: line 156: /usr/lib64/qt4/bin/oosplash: No such file or directory
> 

Here are the relevant lines of the libreoffice script:

41 # resolve installation directory
42 sd_cwd=`pwd`
43 sd_res=$0
44 while [ -h "$sd_res" ] ; do
45     cd "`dirname "$sd_res"`"
46     sd_basename=`basename "$sd_res"`
47     sd_res=`ls -l "$sd_basename" | sed "s/.*$sd_basename -> //g"`
48 done
49 cd "`dirname "$sd_res"`"


Here's what happening:

I invoke the program as "libreoffice".  
Based on my path, the $0 variable in line 43 is "/usr/lib64/qt4/bin/libreoffice".
At that location is a symlink to "../lib64/libreoffice/program/soffice", 
so $sd_res is set to "../lib64/libreoffice/program".
The cd command in line 49 evaluates this relative to my home directory, so the command fails. 


If I change the symlink to "/usr/lib64/libreoffice/program/soffice", the fail behavior goes away.

Thanks to all.
Comment 1 Richard Chonak 2014-11-10 04:12:50 UTC
Correcting a detail in my problem description:

Here's what happening:

I invoke the program as "libreoffice".  
Based on my path, the $0 variable in line 43 is "/usr/lib64/qt4/bin/libreoffice".
At that location is a symlink to "../lib64/libreoffice/program/soffice", 
so $sd_res is set to "../lib64/libreoffice/program/soffice".
so `dirname "$sd_res"` results in "../lib64/libreoffice/program".
The cd command in line 49 evaluates this relative to my home directory, so the command fails.
Comment 2 Robinson Tryon (qubit) 2015-01-07 02:18:07 UTC
(In reply to Richard Chonak from comment #0)
> > libreoffice 
> /usr/lib64/qt4/bin/libreoffice: line 49: cd: ../lib64/libreoffice/program:
> No such file or directory
> /usr/lib64/qt4/bin/libreoffice: line 156: /usr/lib64/qt4/bin/oosplash: No
> such file or directory

I'm going to guess that this is running under KDE.

Whiteboard -> needsKDE

The 4.1 and 4.2 branches are now EOL. Please grab a 4.3 or 4.4 build from our Download site and see if you can reproduce the problem:
https://www.libreoffice.org/download/

Status -> NEEDINFO

(Change status -> UNCONFIRMED after you've finished testing. Thanks!)
Comment 3 QA Administrators 2015-07-18 17:35:05 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-07-18
Comment 4 QA Administrators 2015-09-04 03:00:25 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-09-03