https://bugs.documentfoundation.org/show_bug.cgi?id=153601

Stéphane Guillou (stragu) <stephane.guil...@libreoffice.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Can't save a document with  |Crash when saving a
                   |gpg-key encryption anymore  |document with gpg-key
                   |(Crash-ID:                  |encryption (
                   |11aa9d0d-6795-42a7-bb41-9a5 |EXCEPTION_ACCESS_VIOLATION_
                   |6574fe192)                  |READ )
                 CC|                            |stephane.guillou@libreoffic
                   |                            |e.org
    Crash report or|11aa9d0d-6795-42a7-bb41-9a5 |static struct
    crash signature|6574fe192                   |com::sun::star::util::DateT
                   |                            |ime `anonymous
                   |                            |namespace'::convertUnixTime
                   |                            |ToDateTime(__int64)
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEEDINFO

--- Comment #9 from Stéphane Guillou (stragu) 
<stephane.guil...@libreoffice.org> ---
I installed Gpg4win (which bundles Kleopatra) from
https://www.gpg4win.org/get-gpg4win.html
Then created a keypair with it, then opened LO and saved with encryption, and I
could see and use the key successfully.

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d887b6a6fa2a572f48498839c5a68791c3196634
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: threaded

7.4.5.1 also worked as expected.

Regarding this type of "EXCEPTION_ACCESS_VIOLATION_READ" issue, maybe some
troubleshooting like
https://windowsreport.com/exception-access-violation-windows-10/ could help?
Wondering if the issue is not necessarily on our end.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to