Bug 156298 - Recorded macro in Writer is not saved when program quits in LibreOffice 7.3.7.2 new
Summary: Recorded macro in Writer is not saved when program quits in LibreOffice 7.3.7...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
7.3.7.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-15 11:24 UTC by William
Modified: 2024-04-06 03:15 UTC (History)
1 user (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 William 2023-07-15 11:24:55 UTC
Description:
Using LibreOffice 6 I had recorded and saved several Basic macros in Writer (Library Standard Module1). Now in LibreOffice 7.3 I tried to record and save a simple macro. It works while I am using the program, but if the system closes the program, the macro is not saved. This behaviour is new in version 7.3
I have also updated to Ubuntu 22 on my Slimbook laptop Essential15.  

Steps to Reproduce:
1.record and save a macro
2. let Ubuntu close down all programs
3.restore Writer file and test the macro

Actual Results:
Click icon to record macro in Writer
press space bar
stop recording
save macro in Library Standard Module1 as "sp"
CTRL-S to save file
Assign "sp" to key CTRL-[space]
test by pressing CTRL-[space] -- successful
Allow computer to close down and close all programs automatically
Turn on computer and restore all active Writer files -- succeeds
Test the macro by pressing CTRL-[space] in any text -- fails,
with error message that the macro "sp" cannot be found.

Expected Results:
macro "sp" should appear in list of defined macros


Reproducible: Always


User Profile Reset: No

Additional Info:
Manually closing the file and re-opening it did not remove the problem. I will try manually quitting LibreOffice. 
I do not know why Ubuntu is closing down -- I would normally expect it to Suspend and keep files open. But in any case I never had this problem for LibreOffice 6 even when Ubuntu closed the application and I had to recover the files. I have not tried resetting my profile
Comment 1 Buovjaga 2023-09-07 15:55:24 UTC
(In reply to William from comment #0)
> Click icon to record macro in Writer
> press space bar
> stop recording
> save macro in Library Standard Module1 as "sp"
> CTRL-S to save file

You don't specify where you are saving the macro in. You mention Ctrl-S to save file, but if you save the macro into My Macros, it will not be tied to any document. I think that what you want is to have the macro + keyboard shortcut work globally, so you don't want to tie it to any single document.

I can kill LibreOffice just fine after saving the macro to My Macros and assigning to a shortcut, because the information is written to the disk.

Please clarify.
Comment 2 QA Administrators 2024-03-06 03:14:23 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2024-04-06 03:15:12 UTC
Dear William,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp