Issue 7534 - OO hangs at startup in psprint module
Summary: OO hangs at startup in psprint module
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: gsl
Classification: Code
Component: www (show other issues)
Version: current
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: philipp.lohmann
QA Contact: Unknown
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-06 00:10 UTC by Unknown
Modified: 2003-03-12 14:33 UTC (History)
1 user (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 Unknown 2002-09-06 00:10:39 UTC
OpenOffice 1.0.1 appears to hang on loading while displaying the 
splash screen. After about 4 minutes of inactivity it continues to load 
normally.
I've filed this as a printing issue because an strace shows that 
'SGENPRT.PS' and 'psprint.conf' are being read, followed by a fork(), 
and then nothing happens for several minutes. (I can mail the strace 
to anyone who's interested).
When 'SGENPRT.PS'  is deleted this behaviour disappears and 
OpenOffice starts correctly.

Here is the top portion of the stacktrace from the thread that I think is 
responsible ( full stack is at 
http://www.pchap.pwp.blueyonder.co.uk/OOo_stack.txt ):

#0  0x40bd0464 in read () from /lib/libc.so.6
#1  0x409aef1c in __DTOR_END__ () from /lib/libpthread.so.0
#2  0x40b6a506 in _IO_file_read () from /lib/libc.so.6
#3  0x40b6968c in _IO_file_underflow () from /lib/libc.so.6
#4  0x40b6bf59 in _IO_default_uflow () from /lib/libc.so.6
#5  0x40b6afc2 in __uflow () from /lib/libc.so.6
#6  0x40b60c2a in _IO_getline_info () from /lib/libc.so.6
#7  0x40b60d0e in _IO_getline () from /lib/libc.so.6
#8  0x40b5fc06 in fgets () from /lib/libc.so.6
#9  0x40c7d55b in 
psp::PrinterInfoManager::getSystemPrintQueues() ()
   from /usr/local/OpenOffice.org1.0/program/libpsp641li.so
#10 0x40c75f43 in psp::PrinterInfoManager::initialize() ()
   from /usr/local/OpenOffice.org1.0/program/libpsp641li.so
#11 0x40c7506c in psp::PrinterInfoManager::PrinterInfoManager() ()
   from /usr/local/OpenOffice.org1.0/program/libpsp641li.so
#12 0x40c74c87 in psp::PrinterInfoManager::get() () from 
/usr/local/OpenOffice.org1.0/program/libpsp641li.so
#13 0x4035ed5f in SalInstance::GetDefaultPrinter() () from 
/usr/local/OpenOffice.org1.0/program/libvcl641li.so
#14 0x4028a638 in Printer::GetDefaultPrinterName() () from 
/usr/local/OpenOffice.org1.0/program/libvcl641li.so
#15 0x4028ae93 in Printer::Printer() () from 
/usr/local/OpenOffice.org1.0/program/libvcl641li.so
#16 0x4293b6ad in SfxPrinter::SfxPrinter(SfxItemSet*) ()
   from /usr/local/OpenOffice.org1.0/program/libsfx641li.so
#17 0x440e2d5f in SwDoc::_GetPrt() const () from 
/usr/local/OpenOffice.org1.0/program/libsw641li.so
#18 0x43ee87e9 in ViewShell::GetPrt(unsigned char) const ()
   from /usr/local/OpenOffice.org1.0/program/libsw641li.so

I'm running Mandrake 8.1, KDE 3.0.3, CUPS 1.1.14 and my kernel is 
2.4.18. A list of my other packages is at 
http://www.pchap.pwp.blueyonder.co.uk/packages.txt.
Comment 1 philipp.lohmann 2002-11-12 14:21:18 UTC
this shows, that either "lpstat -s" or (more probably, since you use
Linux) "lpc status" do not return, which seems to point at an error
with your printing system. Please try those two commands from a
terminal and see if that is really the case.
Comment 2 philipp.lohmann 2003-01-24 14:17:56 UTC
I don't think i can do anything against an external program that
hangs. This is probably something due to a misconfiguration in the
print subsystem used.
Comment 3 michael.bemmer 2003-03-12 14:14:13 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 4 michael.bemmer 2003-03-12 14:14:31 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 5 michael.bemmer 2003-03-12 14:33:15 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.