I've noticed this before also - quite annoying. Glad you reported it :)


Marking as:

New
Minor - doesn't prevent high quality work but slows it down and is quite annoying
High - makes users think a macro exists still, anyone who had a macro and deletes it will be affected

ProposedEasyHack


Confirmed on:
4.2 Master built last week
Bodhi Linux x64

In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval.

Thank you and apologies for the noise

@Richard - I think that this issue has been resolved. Can you verify that this is the case with 4.4.1.2 or newer and mark the bug as RESOLVED -> WORKSFORME?

This bug still exists in version 5.4.2.2.

I have an ODS calc file that I have deleted macros from. I tried renaming .config/libreoffice/4 in case there was a problem in there, but no change.

OS: slackware 14.2 64bit.
LibreOffice: 5.4.2.2

Just deleting all of the macro code (which to all appearances is the only way to delete this stuff) is not enough to get rid of the macro warning.

However, I just found a way to get rid of the entire VBAMacros library. Go to the Macros Organizer (Tools - Macros - Organize Dialogs), switch to the libraries tab and set the location as your file. Then you can select the VBAMacros library and delete it.

After that, no more prompts.

Created attachment 148157 [details]
Minimal example to provoke bug

This is a copy of my file from which I've deleted all the data except for two sheets, which I've renamed as sheet1 and sheet2 and deleted all the content. AS is is, opening it provokes the "has macros" message. Deleting either of the two sheets gets rid of the message

The bug is still present in LibreOffice Version: 6.1.3.2.

Tools->Macros->Run Macro... doesn't show any macros in the file.
Tools->Macros->Organise Macros->LibreOffice Basic... doesn't show any macros in the file.
Tools->Macros->Organise Macros->JavaScript... doesn't show any macros in the file.
Tools->Macros->Organise Macros->Python... doesn't show any macros in the file.
Tools->Macros->Organise Dialogs... doesn't show any macros in any of its tabs.

I do have a global My Macros file, but this doesn't provoke the error message with any of my other spreadsheets.

(In reply to Richard Parkins from comment #8)
> Minimal example to provoke bug
The code that identifies the "presence" of the macros is in sfx2/source/doc/docmacromode.cxx.

So, ODS files are just zip files.  I believe that the presence of Basic folder with script files in it triggers the macros.  I was able to unzip the file, delete the Basic folder, and re-zip the file to avoid the macro problem.

I didn't see anywhere in the code that could have accomplished this. One thing to investigate is why the "delete" button cannot delete these things in the modules area.

When editing the macros, when you double click on "sheet2", it pops up the code tab with Sub Main/End Sub.  Right clicking on the tab gives a delete option, but then the empty code file is just re-created again.

if I force to module dialog code to enable the delete button (basctl/source/basicide/moduldlg.cxx), it still fails to actually delete the Document Object, so I give up.

(In reply to Justin L from comment #11)
> (In reply to Richard Parkins from comment #8)
> > Minimal example to provoke bug
> The code that identifies the "presence" of the macros is in
> sfx2/source/doc/docmacromode.cxx.
> 
> So, ODS files are just zip files.  I believe that the presence of Basic
> folder with script files in it triggers the macros.  I was able to unzip the
> file, delete the Basic folder, and re-zip the file to avoid the macro
> problem.
> 
> I didn't see anywhere in the code that could have accomplished this. One
> thing to investigate is why the "delete" button cannot delete these things
> in the modules area.

There are several zip algorithms supported by Linux. In order to replicate the solution that you describe, I need to know which algorithm to use to re-zip the file. I tried zipinfo on the original file, but it doesn't tell me.

(In reply to Richard Parkins from comment #14)
> I need to know which algorithm to use to re-zip the file.
I just used "zip" from the command line, which is Info-Zip 3.0 in my case.

(In reply to Justin L from comment #15)
> (In reply to Richard Parkins from comment #14)
> > I need to know which algorithm to use to re-zip the file.
> I just used "zip" from the command line, which is Info-Zip 3.0 in my case.

OK, thanks. That fixes my original file, so it looks as if it a good workaround.

However IMHO the bug (deleting macros not removing the warning) still needs to be fixed.

looks depending on the - not very well defined? - ole object, embedded and represented by the white square at https://www.wowessays.com/ A14:B20 , 

1. insert row - undo - crash, 

2. F5 - ole objects - object1 - delete 
insert row - undo - no crash, 

2a. click on object - delete (worked not on all attempts) 
insert row - undo - no crash, 

3. undo until ole object present again 
insert row - undo - no crash, 

4. close without save, reload file, 
insert row - undo - crash, 

5. steps 1-3, save file, 
reopen - insert row - undo - crash, 

steps 3. - 4. no 'stable reproducibility', 

played with ver. 6.4.0.1, 6.4.0.2, 7.0.0.0

I escalated the importance to normal as a user will be worried that he has unknown/not found macro in his document.

*** Bug 146920 has been marked as a duplicate of this bug. ***

*** Bug 124314 has been marked as a duplicate of this bug. ***

For DOCM files, simply saving as DOCX gets rid of macros (in 7.6) thanks to bug 125338.