Issue 5926 - Open Office writer starts only after a second or third invocation
Summary: Open Office writer starts only after a second or third invocation
Status: CLOSED DUPLICATE of issue 4494
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-17 21:19 UTC by wzab
Modified: 2003-09-08 16:56 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description wzab 2002-06-17 21:19:43 UTC 
When I start Open Office Writer on my home machine (Athlon 850/256 MB RAM) it
starts only after the second trial. After the first press of the appropriate
icon the Writer's window appears and gets closed immediately, before the cursor
starts to blink. On my office machine (Athlon 650/128MB RAM) it works similarly,
but usually it starts after the third trial. Additionally this efect depends on
the amount of time between the consecutive trials (the two trials on my home
machine, or three trials on my office machine must be performed very quickly one
after another, otherwise the Open Office Writer does not start at all).
 It seems that it may be a timeout problem when initializing different threads
of the application?
Comment 1 caolanm 2002-06-18 09:00:07 UTC 
Running gnome on those linux machines ? Try issue 4494. App starts up
too slowly and the gnome session manager thinks its not responding.
Subsequent restarts are faster because of caches and so sneaks past
the magic timeout value. Either make timeout larger, or unsetenv
SESSION_MANAGER to tell session manger to ignore it. Read 4494 for
details.

*** This issue has been marked as a duplicate of 4494 ***
Comment 2 michael.bemmer 2003-03-11 17:21:44 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 3 michael.bemmer 2003-03-11 17:25:49 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 4 michael.bemmer 2003-03-11 17:27:20 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 5 michael.bemmer 2003-03-11 17:37:36 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details.