[kdepim] [Bug 279749] Kontact crashed when trying to open gpg encripted email

2015-02-14 Thread Tobias N .
https://bugs.kde.org/show_bug.cgi?id=279749 --- Comment #44 from Tobias N. --- Hi, at least with KDE 4.13 the problem seems to be fixed. I cannot reproduce it, and the general behaviour regarding decryption has obviously been changed. So I assume, that there were major code changes and thus it

[kdepim] [Bug 279749] Kontact crashed when trying to open gpg encripted email

2014-01-31 Thread Tobias N .
https://bugs.kde.org/show_bug.cgi?id=279749 --- Comment #35 from Tobias N. --- Created attachment 84924 --> https://bugs.kde.org/attachment.cgi?id=84924&action=edit Patch to solve the bug entirely The bug 96498 was very related to bug 279749 and has been fixed already. However, it did

[kdepim] [Bug 279749] Kontact crashed when trying to open gpg encripted email

2014-01-31 Thread Tobias N .
https://bugs.kde.org/show_bug.cgi?id=279749 Tobias N. changed: What|Removed |Added Attachment #84924|0 |1 is obsolete

[kdepim] [Bug 279749] Kontact crashed when trying to open gpg encripted email

2014-02-04 Thread Tobias N .
https://bugs.kde.org/show_bug.cgi?id=279749 --- Comment #40 from Tobias N. --- Ok, may be the problem was already solved in another way, since I am using version 4.11.3 (Kubuntu). Comparing the sources of viewer_p.cpp with the latest version in git, however, does not show a bugfix for this

[kdepim] [Bug 279749] Kontact crashed when trying to open gpg encripted email

2014-02-08 Thread Tobias N .
https://bugs.kde.org/show_bug.cgi?id=279749 --- Comment #41 from Tobias N. --- I've now tried version 4.12.2 (ubuntu) and get the problem, that it is not possible at all to decrypt an email, that requires a passphrase for decryption. Thus the dialog does not appear and consequently, the pr

[kdepim] [Bug 279749] Kontact crashed when trying to open gpg encripted email

2014-02-14 Thread Tobias N .
https://bugs.kde.org/show_bug.cgi?id=279749 --- Comment #42 from Tobias N. --- I have tried version 4.11.5 and it is still reproducable. Can anyone check this and/or commit the patch in the coming version 4.11.6? -- You are receiving this mail because: You are the assignee for the bug