Bug#433417: openoffice hangs, takes all CPU when port 631 (CUPS) is in use

[Kostas Evangelinos <kos@bastard.net>]

Hi Rene,

| And why is this a OOo bug? Of course OOo should not hang here, but
| IMHO it's a bug in your system. 631 is IPP.

This was actually my first evaluation too. However, OOo makes the big 
assumption that if something is listening on port 631 then you must have
a CUPS enabled system, which is wrong. The correct detection should be 
smarter IMHO: Since CUPS follows an HTTP type protocol, the library doing
this work should look for an actual application response according to the 
CUPS protocol. What if your CUPS daemon is hung? You won't be able to save
your documents.

I looked at the library dependencies in OOo, and it seems like it is using
its own libraries rather than using libcups2. So I filed this bug against OOo 
itself.

In addition, the detection process should be done asynchronously. Assuming 
mountd can be configured/patched to not use this particular port, some other
application may. OOo should not hang completely, only the printing function
should be affected. Hopefully it will simply say 'printing system not working'
or similar.

I think that for the typical user this type of situation is hard to detect
and troubleshoot. It seemed better to take care of it in OOo itself once and 
for all, rather than look for and fix each and every daemon that may 
potentially bind to 631/tcp inadvertedly.

| > "export SAL_DISABLE_CUPS=1" to /etc/openoffice/openoffice.conf makes
| > no difference.
| 
| That would mean I'd break my cups...

The point here is that this config was supposed to disable CUPS altogether
for OOo. It didn't work in my case.

What do you think? I haven't filed a bug against rpc.mountd but can do.

thanks,
Kostas