Bug 154570 - LO Writer not saving macros globally on macOS (works in file)
Summary: LO Writer not saving macros globally on macOS (works in file)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.6.2 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL: https://ask.libreoffice.org/t/saving-...
Whiteboard:
Keywords:
Depends on:
Blocks: Macro
  Show dependency treegraph
 
Reported: 2023-04-02 18:21 UTC by Alexis
Modified: 2023-04-19 23:02 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexis 2023-04-02 18:21:44 UTC
LibreOffice 7.4.6.2 does not save macros on macOS Monterey.

Expected Behavior: Recorded and saved macros are available after quitting and relaunching LO.

Observed Behavior: Recorded and saved macros are not available after quitting and relaunching LO.

Steps to reproduce:

1. Launch LibreOffice, and select Create: Writer Document.

2. Type "Blah blah blah." and select the middle "blah".

3. Tools > Macro > Record Macro

4. Change some characteristic of the text, for example, click the Font Color icon to make it Dark Red 2.

5. Click Stop Recording, and save macro in MyMacros > Standard > Module1, using a name like "FontColor" by clicking "Save".

6. Save your document as "Blah.odt", and quit LibreOffice.

7. Launch LibreOffice and open Blah.odt.

8. Tools > Macros > Organize Macros > Basic… navigate to MyMacros > Standard > Module1 and Observe that FontColor is nowhere to be found.
Comment 1 Dieter 2023-04-09 20:52:08 UTC
Alexis, does it also happen in latest version 7.5.2.2?
=> NEEDINFO
Comment 2 Alexis 2023-04-10 16:16:51 UTC
(In reply to Dieter from comment #1)
> Alexis, does it also happen in latest version 7.5.2.2?
> => NEEDINFO

No idea, I only use the production version.
Comment 3 QA Administrators 2023-04-11 03:19:02 UTC Comment hidden (obsolete)
Comment 4 raal 2023-04-13 18:39:22 UTC
No repro with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 60bce1af8aab2115d603781193bb659b35d1aedb
CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded
Comment 5 Buovjaga 2023-04-14 14:04:33 UTC
(In reply to Alexis from comment #2)
> (In reply to Dieter from comment #1)
> > Alexis, does it also happen in latest version 7.5.2.2?
> > => NEEDINFO
> 
> No idea, I only use the production version.

7.5 is a production version, just more recent with new features etc. But you could try with an unstable version, so you don't have to replace your stable one: https://dev-builds.libreoffice.org/daily/master/current.html
Comment 6 Alexis 2023-04-14 15:58:15 UTC
(In reply to Buovjaga from comment #5)
> (In reply to Alexis from comment #2)
> > (In reply to Dieter from comment #1)
> > > Alexis, does it also happen in latest version 7.5.2.2?
> > > => NEEDINFO
> > 
> > No idea, I only use the production version.
> 
> 7.5 is a production version, just more recent with new features etc. But you
> could try with an unstable version, so you don't have to replace your stable
> one: https://dev-builds.libreoffice.org/daily/master/current.html

If you feel other versions, other OSes, etc. should be checked out, you are quite welcome to do so.

As a non-dev user of LO I am happy to make bug reports on my set ups. I am not inclined to create more elaborate work flows for myself. If doing so is a precondition of filing actionable bug reports, then I fear I, and other users in a similar position will simply be taught to not bother to file bug reports, with consequences for the quality of LO.
Comment 7 Buovjaga 2023-04-14 17:14:00 UTC
(In reply to Alexis from comment #6)
> If you feel other versions, other OSes, etc. should be checked out, you are
> quite welcome to do so.
> 
> As a non-dev user of LO I am happy to make bug reports on my set ups. I am
> not inclined to create more elaborate work flows for myself. If doing so is
> a precondition of filing actionable bug reports, then I fear I, and other
> users in a similar position will simply be taught to not bother to file bug
> reports, with consequences for the quality of LO.

Quite the contrary. Our user base is extremely active and helpful when it comes to bug reports. Not only that, but we get a constant stream of quality assurance volunteers from outside the project and they receive methodical training. There is no expectation of having a developer background.

I am sure we will get macOS testers to help with this report, but the best person to provide additional and up-to-date information regarding the report is yourself, of course.
Comment 8 Stéphane Guillou (stragu) 2023-04-19 23:02:48 UTC
I could reproduce with:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: fc6806c4be8585ce0d35a6b581bf8b3dbf858500
CPU threads: 2; OS: Mac OS X 13.2.1; UI render: Skia/Raster; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

and:

Version: 7.4.6.2 / LibreOffice Community
Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d
CPU threads: 2; OS: Mac OS X 13.2.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

A recorded macro is persistent when saved in the file, but not when saved in My Macros.

Seems someone else was having the same issue in 7.3: https://ask.libreoffice.org/t/saving-macros-in-calc/79745
And another on 7.4: https://ask.libreoffice.org/t/i-have-a-disappearing-macro/84339/4

Not reproduced on Linux:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 61b41646c5a93ca24f2c9f143cdb0da2c9258989
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded