Bug 147893 - openoffice doesnt create a new document on startup
Summary: openoffice doesnt create a new document on startup
Status: CLOSED DUPLICATE of bug 147889
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-02-12 04:04 UTC by Phil Anderson
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-02-13 00:03:44 UTC

Attachments (Terms of Use)
Empty window when launching Openoffice (17.15 KB, image/png)
2005-02-12 04:04 UTC, Phil Anderson
no flags Details

Description Phil Anderson 2005-02-12 04:04:28 UTC
Description of problem:
Since updating to the latest openoffice package for FC3, openoffice fails to
start with a 'new document' on startup.  No matter which openoffice.org menu
item I launch with, I'm greeted with an empty window!  I can then do
file->new->??? and everything is fine.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Update to the above version
2. Launch oowriter, or one of the other links

Actual results:
Empty window (see attachment)

Expected results:
A blank writer document

Comment 1 Phil Anderson 2005-02-12 04:04:28 UTC
Created attachment 111021 [details]
Empty window when launching Openoffice

Comment 2 Gerry Tool 2005-02-12 04:34:00 UTC
Same here.  I'm glad to have the printers back, however.

Comment 3 Jim 2005-02-12 15:12:29 UTC

Include the component you wish to use in the command line. For example:

ooffice -writer

That seems to work for me. This is the way the official OpenOffice.org builds
work - if you just launch "soffice" it appears blank.

Comment 4 Phil Anderson 2005-02-12 22:55:13 UTC
To fix this edit /usr/bin/ooffice changing line 39 to read:
my $BinSuffix = '';

Comment 5 Dan Williams 2005-02-13 00:03:44 UTC

*** This bug has been marked as a duplicate of 147889 ***

Note You need to log in before you can comment on or make changes to this bug.