Bug 169790 - BASIC Macro code not shown and can't be edited
Summary: BASIC Macro code not shown and can't be edited
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
25.8.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-02 11:31 UTC by Jürgen Pitz
Modified: 2025-12-03 09:05 UTC (History)
2 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 Jürgen Pitz 2025-12-02 11:31:12 UTC 
Description:
BASIC Macro code not shown and can't be edited

Steps to Reproduce:
1.Start LO Calc
2.Goto Tools->Macros->Edit Macros
3.Try to edit a macro e.g MyMacros & Dialogs/Standard/Module1/Main


Actual Results:
The editor area is empty. Nothing can be edited.

Expected Results:
Same behavior as in version 25.2.7.2: An empty procedure main is shown and can be edited.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 25.8.3.2 (X86_64)
Build ID: 8ca8d55c161d602844f5428fa4b58097424e324e
CPU threads: 20; OS: Windows 11 X86_64 (build 26200); UI render: Skia/Raster; VCL: win
Locale: en-US (C); UI: en-US
Calc: threaded
Comment 1 Werner Tietz 2025-12-02 11:58:06 UTC 
cannot confirm!

@Jürgen Pitz: does it work if you **⇒Help⇒Restart in SafeMode**?
Comment 2 Jürgen Pitz 2025-12-02 13:21:53 UTC 
It happens as well if I restart in SafeMode. I can reproduce this behavior on two Laptops (one Windows 10, one Windows 11). After deinstalling 25.8.3.2 and installing 25.2.7.2 it works as expected.
Comment 3 Jürgen Pitz 2025-12-02 15:49:15 UTC 
Correction: 25.8.3.2 does not have this problem on the machine with Windows 10. I mixed this up with an earlier problem which is already fixed. Sorry!
Comment 4 Xisco Faulí 2025-12-03 09:05:19 UTC 
(In reply to Jürgen Pitz from comment #3)
> Correction: 25.8.3.2 does not have this problem on the machine with Windows
> 10. I mixed this up with an earlier problem which is already fixed. Sorry!

Thanks for your feedback.
Let's close it as RESOLVED WORKSFORME then