huh… so, i made a script, called “ooffice-wrapper,” containing exactly to two lines you gave me, and put it as an executible in /usr/local/bin/. when i type ‘ooffice-wrapper’ from the console, openoffice starts up fine. but, when i type “Exec exec ooffice-wrapper” in the “talk to fvwm” dialog, i get nothing. same goes for “exec ooffice-wrapper.” nothing happens, and i get no message back.
no, i know that. i did make it executible. that’s that part where i said “put it as an executible in /usr/local/bin.” an i can execute the script, but only from the console, and not from Fvwm’s dialogs.
Nor does it make any sense to me. I placed that script into /usr/local/bin, invoked FvwmForm FvwmForm-Talk (which is what you used), typed: “Exec foo” and it loaded open office…
If fvwm logs to ~/.xsession-errors, you might want to see if it put anything there.
Seems like an OO.o issue more so than fvwm. Fvwm does nothing special when it encounters that wrapper script. Indeed, it is the function of the underlying shell at that point.
I suggest you run strace from within that wrapper script to determine where OO is failing, and hence why. It’s no longer an fvwm issue.