Bug 119842

Summary: Crash in: vcl::Window::EnableInput(bool,bool) after opening .ods with signed macro
Product: LibreOffice Reporter: j.j.berkhout
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED NOTOURBUG    
Severity: normal CC: j.j.berkhout, xiscofauli
Priority: medium    
Version: 6.0.5.2 release   
Hardware: x86-64 (AMD64)   
OS: Windows (All)   
See Also: https://crashreport.libreoffice.org/stats/signature/vcl::Window::EnableInput(bool,bool)
Whiteboard:
Crash report or crash signature: ["vcl::Window::EnableInput(bool,bool)"] Regression By:
Attachments: .ods file with macro in development (my first...)
.ods with signed macro in development

Description j.j.berkhout 2018-09-13 12:34:00 UTC 
Created attachment 144836 [details]
.ods file with macro in development (my first...)

This bug was filed from the crash reporting server and is br-892eee95-3268-4e1b-8b8e-73994c4d4838.
=========================================
Calc spreadsheet in .ods format.  This file contains  a macro signed by myself with  an OpenPGP key.  After opening, a popup window appears stating:
"The document contains document macros signed by:"
followed by a blank line (so no certificate information).
If I now click on the "View Signatures..." button, LO crashes.
OpenPGP installed is GnuPG for Windows version 2.2.10
I installed version LO 6.0.6.2, result is the same.
OS: Windows 7 latest service pack, all updates current as of 13 september.
Spreadsheet is attached.
Comment 1 j.j.berkhout 2018-09-13 12:44:14 UTC 
Created attachment 144838 [details]
.ods with signed macro in development
Comment 2 Xisco Faulí 2018-09-13 13:39:20 UTC 
I don't see the mentioned banner, are you sure you attached the correct file with a signed macro ?
Comment 3 j.j.berkhout 2018-09-13 15:39:47 UTC 
Sorry to be a bit late with my response.
It seems I had 2 versions of gpg4win: the newest one (3.1.3) and a version 2.3.0.
I found out that path definitions were clobbered.  I uninstalled both, removed some registry entries, rebooted and reinstalled 3.1.3.
After this: no more crashes, macro is signed.
However, if I try to start the Certificate Manager, it can't find it.  Oh well, no big deal.
Sorry for a perhaps too early bug report.