https://bugs.documentfoundation.org/show_bug.cgi?id=156352
--- Comment #32 from Patrick Luby <[email protected]> --- (In reply to steve from comment #31) > It is funny, because at least once the process worked as expected and the > key list of public keys was shown and an encrypted document was saved which > asked for the yubikey to be connected on open, where the OpenPGP secret key > part is stored. > > Then in the next test round I am not seeing the public key list and LO > crashes and shows the error dialog. In a third round the crash happens again. > > Hope the crash log is useful. Maybe all those crashes are still cases of > https://bugs.documentfoundation.org/show_bug.cgi?id=152524 after all and > while LO no longer crashes on open, the crash now happens as soon as any > OpenPGP operation is called? You are correct: the crash is still a case of tdf#152524. But it is now in a separate thread, not the main thread. What is really noticeable to me about your latest crash is that there is only one thread listed and that is the same old fork() in gpgme. What I don't understand is where is the main thread in your latest crash log? The main thread is blocked waiting for the thread that crashed so the main thread should still be alive at the time of crash. But it isn't. Instead, the gpgme thread is thread 0. That makes me suspect that the gpgme code corrupts memory after some number of times gpg is executed. My code only tries to ensure that LibreOffice doesn't execute gpg until a previous gpg is completely finished. That seems to only delay the inevitable so maybe your particular OpenPGP data or configuration trigger a bug in gpgme code? -- You are receiving this mail because: You are the assignee for the bug.
