Re: KMail: segfault on trying to send GPG encrypted mail
Hey Sandro. Sandro Knauß - 11.12.20, 23:25:54 CET: > > Do you want me to file a bug report? If so, against which package? > > > >From the backtrace you see that it is messagecomposer, that is inside > >the > messagelib package. But no need to file a bug, there is already a > patch prepared for the next upload: > > https://salsa.debian.org/qt-kde-team/kde/messagelib/-/blob/master/ debian/patches/upstream-FIX-messagecomposer-cryptocomposertests-Use- EncryptJ.patch Thank you very much. I just updated to KDEPIM 20.08.3 and can confirm that encryption and signing works nicely again! Best, -- Martin
Re: KMail: segfault on trying to send GPG encrypted mail
Hi Sandro. Sandro Knauß - 11.12.20, 23:25:54 CET: > > Do you want me to file a bug report? If so, against which package? > From the backtrace you see that it is messagecomposer, that is > inside the messagelib package. But no need to file a bug, there is > already a patch prepared for the next upload: Great! Thank you a lot, Sandro! Best, -- Martin
Re: KMail: segfault on trying to send GPG encrypted mail
Hey, > Do you want me to file a bug report? If so, against which package? >From the backtrace you see that it is messagecomposer, that is inside the messagelib package. But no need to file a bug, there is already a patch prepared for the next upload: https://salsa.debian.org/qt-kde-team/kde/messagelib/-/blob/master/debian/ patches/upstream-FIX-messagecomposer-cryptocomposertests-Use-EncryptJ.patch hefee signature.asc Description: This is a digitally signed message part.
Re: KMail: segfault on trying to send GPG encrypted mail
Hey, > So doing asynchronous operations at the same time is supposed to be safe. > FWIW I don't know anything about the code you're referring to, but perhaps > it's no longer coordinating use of the synchronous functions, or it's just > uncovered a GPGME bug. Sorry, I have too may hats here to as I also be part of upstream. When I was moving the code to an asynchronous code in March the tests were run successfully. Than I saw in August that the tests are failing with no further changes on kdepim side. So it is properly a gpg issue. But nobody told me that there is also a real bug, so I thought, it is only a test issue, that I can ignore, that's why I haven't rushed to get the patch merged: https://invent.kde.org/pim/messagelib/-/merge_requests/14 hefee signature.asc Description: This is a digitally signed message part.
Re: KMail: segfault on trying to send GPG encrypted mail
On Saturday, November 21, 2020 11:29:32 AM EST Sandro Knauß wrote: > I can reproduce this issue and also have an idea what is wrong in the code. > Encrypt uses the async method of gnupg and sign+encrypt till using the old > non-async method. It seems like gnupg has changed something in the last > version(s) and the async method breaks somehow. I've seen this issue also for other parts. I'll try to create a patch the next weeks. GnuPG hasn't been updated in a while though and neither has GPGME. The GPGME manual says > Only one thread at any time is allowed to call gpgme_wait. If multiple > threads call this function, the caller must make sure that all invocations > are fully synchronized. It is safe to start asynchronous operations while a > thread is running in gpgme_wait. So doing asynchronous operations at the same time is supposed to be safe. FWIW I don't know anything about the code you're referring to, but perhaps it's no longer coordinating use of the synchronous functions, or it's just uncovered a GPGME bug. signature.asc Description: This is a digitally signed message part.
Re: KMail: segfault on trying to send GPG encrypted mail
Hi Sandro. Sandro Knauß - 21.11.20, 17:29:32 CET: > I can reproduce this issue and also have an idea what is wrong in the > code. Encrypt uses the async method of gnupg and sign+encrypt till > using the old non-async method. It seems like gnupg has changed > something in the last version(s) and the async method breaks somehow. > I've seen this issue also for other parts. I'll try to create a patch > the next weeks. Thank you very much. Do you want me to file a bug report? If so, against which package? Best, Martin > > > I found out yesterday that trying to send a GPG encrypted mail > > > gives > > > > > > KMail got signal 11 (Exiting) > > > > > > after confirming the encryption related dialog windows. > > > > Same here on an up-to-date Sid. > > > > A trivial workaround is to also sign the message. > > > > @++ -- Martin
Re: KMail: segfault on trying to send GPG encrypted mail
Hey, I can reproduce this issue and also have an idea what is wrong in the code. Encrypt uses the async method of gnupg and sign+encrypt till using the old non-async method. It seems like gnupg has changed something in the last version(s) and the async method breaks somehow. I've seen this issue also for other parts. I'll try to create a patch the next weeks. hefee -- > > I found out yesterday that trying to send a GPG encrypted mail gives > > > > KMail got signal 11 (Exiting) > > > > after confirming the encryption related dialog windows. > > Same here on an up-to-date Sid. > > A trivial workaround is to also sign the message. > > @++ signature.asc Description: This is a digitally signed message part.
Re: KMail: segfault on trying to send GPG encrypted mail
Hi, > I found out yesterday that trying to send a GPG encrypted mail gives > > KMail got signal 11 (Exiting) > > after confirming the encryption related dialog windows. Same here on an up-to-date Sid. A trivial workaround is to also sign the message. @++ -- Cyril Lacoux -- BOFH excuse #287: Telecommunications is downshifting.
Re: KMail: segfault on trying to send GPG encrypted mail
Am Freitag, 13. November 2020, 17:33:44 CET schrieb Martin Steigerwald: > I found out yesterday that trying to send a GPG encrypted mail gives > > KMail got signal 11 (Exiting) > > after confirming the encryption related dialog windows. It's similar on Debian sid with Plasma 5.20 from Norbert Preining's repo. The output is: 'org.kde.pim.kmail: Danger, using an event loop, this should no longer be happening! Received the SIGALRM signal (the alarm clock rings)' -- Gruß Helge
KMail: segfault on trying to send GPG encrypted mail
Hi! On Debian Sid, as of yesterday I think. But had new Plasma with experimental packages before. I found out yesterday that trying to send a GPG encrypted mail gives KMail got signal 11 (Exiting) after confirming the encryption related dialog windows. Before I dig deeper into it: Anyone else with this issue? Anyone any clue what this might be? It worked before, so I bet it may have to do with some less than optimal version mix or so. 'dpkg -l | grep 5.17' shows no result however. Best, -- Martin
