To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69642
                 Issue #|69642
                 Summary|unopkg fails when Setup.xcu is missing
               Component|framework
                 Version|OOo 2.0.4
                Platform|Opteron/x86_64
                     URL|
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|tm
             Reported by|hatapitk





------- Additional comments from [EMAIL PROTECTED] Mon Sep 18 07:24:08 -0700 
2006 -------
On Linux it is impossible to use unopkg if some of the user configuration 
files have not been created. This is a problem, because when installing uno 
extensions for all users, installation is usually done as root. And root never 
runs OOo directly.

Steps to reproduce:
c2:~# rm -r .openoffice.org2
c2:~# /opt/openoffice.org2.0/program/unopkg list

ERROR: (com.sun.star.lang.WrappedTargetRuntimeException) { { { Message 
= "[context=\"user\"] caught unexpected exception!", Context = 
(com.sun.star.uno.XInterface) @0 } }, TargetException = (any) { 
(com.sun.star.uno.Exception) { Message = "Invalid language string.", Context = 
(com.sun.star.uno.XInterface) @0 } } }

unopkg failed.
c2:~#

This problem can be worked around as follows:
c2:~# rm -r .openoffice.org2
c2:~# mkdir -p .openoffice.org2/user/registry/data/org/openoffice
c2:~# cp /tmp/Setup.xcu .openoffice.org2/user/registry/data/org/openoffice/
c2:~# /opt/openoffice.org2.0/program/unopkg list
all deployed user packages:
<none>

It is sufficient for Setup.xcu to contain the followin lines:
<?xml version="1.0" encoding="UTF-8"?>
<oor:component-data xmlns:oor="http://openoffice.org/2001/registry"; 
xmlns:xs="http://www.w3.org/2001/XMLSchema"; oor:name="Setup" 
oor:package="org.openoffice">
 <node oor:name="L10N">
  <prop oor:name="ooLocale" oor:type="xs:string">
   <value>xxx</value>
  </prop>
 </node>
</oor:component-data>

The xxx in within value tags is just to demonstrate that it does not matter if 
the language string actually is valid, it just has to be present and not 
longer than three characters.

This bug is present in version OOD680_m4 but it is not present in 2.0.3.

One important feature that is broken by this is installation of OOo extensions 
through Debian package management system:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=387224
This is especially bad for Finnish users who rely on third party components to 
provide spellchecking and hyphenation capabilities for OOo.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to