Created attachment 50616 [details] typescript with gdb backtrace I am working on ubuntu-natty (11.04) with a local build from commit id c305f3c (2011-08-25); autogen.lastrun shows --with-linked-git=/home/terry/lo_hacking/git/libo/clone --with-external-tar=/home/terry/lo_hacking/git/libo/src --disable-mozilla --enable-symbols --enable-dbgutil --enable-crashdump --disable-build-mozilla --without-junit This first happened as I was generally playing around the edges of the "MacroSecurity..." button failing to display the expected dialog <http://listarchives.documentfoundation.org/www/discuss/msg07479.html>. That button is still disabled, and my registrymodification.xcu lacks the string MacroSecurityLevel. I have created the crash under gdb, thusly ... (*) Start work in empty Writer document "Untitled 1" (*) Take menu options Help > "About LibreOffice". Program displays About dialog. Note the build ID. (*) Click OK. (*) Take menu options Tools > Macros > "Organize Macros" > "LibreOffice Basic..." . Program presents dialog "LibreOffice Basic Macros"; the pane "Macro from" includes "Untitled 1". (*) Expand "Macro from" > "Untitled 1". Program shows that "Untitled 1" is empty. (*) Click "Untitled 1" in the "Macros from" pane. Program enables New button. (*) Click New. Program displays "New Module" dialog with Name control showing default value "Module 1". (*) Click OK. gdb reports SIGSEGV. I am attaching typescript of the gdb session. The SIGSEGV appears about 80 lines in. After gdb ended, the program displayed dialog box "Due to an unexpected error ...", naming the files to be recovered as rzkh.odb, "Untitled 1", and "Untitled 1". Yes, "Untitled 1" appears twice. For comparison, build id aa51fd4 (around 2011-08-15) also ignores the MacroSecurity... button, but it does let me enter a basic command and execute the macro. However, the attempt to open a (database) document with macros provoke the warning that "execution of macros is disabled due to the current macro security setting".
This works for me.
I couldn't reproduce this, but I could see some oddities under valgrind which *might* have been the trigger for this, fixed what I could see with... http://cgit.freedesktop.org/libreoffice/core/commit/?id=fa9ff01fe4731a5d91da60ec3f5c2cafa7b3f382 Can you try again and see if that made any difference.
MacroSecurity button is indeed unavailable in a mozilla-disabled build seeing as the dialog is in libxmlsecurity and that's not build with no mozilla. Probably should rearrange things so libxmlsecurity is still built and installed even with no mozilla in order to get the dialogs etc which don't depend on xmlsignature support.
Fixed the no-mozilla->no macro security UI with http://cgit.freedesktop.org/libreoffice/core/commit/?id=0a18f6bef456084e92e3f6700ca8ab80ba20d14d
http://cgit.freedesktop.org/libreoffice/core/commit/?id=aa584559a8ada4e31331ab8a23f2c09eb11c609b I mean Anyway, I can't reproduce the exact first crash, but fixed something that might be the cause, and the macro security dialog with --disable-mozilla is fixed also
Thank you. It is working like a charm.