Bug 144795

Summary:	ooffice wrapper opens writer window by default
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Petr Mladek <pmladek>
Component:	OpenOffice.org	Assignee:	Jan Holesovsky <kendy>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P3 - Medium	CC:	kendy
Version:	Beta 1
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Petr Mladek 2006-01-23 14:48:05 UTC

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

This problem was partly discussed in the bug #144285. Michel Meeks wrote:
--- cut ---
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> ?
--- cut ---

My answer is:
./soffice.bin opens blank window in no special mode when it is started without parameters. So, it still works as expected.

Comment 1 Michael Meeks 2006-01-24 20:54:28 UTC

So - what ./soffice.bin are you using ? I'm using:

OpenOffice_org-2.0.0.99.150-0.1

And my ./soffice throws up writer - as did my 2.0.0.99;
Strange - but so - and we've not changed any code to do with this AFAICS.

Comment 2 Michael Meeks 2006-01-24 20:55:44 UTC

grief - I'm wrong & you're right - I was suckered by a lurking factory process ;-)

Comment 3 Michael Meeks 2006-01-24 20:58:05 UTC

So - I think this should be fixed in the new quickstarter by eliding the "" arguments; at least:

./soffice # gives the right behavior
./soffice "" # starts writer - same as quickstarter bug :-)

Comment 4 Petr Mladek 2006-03-13 13:56:09 UTC

It happens again with the package for SL 10.1-beta8/NLD10-beta8. It might be related to the new ooqstart written in pure X11?

Comment 5 Michael Meeks 2006-03-13 15:08:09 UTC

Seems unlikely. Can you confirm you had no soffice.bin running before you ran 'ooffice' ? ie.

killall -9 soffice.bin
ooffice

as we know - the 2nd time start behavior is different; c'est la vie.

Comment 6 Petr Mladek 2006-03-13 15:24:28 UTC

I have double checked it and there is no soffice.bin running on background:

1. "ps aux | grep soffice"  shows nothing.
2. The application would start faster if there is a running instance on background.

Comment 7 Jan Holesovsky 2006-03-13 16:42:20 UTC

The presence of -splash-pipe=blah seems to change the behavior of ./soffice

./soffice

=> empty window

./soffice -splash-pipe=blah
25%
50%
75%
100%
end

=> writer window.

Comment 8 Michael Meeks 2006-03-13 16:47:07 UTC

Jan - sounds like you're eager to dig this out :-)

If you're there - we should look at getting 'oofromtemplate' to close the splash as it starts too; same ball-game I think.

Comment 9 Jan Holesovsky 2006-03-13 20:14:20 UTC

Fixed both in ooo-build HEAD (speed-ooqstart-open-empty.diff, speed-ooqstart-hide-asap.diff).  Please verify.