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
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 u
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/me
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
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
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 th
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 issu
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:
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 P
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 els
10 matches
Mail list logo
