Proposed patch, please review and apply if it solves the problem (it does on my installation). The problem is that openoffice seems to fork new processes repeatedly on start-up and the parents exit() afterwards (shell script wrappers I suppose). oooqs2 connects the void KProcess::processExited signal to the preloadInstance() slot, which checks if a soffice.bin process is running and starts openoffice if not. Unfortunately openoffice takes a while to start-up completely and soffice.bin seems to be one of the processes which are forked later on during start-up (by the openoffice start-up scripts probably). Therefore preloadInstance() thinks openoffice is not running and executes a new instance. I simply delayed the check for 10sec, on receiving the KProcess::processExited signal. Apply and enjoy.
Proposed patch, please review and apply if it solves the problem (it does on my installation). The problem is that openoffice seems to fork new processes repeatedly on start-up and the parents exit() afterwards (shell script wrappers I suppose). oooqs2 connects the void KProcess: :processExited signal to the preloadInstance() slot, which checks if a soffice.bin process is running and starts openoffice if not. Unfortunately openoffice takes a while to start-up completely and soffice.bin seems to be one of the processes which are forked later on during start-up (by the openoffice start-up scripts probably). Therefore preloadInstance() thinks openoffice is not running and executes a new instance. I simply delayed the check for 10sec, on receiving the KProcess: :processExited signal. Apply and enjoy.