Bug 144285

Michal, this is related to your recent wrapper-related changes. You kept only the functionality-specific wrappers, such as oowriter, oocalc. Was it intentional to remove the global universal wrappers (ooffice, ooo-wrapper) that started OOo with a blank page?

I would vote to add ooffice back again.

Oh - no, it wasn't intentional - I'll have a poke at that.

So - now we install an ooffice script again - Petr: can you update OOo-wrapper to use that instead of ooo-wrapper ?

Thanks.

OOo-wrapper is upaded, so it should work on beta2 again.

However, there are still some issues with the OOo and ooffice wrappers:

1. The new ooffice wrapper opens blank text file in the writer mode instead of blank window in no special mode.

2. I tested how it works with the KDE quickstarter. The base function is fine. The problem is when the user tries to start ooffice from xterm and there is only the quickstarter instance on backgroung. It should open a window but it does nothing.

Steps to reproduce the 2nd problem:
1. quit all OOo instances
2. start /usr/lib/ooo-2.0/program/soffice -nodefault -nologo
   This command is used by the KDE quickstarter to start the OOo instance on background. However, the result is the same even when you use "ooffice" instead of "/usr/lib/ooo-2.0/program/soffice".
3. start ooffice

Result:
It should open a window but nohing happens. You must start OOo in a special mode (oowriter, oocalc, ...) to get a visible window.

Michael, should I create two extra bug entries fo these two problems?

I think I know what's wrong :-) it'd be great if you could test a patch next week.

------- Comment #4 from pmladek@suse.de  2006-01-20 10:01 MST -------
> OOo-wrapper is upaded, so it should work on beta2 again.
> 1. The new ooffice wrapper opens blank text file in the writer mode
> instead of blank window in no special mode.
> 
	Well - it seems that the old 'ooffice' did this too; at least - perhaps the functionality has changed here: my old 2.0.0.99 build if you run ./soffice.bin starts the shell, but my newer ones all start writer. What do you get if you start: ./soffice.bin <no-args> ?

> 2. I tested how it works with the KDE quickstarter. The base function is fine.
> The problem is when the user tries to start ooffice from xterm and there is
> only the quickstarter instance on backgroung. It should open a window but it
> does nothing.
> 
	Ok - interesting.

> Steps to reproduce the 2nd problem:
> 1. quit all OOo instances
> 2. start /usr/lib/ooo-2.0/program/soffice -nodefault -nologo
>    This command is used by the KDE quickstarter to start the OOo instance on
> background. However, the result is the same even when you use "ooffice"
> instead of "/usr/lib/ooo-2.0/program/soffice".
> 3. start ooffice
> 
	So - taking a lower-level approach :-) if I do:

	/usr/lib/ooo-2.0/program/soffice -nodefault -nologo\
	sleep 20
	/usr/lib/ooo-2.0/program/soffice

	I get no shell window either ;-)

> It should open a window but nohing happens. You must start OOo in a special
> mode (oowriter, oocalc, ...) to get a visible window.
> 
> Michael, should I create two extra bug entries fo these two problems?

I think they're the same bug - but, yes please do create another bug; somehow the 'shell' has got clobbered by someone (up-stream prolly). I'll commit a fix for the other minor problem I was concerned about though.

Thanks.

OOo works now with beta2.

But the following fails:
OOo something.sxw

It opens a window with:
/usr/lib/ooo-2.0/program/something.sxw does not exist.

OOo-writer something.sxw gives the same error.

ooowriter something.sxw fails as well

Michael, could you look at it?

Sure; fixed:

2006-02-01  Michael Meeks  <michael.meeks@novell.com>

	* patches/src680/speed-ooqstart.diff: fix cwd issues
	for files without paths; always send absolute paths;
	Also do system setup bits. n#144285

Thanks for the report.