[Akonadi] [Bug 341860] akonadi_imap_resource (4.14) segfault
https://bugs.kde.org/show_bug.cgi?id=341860 Christoph Feck changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 341860] New: akonadi_imap_resource (4.14) segfault
https://bugs.kde.org/show_bug.cgi?id=341860 Bug ID: 341860 Summary: akonadi_imap_resource (4.14) segfault Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: gtwilli...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Left Kmail open for several hours and, upon returning, crash handler was awaiting my response. Reproducible: Sometimes -- Backtrace: Application: Google Mail of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2886c03880 (LWP 4438))] Thread 3 (Thread 0x7f28699ef700 (LWP 4440)): #0 0x7f28807a3f30 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #1 0x7f28807a638b in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f28807a6d4b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f28807a6f3c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f2885fab6be in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQtCore.so.4 #5 0x7f2885f7af91 in QEventLoop::processEvents(QFlags) () from /lib64/libQtCore.so.4 #6 0x7f2885f7b2f5 in QEventLoop::exec(QFlags) () from /lib64/libQtCore.so.4 #7 0x7f2885e70b69 in QThread::exec() () from /lib64/libQtCore.so.4 #8 0x7f2885e733cf in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #9 0x7f2885be252a in start_thread () from /lib64/libpthread.so.0 #10 0x7f2881a9877d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f2863fff700 (LWP 4442)): #0 0x7f28807a66a9 in g_main_context_query () from /lib64/libglib-2.0.so.0 #1 0x7f28807a6d9a in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f28807a6f3c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f2885fab6be in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQtCore.so.4 #4 0x7f2885f7af91 in QEventLoop::processEvents(QFlags) () from /lib64/libQtCore.so.4 #5 0x7f2885f7b2f5 in QEventLoop::exec(QFlags) () from /lib64/libQtCore.so.4 #6 0x7f2885e70b69 in QThread::exec() () from /lib64/libQtCore.so.4 #7 0x7f2885e733cf in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #8 0x7f2885be252a in start_thread () from /lib64/libpthread.so.0 #9 0x7f2881a9877d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f2886c03880 (LWP 4438)): [KCrash Handler] #5 0x7f288496f84d in KIMAP::SearchJob::handleResponse(KIMAP::Message const&) () from /lib64/libkimap.so.4 #6 0x7f288496090b in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () from /lib64/libkimap.so.4 #7 0x7f2885f955f1 in QObject::event(QEvent*) () from /lib64/libQtCore.so.4 #8 0x7f28850b5f6c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQtGui.so.4 #9 0x7f28850bc9b8 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQtGui.so.4 #10 0x7f2882f179ea in KApplication::notify(QObject*, QEvent*) () from /lib64/libkdeui.so.5 #11 0x7f2885f7c43d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQtCore.so.4 #12 0x7f2885f7f701 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQtCore.so.4 #13 0x7f2885fab52e in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQtCore.so.4 #14 0x7f28807a6aeb in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #15 0x7f28807a6e88 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #16 0x7f28807a6f3c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #17 0x7f2885fab69e in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQtCore.so.4 #18 0x7f2885159346 in QGuiEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQtGui.so.4 #19 0x7f2885f7af91 in QEventLoop::processEvents(QFlags) () from /lib64/libQtCore.so.4 #20 0x7f2885f7b2f5 in QEventLoop::exec(QFlags) () from /lib64/libQtCore.so.4 #21 0x7f2885f809c7 in QCoreApplication::exec() () from /lib64/libQtCore.so.4 #22 0x7f28866f4bec in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /lib64/libakonadi-kde.so.4 #23 0x00418c3e in int Akonadi::ResourceBase::init(int, char**) () #24 0x7f28819b7fe0 in __libc_start_main () from /lib64/libc.so.6 #25 0x00418ae4 in _start () -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[knotes] [Bug 341761] Wish: More display- and sorting options in Knotes
https://bugs.kde.org/show_bug.cgi?id=341761 --- Comment #6 from Laurent Montel --- (In reply to Lars from comment #5) > Sort in kontact or knotes! ? knotes shows note on destkop Kontact show note in apps Please specify apps and not a "or" :) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[knotes] [Bug 341761] Wish: More display- and sorting options in Knotes
https://bugs.kde.org/show_bug.cgi?id=341761 --- Comment #5 from Lars --- Sort in kontact or knotes! -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[knotes] [Bug 341761] Wish: More display- and sorting options in Knotes
https://bugs.kde.org/show_bug.cgi?id=341761 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 256137 *** -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[knotes] [Bug 256137] add option for sort order in notes list
https://bugs.kde.org/show_bug.cgi?id=256137 Christoph Feck changed: What|Removed |Added CC||lars.koes...@web.de --- Comment #1 from Christoph Feck --- *** Bug 341761 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 340931] Read status of emails not updated when changed outside KMail, but only for GMail accounts via IMAP
https://bugs.kde.org/show_bug.cgi?id=340931 Erik Quaeghebeur changed: What|Removed |Added CC||kdebugs@equaeghe.nospammail ||.net --- Comment #3 from Erik Quaeghebeur --- This just now started happening to me for a Cyrus IMAP server after updating to KDE SC 4.14.3 from 4.12.5. I assume there must be some connection to KMail, because akonadi-server had been updated already to 1.13.0 some weeks before. My investigation turned up the following: * When opening the mailbox with kmail, they appeared as unread. * When opening with akonadi-console, the messages in the mailbox had no flags (or keywords) set at all. * When opening the mailbox using Thunderbird, everything worked fine. * When opening with Trojita, its IMAP implementation complained that there were non-parseable flags (or did it say keywords? that would be more correct), namely, "[EXPUNGED]", and "[ARCHIVED]". It is not clear to me whether the '[' and ']' characters are disallowed by the IMAP RFCs (they seem valid in modified UTF-7, I think.) I therefore did the following: I used Firefox to remove those keywords, after which all the other clients behaved as they should: picking up all flags and keywords. (KMail does not show the keywords, of course, see Bug 283020.) My conclusion is therefore that the IMAP resource chokes on such keywords. If these are not invalid according to the RFC, the resource's flag/keyword parser should be modified to be able to deal with them. If these are invalid, upstream bugs should be filed to the generators of those keywords and perhaps workaround code for know invalid keywords could be included. To verify my conclusion, another affected user should install Trojita and sees what it lists. (They can of course also use akonadi-console or Thunderbird for further tests.) If verified somebody with sufficient IMAP RFC erudition should shine a light on whether such keywords are valid or not. Then a course of action can be taken. (Modifying the parser should not be that big of a modification, no?) -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 333150] Deleting attachment removes the entire message
https://bugs.kde.org/show_bug.cgi?id=333150 michael.zug...@college-de-france.fr changed: What|Removed |Added Version|4.12.3 |4.14.2 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 341852] New: Kontact crash after I tryed to start a new instance
https://bugs.kde.org/show_bug.cgi?id=341852 Bug ID: 341852 Summary: Kontact crash after I tryed to start a new instance Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mar...@janus.me.uk Application: kontact (4.14.3) KDE Platform Version: 4.14.3 Qt Version: 4.8.6 Operating System: Linux 3.17.4-200.fc20.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: Kontact crash after I tryed to start a new instance of Kontact -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8b65fc4940 (LWP 23316))] Thread 4 (Thread 0x7f8b1a2f4700 (LWP 23317)): #0 0x0038a8e0bca0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x003e38ab9a8d in JSC::BlockAllocator::blockFreeingThreadMain() () from /lib64/libQtWebKit.so.4 #2 0x003e38dabe36 in WTF::wtfThreadEntryPoint(void*) () from /lib64/libQtWebKit.so.4 #3 0x0038a8e07ee5 in start_thread () from /lib64/libpthread.so.0 #4 0x0038a92f4b8d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f8b10b44700 (LWP 23327)): #0 0x0038a92ea71d in poll () from /lib64/libc.so.6 #1 0x0038ab6495b4 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x0038ab6496dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x0038b0bb543e in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQtCore.so.4 #4 0x0038b0b8538f in QEventLoop::processEvents(QFlags) () from /lib64/libQtCore.so.4 #5 0x0038b0b856dd in QEventLoop::exec(QFlags) () from /lib64/libQtCore.so.4 #6 0x0038b0a79e5f in QThread::exec() () from /lib64/libQtCore.so.4 #7 0x0038b0a7c69f in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #8 0x0038a8e07ee5 in start_thread () from /lib64/libpthread.so.0 #9 0x0038a92f4b8d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f8b0aa0b700 (LWP 23366)): #0 0x0038b0bb6cd5 in QTimerInfoList::timerWait(timeval&) () from /lib64/libQtCore.so.4 #1 0x0038b0bb52cc in timerSourcePrepareHelper(GTimerSource*, int*) () from /lib64/libQtCore.so.4 #2 0x0038b0bb5395 in timerSourcePrepare(_GSource*, int*) () from /lib64/libQtCore.so.4 #3 0x0038ab648bed in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #4 0x0038ab6494bb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #5 0x0038ab6496dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #6 0x0038b0bb543e in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQtCore.so.4 #7 0x0038b0b8538f in QEventLoop::processEvents(QFlags) () from /lib64/libQtCore.so.4 #8 0x0038b0b856dd in QEventLoop::exec(QFlags) () from /lib64/libQtCore.so.4 #9 0x0038b0a79e5f in QThread::exec() () from /lib64/libQtCore.so.4 #10 0x0038b0b65de3 in QInotifyFileSystemWatcherEngine::run() () from /lib64/libQtCore.so.4 #11 0x0038b0a7c69f in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #12 0x0038a8e07ee5 in start_thread () from /lib64/libpthread.so.0 #13 0x0038a92f4b8d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f8b65fc4940 (LWP 23316)): [KCrash Handler] #5 0x0038a9235877 in raise () from /lib64/libc.so.6 #6 0x0038a9236f68 in abort () from /lib64/libc.so.6 #7 0x0038b0a71ce4 in qt_message_output(QtMsgType, char const*) () from /lib64/libQtCore.so.4 #8 0x0038b0a71e89 in qt_message(QtMsgType, char const*, __va_list_tag*) () from /lib64/libQtCore.so.4 #9 0x0038b0a72791 in qFatal(char const*, ...) () from /lib64/libQtCore.so.4 #10 0x003e44c69067 in MailCommon::Kernel::self() () from /lib64/libmailcommon.so.4 #11 0x003e44cb0e33 in MailCommon::FolderCollection::writeConfig() const () from /lib64/libmailcommon.so.4 #12 0x003e44cb1652 in MailCommon::FolderCollection::~FolderCollection() () from /lib64/libmailcommon.so.4 #13 0x003e44cb16c9 in MailCommon::FolderCollection::~FolderCollection() () from /lib64/libmailcommon.so.4 #14 0x003e44cafde4 in QMap >::freeData(QMapData*) [clone .isra.20] () from /lib64/libmailcommon.so.4 #15 0x0038a92390e9 in __run_exit_handlers () from /lib64/libc.so.6 #16 0x0038a9239135 in exit () from /lib64/libc.so.6 #17 0x00371a549ba6 in KCmdLineArgs::isSet(QByteArray const&) const () from /lib64/libkdecore.so.5 #18 0x00403f57 in KontactApp::newInstance() () #19 0x003e30451aed in KUniqueApplicationAdaptor::newInstance(QByteArray const&, QByteArray const&) () from /lib64/libkdeui.so.5 #20 0x003e30451bad in KUniqueApplicationAdaptor::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.18] () from /lib64/libkdeui.s
[kmail2] [Bug 333150] Deleting attachment removes the entire message
https://bugs.kde.org/show_bug.cgi?id=333150 --- Comment #4 from Erik Quaeghebeur --- I tested, and this is still present in 4.14.3. Perhaps the original reporter or a developer can update the version in the bug description? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 329092] Akregator
https://bugs.kde.org/show_bug.cgi?id=329092 Christoph Feck changed: What|Removed |Added CC||keren_...@live.com --- Comment #4 from Christoph Feck --- *** Bug 340988 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 341116] cannot edit IMAP flags; Save button stays grayed-out
https://bugs.kde.org/show_bug.cgi?id=341116 Erik Quaeghebeur changed: What|Removed |Added Version|4.12|4.13 --- Comment #2 from Erik Quaeghebeur --- Still present in 4.14.3; updating version to latest (is 4.13!?). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[knotes] [Bug 341761] Wish: More display- and sorting options in Knotes
https://bugs.kde.org/show_bug.cgi?id=341761 --- Comment #3 from Laurent Montel --- sort on desktop ? or sort in kontact ? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 341426] Change default to Yes for "Keep replies in this folder"
https://bugs.kde.org/show_bug.cgi?id=341426 --- Comment #4 from Laurent Montel --- (In reply to Peter Humphrey from comment #2) > Yet you seem to be quite happy to release a version (4.14.3) that removes > all my carefully set folder prefer-HTML choices without permission. I was > only asking for a change in a default setting, which would not have affected > anyone's existing setup. > This is one more illustration of the amateurish approach to KDE development > and release. ?? you bug is about " Change default to Yes for "Keep replies in this folder" and now you speak about "prefer-HTML choices" ?? Please don't mix bug report. "This is one more illustration of the amateurish approach to KDE development and release." If you think that you are better send patch and co no ? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail] [Bug 116817] Cannot create (disconnected) IMAP folder
https://bugs.kde.org/show_bug.cgi?id=116817 Sandro Knauß changed: What|Removed |Added CC||kna...@kolabsys.com Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #16 from Sandro Knauß --- This bug reports only mentioned version with kmail versions, that do not use akonadi. So is this still an issue for kmail > 4.10? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 341426] Change default to Yes for "Keep replies in this folder"
https://bugs.kde.org/show_bug.cgi?id=341426 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk --- Comment #3 from Jonathan Marten --- @submitter: I think it's been made clear that changing the default will silently affect KMail's behaviour for many other users, and as such will not be implemented. It's an unfamiliar option that is not normally provided in other mail clients (although I use it in certain KMail folders and do find it useful) so Laurent's POV is understandable. One option that may better received, though, would be to suggest that this and possibly other folder options too are made inherited; that is, for example, setting this option on "Local Folders" would apply it not only there but also on any subfolders to any depth, unless explicitly overridden. This would allow you in your case to set this option for all folders in only one operation, while still retaining the current default and any current users' settings. This is an option that I've cosidered investigting myself, so if you feel that this would be a workable option for you then please feel free to submit a wishlist item or discuss it on KDE Brainstorm. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 341839] New: No hint why i cannot select a s/mime certificate for signing or encryption
https://bugs.kde.org/show_bug.cgi?id=341839 Bug ID: 341839 Summary: No hint why i cannot select a s/mime certificate for signing or encryption Product: kmail2 Version: 4.14.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: e...@erlenweg.de I am trying to add a s/mime certificate to one of my identities. I have imported it using kleopatra but something went wrong (which I am still trying to narrow down). But meanwhile I see another problem connected to this: The dialog, where I can select a s/mime certificate for signing or encryption, shows the certificate I have imported before. But once I select it, the icon in the 'Key ID' column gets a red cross indicating some kind of problem. But the dialog does not give any kind of hint what is actually wrong. It would be nice to have some kind of error message (maybe as a tooltip on the red cross of the icon, maybe displayed somewhere in the dialog). Reproducible: Always Steps to Reproduce: 1. Edit identity 2. Cryptography: change s/mime signing certificate or change s/mime encryption certificate 3. Select a bad certificate is the selection dialog Actual Results: Red cross in the 'Key ID' column, no error message, 'Ok' button is disabled. Expected Results: Give some kind of error message (displayed as tooltip or within the dialog window) which helps the user to track down the problem. I am in two minds whether this a bug or a feature request. In its core, I suggest a kind of a new feature (some kind of error message in case of problems with one of the certificates). But on the other hand, the current behavior can be quite frustrating for the average user, because there is clearly something going wrong but there is no helpful information displayed. So there is clearly something missing and therefore I have select 'minor bug' for this. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 341426] Change default to Yes for "Keep replies in this folder"
https://bugs.kde.org/show_bug.cgi?id=341426 Peter Humphrey changed: What|Removed |Added Severity|wishlist|normal Resolution|WONTFIX |REMIND Status|RESOLVED|VERIFIED --- Comment #2 from Peter Humphrey --- Yet you seem to be quite happy to release a version (4.14.3) that removes all my carefully set folder prefer-HTML choices without permission. I was only asking for a change in a default setting, which would not have affected anyone's existing setup. This is one more illustration of the amateurish approach to KDE development and release. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 337806] Unable to click on links in "invitations" encrypted with GnuPG
https://bugs.kde.org/show_bug.cgi?id=337806 --- Comment #2 from Franz Schrober --- Anymore was referring to "unencrypted mails with vcard invitations". And I think it worked with the non-akonadi kmail - but I am not sure about this. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 326063] [Security?] KMail invoked from KToolInvocation with an encrypted text will decrypt the text
https://bugs.kde.org/show_bug.cgi?id=326063 --- Comment #2 from Rolf Eike Beer --- I currently can't test this because of bug 332368. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
