On 07/23/2014 12:17 PM, JD wrote: > created the desktop launcher: > The launcher name is > Open Office > The command is: > /usr/bin/ooffice
Mine (from openoffice4.0-debian-menus_4.1-9764_all.deb: <code> #!/usr/bin/env xdg-open [Desktop Entry] Version=1.0 Type=Application Terminal=false Icon[en_US]=/opt/openoffice4/program/logo.png Name[en_US]=OpenOffice Comment[en_US]=ApacheOpenOffice Exec=/opt/openoffice4/program/soffice Name=OpenOffice Comment=ApacheOpenOffice Icon=/opt/openoffice4/program/logo </code> > > 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 What do you have at line 119 in /usr/bin/ooffice? Unless you created ooffice.bin, none will exist. Line 119 in /opt/openoffice4/program/soffice is "$sd_prog/$sd_binary" "$@" & > /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!! > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
