On Tue, Jun 03, 2003 at 11:05:55AM +0200, Joerg Barfurth wrote:
> >I've just received this report about configmgr problems in our beta2
> >packages.  I'm not sure where do start investigating - do you have any
> >pointers where to start based on that error message?
> 
> Try to use a libcfgmgr2.so (built in configmgr) built with debug=t. Look 
> for assertion messages. Maybe break on 
> configmgr::OProviderImpl::clearTreeManager(). That method should not be 
> called before office shutdown, but I can't see a way to get the error 
> you indicate without it.

I can't reproduce this myself - I would have to get Stephane to do this.

> >The packages are built from the beta2 release plus some of the fixes on the
> >beta2 branch.  The only thing that might be of interest is that I am using
> >configimport to change the user locale.  It works for all other users but
> >here's the routine in case it might be causing a problem:
> 
> 
> >If you haven't got any ideas then I'll try and get hold of a backtrace of
> >the calc crash.
> 
> Judging from the below, it might be an unexpected or unhandled 
> exception. But I really have no idea what causes the exception in the 
> first place. Are you doing anything unusual to bootstraprc or 
> configmgrrc ? Do you place libraries in unusual places ?

No, nothing unusual.  Everything is installed under /usr/lib/openoffice1.1 in
the hierarchy as created by setup.

> >when I start 001.1-beta2, I get an large empty window with 
> >a menu and an error popup with the following message:
> >
> >>OpenOffice.org cannot be started due to an error 
> >>accessing the configuration data.
> >>Please contact tou system administrator.
> >>The following internal error as occured: GetStorage name: 
> >
> >file://home/chauveau/.openoffice/1.1/user/config/soffice.cfg:OProviderImpl:
> >
> >>No cache available - provider was already disposed.  
> 
> I have never seen that mix of errors (GetStorage + configuration) and as 
> mentioned, the second (configuration) part looks really dubious. Could 
> it be that one of the configuration files is broken (one of the 
> Common.xcu files is a favorite) ? What locale is being put into the 
> Setup.xcu by your script ? Is that locale available in 
> share/registry/res ? Do you run setup.bin at all ? are any errors 
> reported by setup.log ?

Joerg: The only configuration file modification that we do is the script
snippet that I posted in the original message.  I don't modify Common.xcu.
I don't run setup.bin directly - setup is run like this:

/usr/lib/openoffice1.1/program/setup -R:/etc/openoffice1.1/autoresponse.conf

autoresponse.conf looks like this:
        [ENVIRONMENT]
        INSTALLATIONMODE=INSTALL_WORKSTATION
        INSTALLATIONTYPE=WORKSTATION
        DESTINATIONPATH=<home>/.openoffice/1.1
        OUTERPATH=
        LOGFILE=

        [JAVA]
        JavaSupport=none

Stephane: Can you post the output of the 'locale' command from that user
account please, and also ~/.openoffice/1.1/setup.log?

> >The console output is
> >
> >># rm -rf .openoffice .sversionrc  ; openoffice1.1  
> >>OpenOffice.org for Debian - see 
> >>/usr/share/doc/openoffice.org1.1/README.Debian.gz
> >>running openoffice.org 1.1 setup...
> >>Try `uname --help' for more information.
> 
> Does it actually try to run setup -repair here ?

No, just the setup command line as you can see above.

> Hope that helps a little. It is pretty hard to diagnose this without 
> being able to look at the installation (and I don't have any debian 
> system around to try your special manipulations...).

Thanks for your efforts.  There really aren't a lot of special
manipulations, just the one language change I posted and workstation install
via autoresponse file.

The complete wrapper script is here:
  
http://cvs.debian.org/oo-debian-files/bin/openoffice?rev=1.13.2.3&cvsroot=debian-openoffice

Chris

Reply via email to