Summary: | [7.5] Every (empty) document warns about macros (policies.xcd) | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | klar+tdf |
Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | ilmari.lauhakangas |
Priority: | medium | ||
Version: | 7.5.0.3 release | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Windows (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Attachments: | Registry file |
Description
klar+tdf
2023-02-08 10:31:05 UTC
Created attachment 186258 [details]
Registry file
For testing with 7.5, I placed the file in /usr/lib/libreoffice/share/registry/res and I could reproduce the problem. However, with 7.6 I could not reproduce. I checked that in Tools - Options - LibreOffice - Security, the setting was Very High as expected. Can you check with 7.6? Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away. Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 98cf5157d69d9f1692be7f2cac958b1dfb387ca9 CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 28 March 2023 How do I obtain the 7.6 alpha for Windows? And will this problem be fixed in 7.5 so we can use LibreOffice after June 12, 2023? Thanks for reaching out. (In reply to klar+tdf from comment #3) > How do I obtain the 7.6 alpha for Windows? And will this problem be fixed in > 7.5 so we can use LibreOffice after June 12, 2023? Thanks for reaching out. Win-x86_64@tb77-TDF https://dev-builds.libreoffice.org/daily/master/current.html I can confirm that the behavior is gone in 7.6.0.0.alpha0. Thank you. The bug persists in the recently released version 7.5.3. Because of the fact that LO 7.4 reaches end of life in exactly a month we need a solution to be able to use LibreOffice in the future. Is there a patch for the 7.5 product line? Thank you. Somebody would need to bisect what change fixed it. In any case, reopened status is wrong. |