Bug 40447 - CONFIGURATION: Macro security dialog does not open
Summary: CONFIGURATION: Macro security dialog does not open
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
Master old -3.6
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks: mab3.5
  Show dependency tree / graph
 
Reported: 2011-08-29 00:46 UTC by Rainer Bielefeld Retired
Modified: 2011-11-23 07:33 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Bielefeld Retired 2011-08-29 00:46:22 UTC 
With Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID: f952331-4eb4f62-09af278)]", installed due to <http://wiki.documentfoundation.org/Testing_Daily_Builds>, <http://wiki.documentfoundation.org/Installing_in_parallel>:

Steps to reproduce:
0. Start LibO Master Start Center
1. Open new Writer document from  Start Center
2. Menu 'Tools -> Options -> Security' click button 'Macro Security'
   Expected: Macro security dialog will open
   Actual: Button shows "click reaction", but nothing happens, no new dialog
           opens
Comment 1 Rainer Bielefeld Retired 2011-08-29 01:27:18 UTC 
Wrong OS
Comment 2 Cor Nouws 2011-09-02 01:02:33 UTC 
no problem in Build ID: 6ecb780-4eb4f62-09af278 on Linux
Comment 3 Caolán McNamara 2011-09-07 16:08:48 UTC 
From which tinderbox does the failing build come from, this may be a side effect of a mozilla-disabled build.
Comment 4 Rainer Bielefeld Retired 2011-09-07 23:22:32 UTC 
@Caolán:
I see that in the latest builds from
<http://dev-builds.libreoffice.org/daily/Windows_XP_SP3/>

Was OK with a Master Build in July from Provo_Windows_x86_Tinderbox(?).
Comment 5 Lionel Elie Mamane 2011-11-23 06:09:57 UTC 
Confirming on Debian GNU/Linux.

I traced the code, basically dlopen("/path/to/libxsec_xmlsec.so") returns NULL.
Comment 6 Lionel Elie Mamane 2011-11-23 06:29:54 UTC 
With sal/osl/unx/module at OSL_DEBUGLEVEL 2:



Trace 23071/1: "Error osl_getAsciiFunctionSymbol:
/home/master/src/libreoffice/core/solver/unxlngx6/installation/opt/program/../program/libxmlsecurity.so:
undefined symbol: xmlsecurity_component_getImplementationEnvironmentExt"
Trace 23071/1: "Error osl_getAsciiFunctionSymbol:
/home/master/src/libreoffice/core/solver/unxlngx6/installation/opt/program/../program/libxmlsecurity.so:
undefined symbol: xmlsecurity_component_getImplementationEnvironment"
Trace 23071/1: "Error osl_getAsciiFunctionSymbol:
/home/master/src/libreoffice/core/solver/unxlngx6/installation/opt/program/../program/libxmlsecurity.so:
undefined symbol: component_canUnload"
Trace 23071/1: "Error osl_loadModule:
/home/master/src/libreoffice/core/solver/unxlngx6/installation/opt/program/../program/libnssutil3.so:
version `NSSUTIL_3.12.5' not found (required by
/home/master/src/libreoffice/core/solver/unxlngx6/installation/opt/program/../program/libnss3.so)"
Error: loading component library failed:
file:///home/master/src/libreoffice/core/solver/unxlngx6/installation/opt/program/../program/libxsec_xmlsec.so
From File /home/master/src/libreoffice/core/cui/source/options/optinet2.cxx at
Line 874
Comment 7 Lionel Elie Mamane 2011-11-23 06:51:48 UTC 
Recompiling moz module fixes this issue for me.
Comment 8 Rainer Bielefeld Retired 2011-11-23 06:56:13 UTC 
For me the problem does no longer exist with with Server installation of Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) ENGLISH UI [(Build ID:  4f11d0a-adcf6d5-c4bb9bd)]" Windows_2008R2 - 111118) and also not with  parallel installation of MinGW Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID:  7ba7cba-5d03837-adcf6d5-c4bb9bd)] (daily/MinGW_cross-compilation2011-11-26_02.11.53)"
Comment 9 Lionel Elie Mamane 2011-11-23 07:07:24 UTC 
Cannot reproduce with daily MinGW build: f7831ed-fd3abe7-8b4f344-2306b32
Comment 10 Lionel Elie Mamane 2011-11-23 07:08:14 UTC 
(In reply to comment #8)
> For me the problem does no longer exist

Closing then.
Comment 11 Caolán McNamara 2011-11-23 07:13:23 UTC 
I thought I fixed that with http://cgit.freedesktop.org/libreoffice/core/commit/?id=aa584559a8ada4e31331ab8a23f2c09eb11c609b

What are the configure options on the builds with this problem. Probably --disable-xmlsec I guess ?
Comment 12 Michael Meeks 2011-11-23 07:33:30 UTC 
works for me with a recent master build.