created the desktop launcher: The launcher name is Open Office The command is: /usr/bin/ooffice
in /usr/bin, I have: $ ls -l /usr/bin/*office* lrwxrwxrwx 1 root jd 32 Jul 23 12:18 /usr/bin/ooffice -> /opt/openoffice4/program/soffice $ ls -l /opt/openoffice4/program/soffice -r-xr-xr-x 1 root root 3720 Apr 22 09:40 /opt/openoffice4/program/soffice But the launcher fails to launch open office. I see the following error in /home/jd/.xsession-errors: /usr/bin/ooffice: line 119: /opt/openoffice4/program/ooffice.bin: No such file or directory /usr/bin/ooffice: line 119: /opt/openoffice4/program/ooffice.bin: No such file or directory /usr/bin/ooffice: line 119: /opt/openoffice4/program/ooffice.bin: No such file or directory However, if I execute /opt/openoffice4/program/soffice from the terminal, openoffice runs. So, soffice script takes arg0 and blithely assumes that <arg0>.bin exists, and tries to exec it. Why should a script assume that? It is at least dangerous, especially if executed by a superuser!!
