Issue 6431 - Program hangs after splash screen until lpc process killed
Summary: Program hangs after splash screen until lpc process killed
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 1.1
Assignee: ulf.stroehler
QA Contact: issues@sw
URL:
Keywords:
: 14035 17322 25550 26191 (view as issue list)
Depends on:
Blocks:
 
Reported: 2002-07-15 04:45 UTC by lukekendall
Modified: 2004-03-15 14:11 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description lukekendall 2002-07-15 04:45:28 UTC
Running on Linux (Red Hat 7.2), installed OpenOffice and used it successfully.
Had system crashes (was running in 1600x1200 resolution, so probably
crashes in XFree86).  Could run in 1280x1024 mode quite reliably, but the
program wouldn't start up - it would just hang at the splash screen.

Installed some newer drivers for X.  Tried again in 1600x1200 mode.
Noticed a strange thing - an lpc status process that seemed idle.

When that process was killed, the OpenOffice splash screen vanished and 
the program started up.  I see only this occurrence of lpc in the binaries when
I do a "strings" on everything:

/opt/OpenOffice.org1.0/program/libpsp641li.so
/usr/sbin/lpc status
lpc status


$ ps al
  F   UID   PID  PPID PRI  NI   VSZ  RSS WCHAN  STAT TTY        TIME COMMAND
000   126 20421 20409  13   0  2692 1440 wait4  S    pts/4      0:00 -sh
000   126 16893 20421   9   0 82560 32916 pipe_w S   pts/4      0:05
/opt/OpenOffice.org1.0/program/soffice.bin  
040   126 16960 16893   9   0 82560 32916 do_pol S   pts/4      0:00
/opt/OpenOffice.org1.0/program/soffice.bin  
040   126 16961 16960   9   0 82560 32916 nanosl S   pts/4      0:00
/opt/OpenOffice.org1.0/program/soffice.bin  
040   126 16962 16960   9   0 82560 32916 wait_f S   pts/4      0:00
/opt/OpenOffice.org1.0/program/soffice.bin  
040   126 16963 16960   9   0 82560 32916 nanosl S   pts/4      0:00
/opt/OpenOffice.org1.0/program/soffice.bin  
040   126 16965 16960   9   0 82560 32916 do_pol S   pts/4      0:00
/opt/OpenOffice.org1.0/program/soffice.bin  
000   126 16966 16893   9   0  2740 1196 tcp_da S    pts/4      0:00
/usr/sbin/lpc status
000   126 16987 20421  19   0  3284 1356 -      R    pts/4      0:00 ps al

Seems like something is blocked on  I/O.

luke
Comment 1 stefan.baltzer 2002-07-15 19:15:42 UTC
SBA->TM: "Framework"
Comment 2 thorsten.martens 2002-08-01 10:45:29 UTC
TM->HR/CP: Any ideas ?
Comment 3 jens-heiner.rechtien 2002-08-01 14:14:02 UTC
HR->TM: PL might have any idea
Comment 4 philipp.lohmann 2002-08-01 14:32:13 UTC
Ooo tries "lpc status" on startup to discover which print queues are
available. If the lpc command hangs, then Ooo hangs also, because it
waits for lpc's output. The question is why does it hang ? Does this
also happen via the normal command line ? Ooo tries a popen("lpc
status", "r") which essentially starts '/bin/sh -c "lpc status"' and
passes its output to Ooo via pipe.
Comment 5 lukekendall 2002-08-02 00:31:03 UTC
Hmm, our sysadmins aren't in yet, but as far as I know we don't use
that printing environment here.

If I do lpc from the command line, it outputs octal 0377 and exits
with a status of 0.  Are you trying to read more bytes than that, and
blocking on input?  (Sounds unlikely.)

The problem has stopped of its own (after being perfectly repeatable
for a week or so).  So, perhaps something has enabled lpc to return,
where previously it was hanging.

Anyway, assuming that lpc status is going to work even on systems that
use other printing systems, may be assuming too much.

I'll find out more after our Unix sysadmins get in.

luke
Comment 6 thorsten.martens 2002-09-20 11:14:08 UTC
Problem has been reproducible and will be fixed in a staroffice
6.1beta and a corresponding OO version.
Comment 7 thorsten.martens 2003-02-14 10:10:04 UTC
.
Comment 8 michael.bemmer 2003-05-06 15:52:15 UTC
Too late for beta2, re-targeted to 1.1 RC.
Comment 9 thorsten.martens 2003-05-22 09:41:56 UTC
TM->PL: Possible solution might be to build in a timer within office
start. As discussed via phone, please have a look, thanks !
Comment 10 philipp.lohmann 2003-05-22 17:56:56 UTC
Will build in a timeout for the "popen"; this will let OOo continue,
but without automatic  print queues. I guess the next issue in this
regard will then be that startup takes too long :-)
Comment 11 philipp.lohmann 2003-05-26 09:28:33 UTC
*** Issue 14035 has been marked as a duplicate of this issue. ***
Comment 12 philipp.lohmann 2003-05-27 10:49:54 UTC
moved print command evaluation into a separate thread so it does not
slow down office startup; this means that system print queues and
print command (that is the default print command) will potentially
never be available - which is a probably acceptable if the print
system doesn't work anyway.

fixed in CWS vcl11
Comment 13 stephan_schaefer 2003-05-27 11:11:07 UTC
Review done!
Comment 14 philipp.lohmann 2003-06-04 13:00:39 UTC
pl->us: you can test this by delaying lpc/lpstat artifially; e.g.
place this shell script (on Solaris) into the program directory, name
it lpstat and make it executable:
<----- snip
#!/bin/sh

echo delaying $0 1>&2
sleep 30
echo wakeup $0 1>&2
/usr/bin/lpstat $*
<----- snip

This should not delay office startup anymore and after the wakeup
additional printer should be available.
Comment 15 lukekendall 2003-06-05 02:00:33 UTC
Okay, I've added that command early in my PATH, and if the problem
recurs, I'll pass on the results.

luke
Comment 16 ulf.stroehler 2003-06-06 16:07:42 UTC
Verified in cws vcl11.
Setting to fixed.
Comment 17 ulf.stroehler 2003-06-06 16:08:43 UTC
Setting to verified.
Comment 18 ulf.stroehler 2003-07-18 17:35:36 UTC
OK in OOo 1.1 RC2 (srx645_m13s2.8662)
Closing issue.
Comment 19 philipp.lohmann 2003-07-28 14:28:34 UTC
*** Issue 17322 has been marked as a duplicate of this issue. ***
Comment 20 philipp.lohmann 2004-02-17 12:30:48 UTC
*** Issue 25550 has been marked as a duplicate of this issue. ***
Comment 21 thorsten.martens 2004-03-15 14:11:19 UTC
*** Issue 26191 has been marked as a duplicate of this issue. ***