oooqs does not launch ooo in the background when it starts, neither does it start one of the ooo applications if one is right-clicked through the oooqs menu. I'm using following packages (equery list output): [I--] [ ] app-office/openoffice-1.1.2 (0) [I--] [ ] app-office/oooqs-2.0.2 (0) In fact I first filed this bug as comment to bug #54403 (related to oooqs and ximian ooo) but one of the people following up that bug recommended me to create a new bug. If I strace oooqs I see: 1. execve("/usr/bin/oooqs", ["oooqs", "2"], [/* 5... The argument '2' is a wrong argument. 2. open("/home/kda/.kde3.2/share/config/oooqsrc", O_RD... If look into the file, I found "Exec=/soffice". 3. stat64("/usr/kde/3.2/share/config/oooqsrc", 0xbfff... I don't have that file. I changed (see 2) Exec=/soffice to Exec=soffice and now oooqs starts up, launches soffice in quickstart mode and a ooo application is launched if I choose one through oooqs. Reproducible: Always Steps to Reproduce: 1. login to kde or gnome 2. start oooqs Actual Results: oooqs does not launch ooo in the background when it starts, neither does it start one of the ooo applications if one is right-clicked through the oooqs menu. Expected Results: oooqs starts up, launches soffice in quickstart mode and a ooo application is launched if I choose one through oooqs.
Just tested this, and it works for me, my oooqsrc contains EXEC=/home/xxx/.openoffice/soffice which is correct, so this seems only to be an issue with an old bogus config file on your local setup or something like that, not a lot we could do about that. If unsure just delete /home/kda/.kde3.2/share/config/oooqsrc, it should be regenerated the next time you use oooqs. Tested this with both 2.0.2 and 2.0.3. Anyway closing this
