Re: [Gnumed-devel] bug? Menu Correspondence > Write letter

[Karsten Hilbert]

On Tue, Jul 07, 2009 at 10:47:34PM -0700, Jim Busser wrote:

> In my debian lenny vm, under the default Gnome desktop, I had been
> unable to originally launch OpenOffice although I am not sure
> whether that was before or after I had attempted (from within the
> GNUmed client)
> 
>       Correspondence > Write letter
> 
> however that have a complaint and suggested I retry setting longer
> my Oo startup time, however that made no difference.

The log should have a bit more information.

> I did then install KDE (4.2) and perhaps that reinstalled or fixed
> something from openoffice.org because after I logged back in with
> kdm as my display manager, I was able to launch OpenOffice writer
> from the KDE "Office" menu. The version is
> 
>       openoffice.org 1.2.4.1

1.2.4.1 or 2.4.1 ?  The former is not compatible with GNUmed
(and so unbelievably old that I doubt you meant that).

> But when I switch into GNUmed, and select
> 
>       Correspondence > Write letter
> 
> I got the same complaint from GNUmed even after I changed the Oo
> setting to 45 seconds. So I tried pre-loading Oo so that it was
> already running when I would select "Correspondence > Write letter",
> but that made no difference.

It would have to be running in server mode.

> I re-logged back into Gnome, which now runs Oo without complaint.
> But still the same problem when I would try within GNUmed to write a
> letter. The within-GNUmed template (physiotherapie?) would not be
> any  part of the problem, would it?

Probably not as it seems to retrieve it ...

> 2009-07-07 10:18:59  DEBUG     gm.db 
> (/home/jbusser/gnucvs/gnumed/gnumed/Gnumed/pycommon/gmPG2.py::bytea2file_object()
>  #832): expecting bytea data of size: [289] bytes
> 2009-07-07 10:18:59  DEBUG     gm.db 
> (/home/jbusser/gnucvs/gnumed/gnumed/Gnumed/pycommon/gmPG2.py::bytea2file_object()
>  #833): using chunk size of: [0] bytes
> 2009-07-07 10:18:59  DEBUG     gm.db 
> (/home/jbusser/gnucvs/gnumed/gnumed/Gnumed/pycommon/gmPG2.py::bytea2file_object()
>  #838): chunk size [0] bytes: retrieving all data at once
> 2009-07-07 10:18:59  DEBUG     gm.db 
> (/home/jbusser/gnucvs/gnumed/gnumed/Gnumed/pycommon/gmPG2.py::bytea2file_object()
>  #844): chunks to retrieve: [1]
> 2009-07-07 10:18:59  DEBUG     gm.db 
> (/home/jbusser/gnucvs/gnumed/gnumed/Gnumed/pycommon/gmPG2.py::bytea2file_object()
>  #845): remainder to retrieve: [0] bytes

... just fine.

> 2009-07-07 10:19:00  DEBUG     gm.forms 
> (/home/jbusser/gnucvs/gnumed/gnumed/Gnumed/business/gmForms.py::init_ooo() 
> #252): python UNO bridge successfully initialized

The python module interfacing OOo is loaded.

> 2009-07-07 10:19:00  ERROR     gm.forms 
> (/home/jbusser/gnucvs/gnumed/gnumed/Gnumed/business/gmForms.py::_get_desktop()
>  #294): Cannot connect to OOo server.
> Traceback (most recent call last):
>   File "/home/jbusser/gnucvs/gnumed/gnumed/Gnumed/business/gmForms.py", line 
> 292, in _get_desktop
>     self.remote_context = self.uri_resolver.resolve(self.remote_context_uri)
> com.sun.star.connection.NoConnectException: Connector : couldn't connect to 
> socket (Success)

But there is no OOo server running.

> 2009-07-07 10:19:01  ERROR     gm.forms 
> (/home/jbusser/gnucvs/gnumed/gnumed/Gnumed/business/gmForms.py::_get_desktop()
>  #295): Trying to start OOo server with: [oowriter -invisible 
> -accept="socket,host=localhost,port=2002;urp;"]

So it tries to start one (this is the command for starting
on manually, too).

> 2009-07-07 10:19:01  DEBUG     gm.forms 
> (/home/jbusser/gnucvs/gnumed/gnumed/Gnumed/business/gmForms.py::_get_desktop()
>  #304): waiting 45.0 seconds for OOo to start up
> 2009-07-07 10:19:46  ERROR     gm.forms 
> (/home/jbusser/gnucvs/gnumed/gnumed/Gnumed/business/gmForms.py::_get_desktop()
>  #309): Cannot start (or connect to started) OOo server. You may need to 
> increase <external.ooo.startup_settle_time>.
> Traceback (most recent call last):
>   File "/home/jbusser/gnucvs/gnumed/gnumed/Gnumed/business/gmForms.py", line 
> 307, in _get_desktop
>     self.remote_context       = 
> self.uri_resolver.resolve(self.remote_context_uri)
> com.sun.star.connection.NoConnectException: Connector : couldn't connect to 
> socket (Success)

But it still cannot connect. Since you are running in a VM
I'd try increasing the time to, say, 120 seconds or even
more.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346