Issue 73167 - cannot load Inspector.uno.pkg on Mac Intel
Summary: cannot load Inspector.uno.pkg on Mac Intel
Status: CLOSED DUPLICATE of issue 73952
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: OOo 2.2
Hardware: Mac Mac OS X, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: sparcmoz
QA Contact: issues@porting
URL:
Keywords:
Depends on: 69378
Blocks:
  Show dependency tree
 
Reported: 2007-01-05 10:54 UTC by sparcmoz
Modified: 2007-02-05 08:34 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
GNU/Linux SPARC (146.11 KB, image/png)
2007-01-05 10:58 UTC, sparcmoz
no flags Details
Mac PPC (244.84 KB, image/png)
2007-01-05 11:01 UTC, sparcmoz
no flags Details
Mac OSX Intel (57.87 KB, image/png)
2007-01-05 11:03 UTC, sparcmoz
no flags Details
running on m198 GNU/Linux SPARC (167.46 KB, image/png)
2007-01-05 20:03 UTC, sparcmoz
no flags Details
Inspector running on Mac Intel (332.27 KB, image/png)
2007-01-31 09:54 UTC, sparcmoz
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description sparcmoz 2007-01-05 10:54:53 UTC
I tried the new Inspector from the wiki:
http://wiki.services.openoffice.org/wiki/Object_Inspector
on three different platforms:
(a) Debian GNU/Linux SPARC 680_m5 (built with ecj through java-gcj-compat)
(b) Mac OSX 10.4 PPC (2.1 maho build)
(c) Mac OSX 10.4 Intel (2.1 maho build)
The Inspector appears to work correctly on PPC but cannot load on the others.
Please see attached screenshots for the error messages.
Any comments would be appreciated.
Comment 1 sparcmoz 2007-01-05 10:58:33 UTC
Created attachment 41909 [details]
GNU/Linux SPARC
Comment 2 sparcmoz 2007-01-05 11:01:31 UTC
Created attachment 41910 [details]
Mac PPC
Comment 3 sparcmoz 2007-01-05 11:03:23 UTC
Created attachment 41911 [details]
Mac OSX Intel
Comment 4 berend.cornelius 2007-01-05 13:05:28 UTC
bc: as discussed with sb I assign to him.
Comment 5 Stephan Bergmann 2007-01-05 13:22:45 UTC
Re (a):  sparc.png states that the Inspector.uno.rdb contained in the
Inspector.uno.pkg contains UNO type information for the interface type
org.openoffice.XInstanceInspector that is incompatible with information for that
interface type already available in the OOo installation.  I assume a bad OOo
installation.  @sparcmoz: Can you please retry with a new clean OOo installation
and a new empty OOo user directory?

Re (c):  I have no idea what goes wrong there.  Maybe somebody else with a
MacIntel can try to reproduce?
Comment 6 sparcmoz 2007-01-05 20:02:14 UTC
@sb: thankyou, I am able to run the Inspector on GNU/Linux SPARC after removing
the configuration ~/.openoffice.org2 This works with my m198 and Debian 2.1
builds - both are built with ecj. 
After adding the package, the OOo will crash when any attempt is made to access
the Extension Manager, this affects both Debian 2.1 and my m198. I will make a
separate issue for that.

The current issue now relates only to Mac Intel. 

Comment 7 sparcmoz 2007-01-05 20:03:28 UTC
Created attachment 41937 [details]
running on m198 GNU/Linux SPARC
Comment 8 shaunmcdonald131 2007-01-05 20:30:06 UTC
I can confirm that I get the same message as
http://www.openoffice.org/nonav/issues/showattachment.cgi/41911/intel.png
on 2GHz Intel Core Duo MacBook, 1GB RAM, OpenOffice.org 2.1 en-US from maho.
Comment 9 jjmckenzie 2007-01-08 04:51:35 UTC
Linked this to issue 69378 as both appear to be UNO problems on the Mac Intel.

James McKenzie
Comment 10 Stephan Bergmann 2007-01-08 12:40:20 UTC
@sparcmoz:  For lack of a MacIntel environment, maybe we can do some remote
debugging?  Your attached error box suggests that a call to
com::sun::star::uno::BaseReference::iquery_throw for type
com::sun::star::configuration::backend::XSingleLayerStratum fails on a null
reference.  A quick grep across the code base shows
configmgr/source/backend/multistratumbackend.cxx:1.11 to be the only file where
such calls are made.  Can you try with the below patch, whether this is indeed
the place where we fail and what the call stack looks like (abort is called, so
you can either start in a debugger, attach the debugger to a running soffice
before installing the extension, or debug the resulting core file).

RCS file: /cvs/util/configmgr/source/backend/multistratumbackend.cxx,v
retrieving revision 1.11
diff -u -r1.11 multistratumbackend.cxx
--- source/backend/multistratumbackend.cxx      16 Sep 2006 15:06:31 -0000     1.11
+++ source/backend/multistratumbackend.cxx      8 Jan 2007 12:33:31 -0000
@@ -645,6 +645,7 @@
                        }
                        else
                        {
+if(!mBackendStrata[i].is()){fprintf(stderr,"query A %d\n",i);abort();}
                                uno::Reference<backenduno::XSingleLayerStratum>
xSingleLayerStratum(
                                        mBackendStrata[i],
uno::UNO_REF_QUERY_THROW) ;
                                if (xSingleLayerStratum.is())
@@ -738,6 +739,7 @@
                        }
                        else
                        {
+if(!mBackendStrata[nStrataIndex].is()){fprintf(stderr,"query B
%d\n",nStrataIndex);abort();}
                                uno::Reference< backenduno::XSingleLayerStratum
> xSingleLayerStratum(
                                        mBackendStrata[nStrataIndex],
uno::UNO_REF_QUERY_THROW );

Comment 11 sparcmoz 2007-01-09 11:36:51 UTC
@sb: the trace produced no output so I added another to report reaching this
place. It turns out that A is passed often but not B. Also a debug build
produces this same message or similar, many times on loading and after: 
 jim$ ./soffice
query A is OK 0
query A is OK 2
query A is OK 3
Thread:      1 :SystemIntegration::getSupportingBackend - could not create
platform Backend: unsatisfied query for interface of type
com.sun.star.configuration.backend.XSingleLayerStratum!

This seems to be from configmgr/source/platformbe/systemintegrationmanager.cxx
line 71


...
Comment 12 Stephan Bergmann 2007-01-11 10:23:32 UTC
@sparcmoz:  Does the original error also happen when you install the extension
via command line

  <path-to>/program/unopkg add <path-to>/Inspector.uno.pkg

That might be easier to debug (when installed within OOo, an additional uno
executable is spawned, which might complicate matters).

Anyway, modifying cppu/source/cppu/cppu_opt.cxx:1.27

---8<---
extern "C" rtl_uString * SAL_CALL cppu_unsatisfied_iquery_msg(
    typelib_TypeDescriptionReference * pType )
    SAL_THROW_EXTERN_C()
{
    ...
    OUString ret( buf.makeStringAndClear() );
/*+*/if(ret.indexOf(OUString::createFromAscii("com.sun.star.configuration.backend.XSingleLayerStratum"))>=0){
/*+*/int dummy=0;//break here
/*+*/}
    rtl_uString_acquire( ret.pData );
    return ret.pData;
}
---8<---

might help to find out, in a debugger, more about the call stack of the failing
queryInterface (remember, there *might* be breaks at that place before the
problematic occurrence that leads to the error message is reached).
Comment 13 Stephan Bergmann 2007-01-18 12:45:16 UTC
@sparcmoz:  Feel free to assign back to me once we have more data.
Comment 14 sparcmoz 2007-01-21 05:26:31 UTC
for the first question: what happens via command line:

 jim$ ./unopkg add /Users/jim/Desktop/Inspector.uno.pkg

ERROR: (com.sun.star.uno.RuntimeException) { { Message = "unsatisfied query for
interface of type com.sun.star.configuration.backend.XSingleLayerStratum!",
Context = (com.sun.star.uno.XInterface) @0 } }

unopkg failed.
Comment 15 sparcmoz 2007-01-31 09:52:28 UTC
I have built m201 with cws macosxmapfiles and the Inspector can be loaded by gui
and command line, however the Extensions gui will always make a crash. After
being added, the Inspector seems to run OK. A screenshot of the running
inspector is attached. macosxmapfiles is not resynced to m201 yet so I will test
further when macosxmapfiles is integrated. 
Comment 16 sparcmoz 2007-01-31 09:54:04 UTC
Created attachment 42597 [details]
Inspector running on Mac Intel
Comment 17 sparcmoz 2007-02-03 04:22:23 UTC
@sb: thanks for your attention. Following integration of macosxmapfiles the
Inspector works and the issue now has become a simple crashing of the extension
manager which is a duplicate of issue 73952, where I have attached a patch.

*** This issue has been marked as a duplicate of 73952 ***
Comment 18 sparcmoz 2007-02-05 08:34:18 UTC
closed