Issue 127540 - starting AOO with symlink to <$inst_dir>/program/soffice isn't possible
Summary: starting AOO with symlink to <$inst_dir>/program/soffice isn't possible
Status: CONFIRMED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC Linux, all
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-25 13:43 UTC by mroe
Modified: 2017-09-27 06:49 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.1.3
Developer Difficulty: Easy

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

Note You need to log in before you can comment on or make changes to this issue.
Description mroe 2017-09-25 13:43:51 UTC 
At the moment it isn't possible to test different AOO versions under Linux using simply an symlink to 'soffice' of the corresponding installation.

(I don't know when this issue came up, so I selected 3.30 or older.)

In my opinion there is a simple mistake in line 51 of 'soffice':

sd_binary=`basename "$0"`.bin

should be

sd_binary=`basename "$sd_res"`.bin



With this little change it works!
Comment 1 mroe 2017-09-25 13:46:34 UTC 
additional:

The problem occurs if the symlink isn't named 'soffice'!
Comment 2 mroe 2017-09-25 14:02:15 UTC 
(In reply to mroe from comment #0)
> (I don't know when this issue came up, so I selected 3.30 or older.)

Now I can easy start older installations and I found that the start script was changed between OOo 3.3 and AOO 3.4. But it was forgotten to adapt line 51.
Comment 3 mroe 2017-09-25 15:03:37 UTC 
(In reply to mroe from comment #2)
> Now I can easy start older installations and I found that the start script
> was changed between OOo 3.3 and AOO 3.4. But it was forgotten to adapt line
> 51.

Found: Issue 112542