Issue 25550 - OOo 1.0 hangs at splash screen if CUPS hangs
Summary: OOo 1.0 hangs at splash screen if CUPS hangs
Status: CLOSED DUPLICATE of issue 6431
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 1.0.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: philipp.lohmann
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-16 13:51 UTC by darkdust
Modified: 2004-02-17 12:31 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 darkdust 2004-02-16 13:51:32 UTC 
One of our customers is running OOo 1.0.1 on currently seven application servers, with 
about twenty users per server. Today one of their admins called me because on one of 
these application servers OpenOffice didn't come up correctly, it hung up only showing the 
splash screen. 
 
When run from the command line (via ssh with X forwarding), OOo shows the splash screen 
and the doesn't respond to Ctrl-C or Ctrl-Z anymore. After killing the ssh session and 
reconnecting there were two OOo processes from that user. Killing the first with "kill -9" 
also killed the second. The users start OpenOffice via KDE's start menu and from then on 
had the annoying splash screen that doesn't vanish until they log out and in again. 
 
More or less by luck our customers admin found out that the CUPS printer daemon was 
hanging as well. He then restarted CUPS and from then on OOo started up fine. 
 
System: Dual Pentium III 
OS: SuSE 8.0 with SMP kernel 
CUPS version 1.1.12 from SuSE
Comment 1 thorsten.martens 2004-02-17 11:33:11 UTC 
TM->PL: Please have a look. Maybe a similar problem to the one we´ve had with
the stale mount-points leading the office to hang during startup ?
Comment 2 philipp.lohmann 2004-02-17 12:30:49 UTC 
pl->tm: no, it's not the same, but just as old news :-)

*** This issue has been marked as a duplicate of 6431 ***
Comment 3 philipp.lohmann 2004-02-17 12:31:10 UTC 
closing duplicate