Apache OpenOffice (AOO) Bugzilla – Issue 17583
Network printer communication hangs and crashes OOo 1.0.3.1 on Win2KSP4
Last modified: 2004-03-18 15:06:15 UTC
Office LAN with several computers on a router, plus a printer on one of the computers. USB Epson Stylus 900 printer connected by USB to Mac OS X (latest with hotfixes) shared via Samba sharing with Windows 2000 SP4 client (latest with hotfixes, including vendor drivers). The printer is NOT a network-capable printer, i.e. it has no Ethernet port, just USB. However we share it successfully. The issue is that the printer drops in and out of visibility for two reasons: it has a sleep mode, and its host Mac has a sleep mode. When I try to print from OO Writer during such an episode, there is a full application block while the network timeout elapses. Sometimes there is an actual crash, what the OO dialg calls "unrecoverable error," that causes the whole OO application (and quickstarter) to collapse. I think the solution here is to provide more responsive control over printing. After the first two seconds, if OO is not yet talking to the printer, there should be a marquee in the modal print dialog suggesting a printer error, and that the user can click cancel at any time. Normally in these situations I can correct things manually. In any case I do not want to wait 5 whole minutes blocked in a modal dialog waiting for OO to time out. I certainly don't want OO to crash. (After the crash it restarts and asks if I would like to recover my document. I hope that information helps your debugging as to what code is executed.)
Please download and install OpenOffice1.1rc2 from our web site and get the crash to happen, if you can, and then let it send the crash report up (and what the heck, attach the crash details to this issue, too). That will help us track this down. Thanks!
Dan I cannot install a prerelease just to track down this bug. I suggest that you simply try using a network printer from any version and see how the program stalls during network timeouts, which you can create artificially. The problems are common enough that you really don't need my help to track these things down. Once I get 1.1 final and if the crash happens again (which it probably will) I will post the record here. Thanks!
When using a more recent build like a RC2, this problem isn´t reproducible in our network environment. Due to the fact, that some major changes have been made in accessing the network environment (timeouts, file-open dialog,...) it is neccessary, to know, if this problem still occurs in this special environment and to have a stacktrace or crash report for investigating and evaluating this issue. Without any further information, this issue will be closed as "worksforme" but may be reopened if further information are available.
Issue has been closed due to missing further information.
.