https://bugs.kde.org/show_bug.cgi?id=474477
Bug ID: 474477
Summary: Crash when switching mails while PGP verification is
still in progress
Classification: Applications
Product: kontact
Version: unspecified
Platform:
https://bugs.kde.org/show_bug.cgi?id=450824
Andre Heinecke changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=472086
--- Comment #5 from Andre Heinecke ---
@Laurent I like this bug here in a way because it shows how unilateral
decisions like just renaming all our libs for no unavoidable reason causes
headaches and tons of work for other people. For example I could
https://bugs.kde.org/show_bug.cgi?id=471911
--- Comment #2 from Andre Heinecke ---
I have referred this in our task to update the key selection dialog in KMail so
that we keep it in mind there. In that keyresolver this might already have been
fixed. https://dev.gnupg.org/T6198
--
You
https://bugs.kde.org/show_bug.cgi?id=471911
Andre Heinecke changed:
What|Removed |Added
CC||aheine...@gnupg.org
--- Comment #1 from Andre
https://bugs.kde.org/show_bug.cgi?id=452296
Andre Heinecke changed:
What|Removed |Added
Resolution|--- |WORKSFORME
CC
https://bugs.kde.org/show_bug.cgi?id=463305
Andre Heinecke changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=463305
--- Comment #2 from Andre Heinecke ---
Created attachment 154876
--> https://bugs.kde.org/attachment.cgi?id=154876=edit
Capture of test system
Capture of Notepad / Clipboard operations.
--
You are receiving this mail because:
You are on the
https://bugs.kde.org/show_bug.cgi?id=463266
Andre Heinecke changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=441957
--- Comment #2 from Andre Heinecke ---
Thanks for the report. We were able to reproduce it and have fixed this.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.kde.org/show_bug.cgi?id=430161
Andre Heinecke changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=426436
Andre Heinecke changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=426436
Andre Heinecke changed:
What|Removed |Added
Attachment #131572|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=425889
Andre Heinecke changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=425039
--- Comment #1 from Andre Heinecke ---
You can try to remove ~/.config/kleopatrarc to reset kleopatra's window states.
For more advice I would need to know the version / operating system you use.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=421216
Andre Heinecke changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=363309
--- Comment #3 from Andre Heinecke ---
The proper fix here would be to use the trust levels that we use in GpgOL
throughout Kleopatra and KMail (libkleo)
https://wiki.gnupg.org/AutomatedEncryption#Trust_Levels
There is already some work on this done
https://bugs.kde.org/show_bug.cgi?id=417389
Andre Heinecke changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=415168
--- Comment #5 from Andre Heinecke ---
*** Bug 417389 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.kde.org/show_bug.cgi?id=415168
--- Comment #4 from Andre Heinecke ---
Created attachment 125893
--> https://bugs.kde.org/attachment.cgi?id=125893=edit
De- Inline virtual dtor of Keylistmodelinterface and export it
The underlying reason is the "Invalid Model" from the
https://bugs.kde.org/show_bug.cgi?id=417389
--- Comment #7 from Andre Heinecke ---
Thanks, someone in my office is also using FreeBSD and I was able to see the
same behavior on his system so I can debug / analyze it here.
--
You are receiving this mail because:
You are on the CC list
https://bugs.kde.org/show_bug.cgi?id=417389
Andre Heinecke changed:
What|Removed |Added
Status|REOPENED|CONFIRMED
URL
https://bugs.kde.org/show_bug.cgi?id=417389
Andre Heinecke changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=412569
--- Comment #6 from Andre Heinecke ---
You can get the windows pinentry on Linux by installing pinentry-qt or setting
it to default through something like "update-alternatives" on debian (not sure
how it is called on fedora).
As for the tr
https://bugs.kde.org/show_bug.cgi?id=412569
--- Comment #3 from Andre Heinecke ---
Ok this is definetly bad behavior of pinentry-gnome.
But I don't know pinentry-gnome enough to can say if it is with the GCR System
Prompter or if it is with the version of pinentry-gnome used. I tested
https://bugs.kde.org/show_bug.cgi?id=412569
--- Comment #1 from Andre Heinecke ---
Hi,
thank you for your detailed report. I do not understand the problem correctly.
By password confirmation you mean the "Repeat" field.
If you omit the repeat field it still lets you advan
https://bugs.kde.org/show_bug.cgi?id=411849
--- Comment #6 from Andre Heinecke ---
Your bug report was great. Even a bit too detailed like "not tested on MacOS"
and you pointed out a shameful piece of "quick hack". And you had the luck that
I was working on Kleo today
https://bugs.kde.org/show_bug.cgi?id=411849
--- Comment #4 from Andre Heinecke ---
This was a classical case of a todo that lived too long.
The idea behind this was "I have to talk to Werner and Gniibe how we can detect
the capabilities" and in the meantime I do this.
Then we ta
https://bugs.kde.org/show_bug.cgi?id=411849
Andre Heinecke changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=411849
--- Comment #2 from Andre Heinecke ---
Yeah on it. Just a sec.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.kde.org/show_bug.cgi?id=411469
Andre Heinecke changed:
What|Removed |Added
Resolution|--- |DOWNSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=407594
--- Comment #2 from Andre Heinecke ---
Oh $@"ยง! my bad!
This was noticed and fixed already but I overlooked that the commit that
introduced this problem was part of the release branch and the commit that
fixed the problem was not.
Thank you very
https://bugs.kde.org/show_bug.cgi?id=407594
Andre Heinecke changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=406590
Andre Heinecke changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=404795
Andre Heinecke changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=404795
Andre Heinecke changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=403715
Andre Heinecke changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=403715
--- Comment #1 from Andre Heinecke ---
For such requirements wouldn't it be best to have a two person setup using a
hardware token (e.g. an OpenPGP Smartcard) where one person has access to the
token and the second person knows the PIN?
Anyhow just
https://bugs.kde.org/show_bug.cgi?id=401933
Andre Heinecke changed:
What|Removed |Added
Version Fixed In||18.12.0
--- Comment #15 from Andre Heinecke
https://bugs.kde.org/show_bug.cgi?id=401933
Andre Heinecke changed:
What|Removed |Added
Latest Commit||95d1078933d7c3cd6dee5477211
https://bugs.kde.org/show_bug.cgi?id=401933
--- Comment #12 from Andre Heinecke ---
*eats his words*
git tag --contains db3fd6ea8c6619da75b9903a90fffc0f9330cf12
v18.11.80
v18.11.90
git tag --contains 98cf4b67ac005832a0ada734ba805e10e51a0319
^ none
I think v18.11.90 might have been wrongly
https://bugs.kde.org/show_bug.cgi?id=401933
--- Comment #11 from Andre Heinecke ---
Awesome, thanks for looking into this !
So you have a version that contained my Friday bug (sorry for that)
db3fd6ea8c6619da75b9903a90fffc0f9330cf12
But not my Monday fix
https://bugs.kde.org/show_bug.cgi?id=401933
Andre Heinecke changed:
What|Removed |Added
Severity|major |normal
--- Comment #7 from Andre Heinecke
https://bugs.kde.org/show_bug.cgi?id=401933
Andre Heinecke changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=401933
Andre Heinecke changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=398839
Andre Heinecke changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=360364
--- Comment #6 from Andre Heinecke ---
I hope that it will be fixed with Gpg4win-3.1.3
At least for my windows test system it works now. But the encoding is so messy
that it might still be broken in other situations.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=360364
Andre Heinecke changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=395601
Andre Heinecke changed:
What|Removed |Added
Ever confirmed|0 |1
OS|Linux
https://bugs.kde.org/show_bug.cgi?id=394400
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=390949
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
URL||https://dev.gnu
https://bugs.kde.org/show_bug.cgi?id=393450
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Resolution|--- |UP
https://bugs.kde.org/show_bug.cgi?id=385687
--- Comment #8 from Andre Heinecke <aheine...@intevation.de> ---
Hi,
thank you very much for that input.
(In reply to ekaratsiolis from comment #7)
> CERT_PATH_ALGO_STRENGTH_01 (and ..._02).
>
> Lots of libraries still accept
https://bugs.kde.org/show_bug.cgi?id=385687
--- Comment #5 from Andre Heinecke <aheine...@intevation.de> ---
Thanks for the link to the testing tool.
Can you clarify which Report you mean? I have not yet received the report you
had attached to the other bug. Could you please send it
https://bugs.kde.org/show_bug.cgi?id=385687
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|CONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=393675
--- Comment #1 from Andre Heinecke <aheine...@intevation.de> ---
Created attachment 112321
--> https://bugs.kde.org/attachment.cgi?id=112321=edit
The test message
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=393675
Bug ID: 393675
Summary: KMail might not show that an invalid signature exists
Product: kmail2
Version: 5.2.3
Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385687
--- Comment #2 from Andre Heinecke <aheine...@intevation.de> ---
I don't think that any of the issues raised here are a big (or any) security
concern. Because mails are only ever valid if the corresponding root
certificate is trusted.
If you onl
https://bugs.kde.org/show_bug.cgi?id=393450
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
CC||
https://bugs.kde.org/show_bug.cgi?id=385687
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
URL||https://dev.gnu
https://bugs.kde.org/show_bug.cgi?id=393447
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=393447
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=393095
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Resolution|--- |WAITINGF
https://bugs.kde.org/show_bug.cgi?id=392643
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Resolution|--- |DUP
https://bugs.kde.org/show_bug.cgi?id=391222
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
CC||llev...@ngpv
https://bugs.kde.org/show_bug.cgi?id=389919
--- Comment #8 from Andre Heinecke <aheine...@intevation.de> ---
Thanks for testing!
Good to hear.
But with the current Beta there might still be issues. E.g. Configuration of
the GnuPG-System won't work. These problems are already solved but
https://bugs.kde.org/show_bug.cgi?id=391593
--- Comment #4 from Andre Heinecke <aheine...@intevation.de> ---
There was a logic error that the buttons were not reset on restart after
importing. The Ok button should have been exchanged for a close button and then
readded as OK butto
https://bugs.kde.org/show_bug.cgi?id=391593
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=391593
--- Comment #2 from Andre Heinecke <aheine...@intevation.de> ---
Thanks!
Several people reported to my already that they "Sometimes" saw multiple Ok
buttons but could never tell me how to reproduce this.
I'll look into it.
--
Y
https://bugs.kde.org/show_bug.cgi?id=386518
--- Comment #2 from Andre Heinecke <aheine...@intevation.de> ---
We had a crash in Kleopatra on Verify that has been fixed:
https://dev.gnupg.org/T3761 (Or here BUG 389792 )
We also fixed instabilities of Kleopatra when used with a APPDATA dir
https://bugs.kde.org/show_bug.cgi?id=391222
--- Comment #3 from Andre Heinecke <aheine...@intevation.de> ---
A beta of the next version, which contains the fix is available now
https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=389792
--- Comment #2 from Andre Heinecke <aheine...@intevation.de> ---
A beta with the fix is available now.
https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.kde.org/show_bug.cgi?id=391222
--- Comment #2 from Andre Heinecke <aheine...@intevation.de> ---
Thanks for your report. Indeed this was a recently introduced bug.
Will be fixed in the next Gpg4win release.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.kde.org/show_bug.cgi?id=391222
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=389919
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
URL||https://dev.gnu
https://bugs.kde.org/show_bug.cgi?id=389919
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=390117
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Resolution|--- |WAITINGF
https://bugs.kde.org/show_bug.cgi?id=389792
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Resolution|--- |UP
https://bugs.kde.org/show_bug.cgi?id=380490
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
CC||fortinog
https://bugs.kde.org/show_bug.cgi?id=389689
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=376563
--- Comment #7 from Andre Heinecke <aheine...@intevation.de> ---
No it's a bug in GpgSM / Kleopatra. This special certificate is not handled by
GpgSM correctly and Kleopatra can't cope with it. I'm not sure if this is only
an upstream bug w
https://bugs.kde.org/show_bug.cgi?id=389291
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
CC||nasan...@gma
https://bugs.kde.org/show_bug.cgi?id=388047
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|NEEDSINFO |RE
https://bugs.kde.org/show_bug.cgi?id=389642
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|UNCONFIRMED |NEE
https://bugs.kde.org/show_bug.cgi?id=389291
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|CONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=389291
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=389291
--- Comment #2 from Andre Heinecke <aheine...@intevation.de> ---
Hi,
thanks for your report. Which Version in Neon is that exactly? Depending on the
Neon flavor that can differ.
(dpkg -s kleopatra)
There was one crash that I know of that has been
https://bugs.kde.org/show_bug.cgi?id=389008
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=388478
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Resolution|--- |WAITINGF
https://bugs.kde.org/show_bug.cgi?id=381910
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=388022
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Severity|critical|normal
--- C
https://bugs.kde.org/show_bug.cgi?id=387978
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Resolution|--- |WAITINGF
https://bugs.kde.org/show_bug.cgi?id=355086
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=387484
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Severity|critical|normal
-
https://bugs.kde.org/show_bug.cgi?id=387484
--- Comment #1 from Andre Heinecke <aheine...@intevation.de> ---
Can you decrypt this on the command line?
(Run CMD and then do "gpg --decrypt " basically this is
what kleopatra does under the hood and kleopatra gets "no secre
https://bugs.kde.org/show_bug.cgi?id=386506
--- Comment #6 from Andre Heinecke <aheine...@intevation.de> ---
I could reproduce it. The internal keycache was not always updated correctly
and the internal reference to the newly created key did not exist.
Will be fixed in the next Gpg4win r
https://bugs.kde.org/show_bug.cgi?id=386506
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=386908
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=386506
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
CC||alejandro.es
https://bugs.kde.org/show_bug.cgi?id=386506
Andre Heinecke <aheine...@intevation.de> changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
1 - 100 of 712 matches
Mail list logo
