Issue 17322 - It takes Openoffice a lot of time to launch (about 90 seconds on a fast computer)
Summary: It takes Openoffice a lot of time to launch (about 90 seconds on a fast compu...
Status: CLOSED DUPLICATE of issue 6431
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: current
Hardware: PC Linux, all
: P4 Trivial (vote)
Target Milestone: ---
Assignee: philipp.lohmann
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-23 20:17 UTC by Unknown
Modified: 2003-07-28 14:28 UTC (History)
2 users (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 Unknown 2003-07-23 20:17:52 UTC 
After searching for a long time, i found something really annoying (a bug?) when
i launched my OO applications : 
It takes Openoffice 1.0.3 (and OO 1.1 beta 2) a lot of time to launch (about 90
seconds on a fast computer on my gnu/linux debian 3.0).

the reason : 
my computer tried to connect to an *unavailable* cupsys server... (i found it by
 sniffing my interfaces)

who did i correct it :
i have modified the /etc/cups/client.conf and updated the ServerName entry

ideas : 
i think i could be fine to reduce the "time out" during which the computer
searches for the cupsys server
or
to test the availability of it during the installation
or
to add an "alert box" after the launch of any of OpenOffice application

i hope i have been helpful :)
Comment 1 diane 2003-07-23 21:00:25 UTC 
reassigned issue to framework component.
Comment 2 diane 2003-07-23 21:03:44 UTC 
changed subcomponent to scripting; reassigned issue to owner of
selected subcomponent.
Comment 3 noel.power 2003-07-28 13:32:29 UTC 
Hi Christof,
I talked to Sander and he reckoned that gsl was the correct component
for this bug .
Noel
Comment 4 christof.pintaske 2003-07-28 14:01:24 UTC 
cp->pl: You've already dislocated the lpstat call into a thread, isn't it
Comment 5 philipp.lohmann 2003-07-28 14:28:35 UTC 
it is

*** This issue has been marked as a duplicate of 6431 ***
Comment 6 philipp.lohmann 2003-07-28 14:28:54 UTC 
closing duplicate