https://bugs.documentfoundation.org/show_bug.cgi?id=128744
László Németh <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #11 from László Németh <[email protected]> --- (In reply to Dieter from comment #9) > (In reply to László Németh from comment #8) > > @Dieter: According to the build ID 83d0f2eebae41d431d9a5bfd1a918523977752d0, > > your LO test build is from 26 Apr (see > > https://gerrit.libreoffice.org/c/core/+/126501), but this bug was fixed on 9 > > May. > > Thank you for your hint. I've just recognized, that installation of a more > recent version failed. But also with the following version problem is still > present: > > Version: 7.4.0.0.alpha1 (x64) / LibreOffice Community > Build ID: b871abad383583f02eb49c7e49aeae01f6941072 > CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: > win > Locale: de-DE (de_DE); UI: en-GB > Calc: CL > > => REOPENED @Dieter: Thanks for testing! It seemed for me, that the test document mentioned in the report has a different password, not "test". I've attached a new one (the unit test document of the patch), where I copied an MSO generated "test" password of locked editing to lock changeTracking. Otherwise, it would be fine to check both test documents in MSO 2019, where this encryption is supported. -- You are receiving this mail because: You are the assignee for the bug.
