[kmail2] [Bug 368350] folder full text search doesn't work : folder status always 'still not indexed'
https://bugs.kde.org/show_bug.cgi?id=368350 frank-fisc...@shadow-soft.de changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 366112] [regression] Akonadi does not load remote calendar source
https://bugs.kde.org/show_bug.cgi?id=366112 Frank Steinmetzgerchanged: What|Removed |Added CC||war...@gmx.de --- Comment #1 from Frank Steinmetzger --- I discovered the very same problem on my PC yesterday by chance, because I was making changes to the ICS generator on the remote end and saw no changes in my calendar entries. I did the upgrade from KDE 4 to 5 in mid-July, and the remote read-only ICS calendar got stuck in its state from that time. Just like the OP, I downloaded the file and opened it with KOrganizer and it showed everything as it should. I deleted and re-added the source, and now there are no items at all. Running Gentoo with normal packages. Plasma 5.7.2 nowadays. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 351097] akonadi 15.07.80 crashed when the machine was idle
https://bugs.kde.org/show_bug.cgi?id=351097 Denis Kurzchanged: What|Removed |Added CC||alain.quincerot_...@m4am.ne ||t --- Comment #11 from Denis Kurz --- *** Bug 357732 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 367779] kmail always crashes when closing
https://bugs.kde.org/show_bug.cgi?id=367779 --- Comment #7 from tick...@tsiboboka.de --- (In reply to Denis Kurz from comment #6) [..] > Would you please check your version number? Oh sorry! I just saw the update manager fetching 16.xx packages but didn't checked in detail. You're totally right, I still have to wait until some time. There's nothing newer than 16.08.0 at http://download.opensuse.org/repositories/KDE:/Applications/openSUSE_Leap_42.1/ Sorry for causing useless noise. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 351097] akonadi 15.07.80 crashed when the machine was idle
https://bugs.kde.org/show_bug.cgi?id=351097 Denis Kurzchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #14 from Denis Kurz --- All reports of duplicates of this bug stopped shortly after Weng's proposed fix in comment 3. This fix was included in version 15.12.0 (and even 15.11.80), and the duplicates of this bug reports filed after the release of 15.12.0 were still filed against 15.08.* (when the version was provided). It seems quite obvious that Weng's fix actually solved the problem, so I close here. I gladly reopen if someone stil sees this in version 15.12.0 or later. -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 359090] Akonadi crashes when selecting a specific e-mail
https://bugs.kde.org/show_bug.cgi?id=359090 Denis Kurzchanged: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 351097 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 351097] akonadi 15.07.80 crashed when the machine was idle
https://bugs.kde.org/show_bug.cgi?id=351097 Denis Kurzchanged: What|Removed |Added CC||samuele.kap...@cern.ch --- Comment #13 from Denis Kurz --- *** Bug 359304 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 359304] Akonadi crashed while not using any PIM application
https://bugs.kde.org/show_bug.cgi?id=359304 Denis Kurzchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 351097 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 351097] akonadi 15.07.80 crashed when the machine was idle
https://bugs.kde.org/show_bug.cgi?id=351097 Denis Kurzchanged: What|Removed |Added CC||h6zb8-kdebugs20120801@yahoo ||.de --- Comment #12 from Denis Kurz --- *** Bug 359090 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[kontact] [Bug 357364] kontact crashes after updating from kde4
https://bugs.kde.org/show_bug.cgi?id=357364 Denis Kurzchanged: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 351097 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 351097] akonadi 15.07.80 crashed when the machine was idle
https://bugs.kde.org/show_bug.cgi?id=351097 Denis Kurzchanged: What|Removed |Added CC||mar...@pluskal.org --- Comment #10 from Denis Kurz --- *** Bug 357364 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 352684] Kontact crashed on startup
https://bugs.kde.org/show_bug.cgi?id=352684 Denis Kurzchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 351097 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 351097] akonadi 15.07.80 crashed when the machine was idle
https://bugs.kde.org/show_bug.cgi?id=351097 Denis Kurzchanged: What|Removed |Added CC||denni.gran...@gmail.com --- Comment #7 from Denis Kurz --- *** Bug 354224 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 351097] akonadi 15.07.80 crashed when the machine was idle
https://bugs.kde.org/show_bug.cgi?id=351097 Denis Kurzchanged: What|Removed |Added CC||v...@pelcak.org --- Comment #8 from Denis Kurz --- *** Bug 352684 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 351097] akonadi 15.07.80 crashed when the machine was idle
https://bugs.kde.org/show_bug.cgi?id=351097 --- Comment #9 from Denis Kurz--- *** Bug 355473 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 354224] Akonadi crashes without notice
https://bugs.kde.org/show_bug.cgi?id=354224 Denis Kurzchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 351097 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 355473] Maildir resource crashes
https://bugs.kde.org/show_bug.cgi?id=355473 Denis Kurzchanged: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 351097 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 351097] akonadi 15.07.80 crashed when the machine was idle
https://bugs.kde.org/show_bug.cgi?id=351097 Denis Kurzchanged: What|Removed |Added CC||jan_br...@gmx.net --- Comment #5 from Denis Kurz --- *** Bug 351515 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 355239] Maildir resource crashes
https://bugs.kde.org/show_bug.cgi?id=355239 Denis Kurzchanged: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 351097 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 351515] Akonadi-Resource 15.08 (&15.07.90) crash in background (probably while checking mails)
https://bugs.kde.org/show_bug.cgi?id=351515 Denis Kurzchanged: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 351097 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 351097] akonadi 15.07.80 crashed when the machine was idle
https://bugs.kde.org/show_bug.cgi?id=351097 Denis Kurzchanged: What|Removed |Added CC||aux...@gmail.com --- Comment #6 from Denis Kurz --- *** Bug 355239 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[kontact] [Bug 289107] Kontact crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=289107 --- Comment #10 from Tom Chiverton--- And neither is https://launchpad.net/%7Ekubuntu-ppa/+archive/ubuntu/backports/+index?batch=75=525=525 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 289107] Kontact crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=289107 --- Comment #9 from Tom Chiverton--- Where can I get an updated version to test with then ? https://launchpad.net/%7Ekubuntu-ppa/+archive/ubuntu/ppa/+index?batch=75=150=150 doesn't appear to be it -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367779] kmail always crashes when closing
https://bugs.kde.org/show_bug.cgi?id=367779 --- Comment #6 from Denis Kurz--- Oh noes! But did you see that I mentioned this is fixed in 16.08.1? This version will not be released before Sep 08, and might take (quite) some additional additional time to be included in your distrobution. I hope you did not build the current git master from sources yourself, as that would really mean that it is not fixed in 16.08.1. Would you please check your version number? -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 364994] Kmail crash when deleting message in thread view
https://bugs.kde.org/show_bug.cgi?id=364994 Denis Kurzchanged: What|Removed |Added CC||christian.saem...@gmx.de --- Comment #6 from Denis Kurz --- *** Bug 368150 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368231] kmail crashes while downloading from imap server
https://bugs.kde.org/show_bug.cgi?id=368231 Denis Kurzchanged: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 364994 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368323] Applying a filter crashed Kmail and Kontact
https://bugs.kde.org/show_bug.cgi?id=368323 Denis Kurzchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 364994 *** -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 364994] Kmail crash when deleting message in thread view
https://bugs.kde.org/show_bug.cgi?id=364994 --- Comment #8 from Denis Kurz--- *** Bug 368323 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 364994] Kmail crash when deleting message in thread view
https://bugs.kde.org/show_bug.cgi?id=364994 Denis Kurzchanged: What|Removed |Added CC||muzhm...@centrum.sk --- Comment #7 from Denis Kurz --- *** Bug 368231 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368150] Kontact crashes when email is moved to a folder
https://bugs.kde.org/show_bug.cgi?id=368150 Denis Kurzchanged: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 364994 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367779] kmail always crashes when closing
https://bugs.kde.org/show_bug.cgi?id=367779 --- Comment #5 from tick...@tsiboboka.de --- I'm afraid it still happens, not each time but often. Thanks for your effort! Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2e7482f800 (LWP 7447))] Thread 20 (Thread 0x7f2dc97fa700 (LWP 7484)): #0 0x7f2e718bbbfd in poll () at /lib64/libc.so.6 #1 0x7f2e65cace64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2e65cacf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2e723d7f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2e723878cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2e721ce06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2e721d2899 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f2e6792f0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2e718c402d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f2dc9ffb700 (LWP 7474)): #0 0x7f2e65caa294 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f2e65cac83f in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2e65cacdf8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2e65cacf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2e723d7f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2e723878cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2e721ce06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f2e721d2899 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f2e6792f0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2e718c402d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f2dca7fc700 (LWP 7473)): #0 0x7f2e6793303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2e62505443 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f2e628270a1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f2e6792f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2e718c402d in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f2dcaffd700 (LWP 7472)): #0 0x7f2e6793303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2e62505443 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f2e628270a1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f2e6792f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2e718c402d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f2dcb7fe700 (LWP 7471)): #0 0x7f2e6793303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2e62505443 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f2e628270a1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f2e6792f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2e718c402d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f2dcbfff700 (LWP 7470)): #0 0x7f2e6793303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2e6250446d in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f2e628270a1 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f2e6792f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2e718c402d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f2dd9d3e700 (LWP 7468)): #0 0x7f2e718b7ccd in read () at /lib64/libc.so.6 #1 0x7f2e65cedb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2e65cac999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2e65cacdf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2e65cacf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f2e723d7f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2e723878cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f2e721ce06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f2e721d2899 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f2e6792f0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f2e718c402d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f2dda53f700 (LWP 7466)): #0 0x7f2e718bbbfd in poll () at /lib64/libc.so.6 #1 0x7f2e65cace64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2e65cacf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2e723d7f7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2e723878cb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2e721ce06a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2e721d2899 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f2e6792f0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2e718c402d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f2ddad40700 (LWP 7464)): #0 0x7f2e718bbbfd in poll () at /lib64/libc.so.6 #1 0x7f2e65cace64 in () at
[kontact] [Bug 289107] Kontact crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=289107 Denis Kurzchanged: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #8 from Denis Kurz --- This has been reported for Kontact versions up to 5.2.2 (in bug 365489), setting to confirmed. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 354441] Crash when closing Kontact
https://bugs.kde.org/show_bug.cgi?id=354441 Denis Kurzchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #2 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 289107 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 289107] Kontact crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=289107 Denis Kurzchanged: What|Removed |Added CC||crgla...@gmail.com --- Comment #5 from Denis Kurz --- *** Bug 365489 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 365489] Unknown cause of crash
https://bugs.kde.org/show_bug.cgi?id=365489 Denis Kurzchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 289107 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 289107] Kontact crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=289107 Denis Kurzchanged: What|Removed |Added CC||ja...@jmbeck.com --- Comment #7 from Denis Kurz --- *** Bug 354441 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 289107] Kontact crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=289107 Denis Kurzchanged: What|Removed |Added CC||kdeb...@openaliasbox.org --- Comment #6 from Denis Kurz --- *** Bug 359007 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 359007] Kontact crashed when exit.
https://bugs.kde.org/show_bug.cgi?id=359007 Denis Kurzchanged: What|Removed |Added CC||denis.kurz+kdebugs@posteo.d ||e Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 289107 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 289107] Kontact crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=289107 Denis Kurzchanged: What|Removed |Added CC||bugs.kde@falkensweb.com --- Comment #3 from Denis Kurz --- *** Bug 368354 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 289107] Kontact crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=289107 Denis Kurzchanged: What|Removed |Added CC||d...@gmx.de --- Comment #4 from Denis Kurz --- *** Bug 368168 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368168] Crash when closing kontakt AND mail list whithout text
https://bugs.kde.org/show_bug.cgi?id=368168 Denis Kurzchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 289107 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368354] kmail crashes on exit if open folder properties
https://bugs.kde.org/show_bug.cgi?id=368354 Denis Kurzchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 289107 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 358682] Kontact 5
https://bugs.kde.org/show_bug.cgi?id=358682 Denis Kurzchanged: What|Removed |Added Resolution|WONTFIX |DUPLICATE CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 289107 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 289107] Kontact crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=289107 Denis Kurzchanged: What|Removed |Added CC||ianse...@yahoo.co.uk --- Comment #2 from Denis Kurz --- *** Bug 358682 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 363547] Copying calender folder to owncloud leads to crash
https://bugs.kde.org/show_bug.cgi?id=363547 Denis Kurzchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 355736 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368354] New: kmail crashes on exit if open folder properties
https://bugs.kde.org/show_bug.cgi?id=368354 Bug ID: 368354 Summary: kmail crashes on exit if open folder properties Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@falkensweb.com Application: kontact (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-36-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: exiting the program. no crash if I didn't open an (imap) folder properties. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff8ec8ec940 (LWP 8509))] Thread 12 (Thread 0x7ff82b7f9700 (LWP 8696)): #0 0x7ff8e34f2ae4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff8e34ad9b0 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff8e34ae2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff8e34ae4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff8ea7d5a9b in QEventDispatcherGlib::processEvents (this=0x7ff828c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7ff8ea77cdea in QEventLoop::exec (this=this@entry=0x7ff82b7f8c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7ff8ea5998a4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7ff8ea59e84e in QThreadPrivate::start (arg=0x344dfe0) at thread/qthread_unix.cpp:331 #8 0x7ff8e3cd86fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7ff8e9c9eb5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 11 (Thread 0x7ff834838700 (LWP 8575)): #0 0x7ff8e34ada34 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff8e34ae2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff8e34ae4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff8ea7d5a9b in QEventDispatcherGlib::processEvents (this=0x7ff8240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7ff8ea77cdea in QEventLoop::exec (this=this@entry=0x7ff834837c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7ff8ea5998a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7ff8ea59e84e in QThreadPrivate::start (arg=0x30e2480) at thread/qthread_unix.cpp:331 #7 0x7ff8e3cd86fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7ff8e9c9eb5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 10 (Thread 0x7ff837fff700 (LWP 8537)): #0 0x7ff8e9c92e8d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7ff8e34ae39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff8e34ae4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff8ea7d5a9b in QEventDispatcherGlib::processEvents (this=0x7ff82c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7ff8ea77cdea in QEventLoop::exec (this=this@entry=0x7ff837ffec80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7ff8ea5998a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7ff8ea59e84e in QThreadPrivate::start (arg=0x2cb9020) at thread/qthread_unix.cpp:331 #7 0x7ff8e3cd86fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7ff8e9c9eb5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 9 (Thread 0x7ff861db5700 (LWP 8523)): #0 0x7ff8e34ab43c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff8e34adcfa in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff8e34ae340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff8e34ae4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff8ea7d5a9b in QEventDispatcherGlib::processEvents (this=0x7ff84c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7ff8ea77cdea in QEventLoop::exec (this=this@entry=0x7ff861db4c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7ff8ea5998a4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7ff8ea59e84e in QThreadPrivate::start (arg=0x28b8fc0) at thread/qthread_unix.cpp:331 #8 0x7ff8e3cd86fa in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7ff8e9c9eb5d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 8 (Thread 0x7ff862fcf700 (LWP 8519)): #0 0x7ff8e34ad90b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff8e34ae2cb in ?? () from
[kmail2] [Bug 368350] folder full text search doesn't work : folder status always 'still not indexed'
https://bugs.kde.org/show_bug.cgi?id=368350 --- Comment #1 from Tom Chiverton--- After running balooctl stop I removed .local/share/baloo/emai* and rebooted. Baloo appears hung : $ balooctl status Baloo File Indexer is running Indexer state: Indexing file content Indexed 15615 / 117946 files Current size of index is 76.73 MiB how do I find out what it is actually doing ? Toggleing search off and on via system settings then rechecking just returns it to the same position. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368330] Kontact crash on selecting a mail folder
https://bugs.kde.org/show_bug.cgi?id=368330 Denis Kurzchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||denis.kurz+kdebugs@posteo.d ||e --- Comment #1 from Denis Kurz --- *** This bug has been marked as a duplicate of bug 368329 *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368329] Kontact crash on filing through mails
https://bugs.kde.org/show_bug.cgi?id=368329 --- Comment #1 from Denis Kurz--- *** Bug 368330 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368350] New: folder full text search doesn't work : folder status always 'still not indexed'
https://bugs.kde.org/show_bug.cgi?id=368350 Bug ID: 368350 Summary: folder full text search doesn't work : folder status always 'still not indexed' Product: kmail2 Version: 5.1.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: search Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@falkensweb.com Full text search does not work. Baloo is running though files in .local/share/baloo/email are untouched since Oct 2015. akonadi_baloo_indexer and /usr/bin/akonadi_imap_resource are running Right clicking an IMAP folder, properties, maintaince 'enable' is ticked, but status is 'still not' Reproducible: Always Steps to Reproduce: 1. tools, find 2. search in all, subject contains e 3. search Actual Results: no results, search complete message Expected Results: many results, search complete message -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 368349] New: Kmail failed to display new emails and crashed upon exit
https://bugs.kde.org/show_bug.cgi?id=368349 Bug ID: 368349 Summary: Kmail failed to display new emails and crashed upon exit Product: kmail2 Version: 5.1.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ekkehard.bl...@gmail.com Application: kmail (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-36-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: After running over night, kmail failed to show newly arrived emil messages the next morning. When I closed it (in hopes a restart would solve the problem - which it did), kmail crashed. I am afraid, that's all I can say about this crash. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6424e18940 (LWP 13311))] Thread 19 (Thread 0x7f6370951700 (LWP 14125)): #0 0x7f643bbaeaf0 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f643bb6a24d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f643bb6a4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6445f86a9b in QEventDispatcherGlib::processEvents (this=0x7f636c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f6445f2ddea in QEventLoop::exec (this=this@entry=0x7f6370950c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f6445d4a8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f6445d4f84e in QThreadPrivate::start (arg=0x867600) at thread/qthread_unix.cpp:331 #7 0x7f643c08b6fa in start_thread (arg=0x7f6370951700) at pthread_create.c:333 #8 0x7f644544fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7f6386470700 (LWP 13360)): #0 0x7f644543f9cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f643bbad740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f643bb69e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f643bb6a340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f643bb6a4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6445f86a9b in QEventDispatcherGlib::processEvents (this=0x7f63780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f6445f2ddea in QEventLoop::exec (this=this@entry=0x7f638646fc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f6445d4a8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7f6445d4f84e in QThreadPrivate::start (arg=0xcc2f80) at thread/qthread_unix.cpp:331 #9 0x7f643c08b6fa in start_thread (arg=0x7f6386470700) at pthread_create.c:333 #10 0x7f644544fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7f6387055700 (LWP 13356)): #0 0x7f643bb69802 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f643bb6a2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f643bb6a4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6445f86a9b in QEventDispatcherGlib::processEvents (this=0x7f63740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f6445f2ddea in QEventLoop::exec (this=this@entry=0x7f6387054c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f6445d4a8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f6445d4f84e in QThreadPrivate::start (arg=0xf6c030) at thread/qthread_unix.cpp:331 #7 0x7f643c08b6fa in start_thread (arg=0x7f6387055700) at pthread_create.c:333 #8 0x7f644544fb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f6387ded700 (LWP 13351)): #0 0x7f643bbaeae7 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f643bb69c09 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f643bb6a317 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f643bb6a4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6445f86a9b in QEventDispatcherGlib::processEvents (this=0x7f637c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f6445f2ddea in QEventLoop::exec (this=this@entry=0x7f6387decc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f6445d4a8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f6445d4f84e in QThreadPrivate::start (arg=0xbb8b00) at thread/qthread_unix.cpp:331 #8 0x7f643c08b6fa in start_thread (arg=0x7f6387ded700) at pthread_create.c:333 #9 0x7f644544fb5d in clone () at
[kmail2] [Bug 368346] New: Add configuration option to set notification expiration timeout
https://bugs.kde.org/show_bug.cgi?id=368346 Bug ID: 368346 Summary: Add configuration option to set notification expiration timeout Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jan...@hbz-nrw.de With KDE/Plasma 5 a change was made to the notification system which keeps desktop notifications from being saved in the notifications history unless they´re explicitly marked as "persistent": cf. the discussion at https://github.com/blue-systems/plasma-5.4/issues/48 To me, this is a rather annoying behavior especially with notifications for incoming mails (mine are sorted to a bunch of folders automatically and if I did not read the notification I have to go on a hunt for the new mail...). Other people have similar complaints in different situations; e.g. see Bug #356657. Since the notifications protocol mandates that the app sending the notification is responsible for the timeout I´d suggest adding an appropriate option to the KMail configuration. The behavior of "notify-send" when used with the "-t 0" switch makes some sense: it shows the notification for a few seconds in a pop up window which then auto-hides while the notification is kept in the systray widget (notification history) unless dismissed explicitly. On the other hand it might be even better if one could configure two timeouts: one for the pop up and one for the time the notification would be kept in the history until dismissed automatically (with 0 probably meaning: keep until dismissed manually by the user). Reproducible: Always I´m torn between marking this as a wishlist item and a bug because I consider it a regression... -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner
https://bugs.kde.org/show_bug.cgi?id=364342 Daniel Vrátilchanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im-runtime/c25dcbd8852879a2 ||f7ee102ef0f683b3dad7 Status|UNCONFIRMED |RESOLVED Version Fixed In||16.08.1 --- Comment #15 from Daniel Vrátil --- Git commit c25dcbd8852879a2f7ee102ef0f683b3dad7 by Daniel Vrátil. Committed on 06/09/2016 at 13:33. Pushed by dvratil into branch 'Applications/16.08'. Don't link AkonadiContact from serializer plugins This leads to crashes when the serializer plugin gets loaded from non-GUI thread (like from KRunner), because AkonadiContact depends on Qt5WebEngine, and even just linking Qt5WebEngine triggers static globals initialization that crashes in non-GUI thread. FIXED-IN: 16.08.1 M +2-2plugins/CMakeLists.txt M +13 -6plugins/akonadi_serializer_addressee.cpp M +0-1plugins/akonadi_serializer_contactgroup.cpp http://commits.kde.org/kdepim-runtime/c25dcbd8852879a2f7ee102ef0f683b3dad7 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 368324] Using "not read" filter automatically read all articles
https://bugs.kde.org/show_bug.cgi?id=368324 Christoph Feckchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 350731 *** -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately
https://bugs.kde.org/show_bug.cgi?id=350731 Christoph Feckchanged: What|Removed |Added CC||gabrimo...@gmail.com --- Comment #27 from Christoph Feck --- *** Bug 368324 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368330] New: Kontact crash on selecting a mail folder
https://bugs.kde.org/show_bug.cgi?id=368330 Bug ID: 368330 Summary: Kontact crash on selecting a mail folder Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kdeb...@munin-soft.de Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I started KONATCT with LIBGL_ALWAYS_SOFTWARE=1, as other reports indicated an issue with noveau, but when I select a specific mail folder (happened now three time in a row) which has one unread mail, it directly crashes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f345445c940 (LWP 4022))] Thread 42 (Thread 0x7f32f4ed9700 (LWP 4168)): #0 0x7f344c0aa019 in g_mutex_lock (mutex=mutex@entry=0x7f32e8000990) at gthread-posix.c:1335 #1 0x7f344c065595 in g_main_context_prepare (context=context@entry=0x7f32e8000990, priority=priority@entry=0x7f32f4ed8b40) at gmain.c:3444 #2 0x7f344c065f5b in g_main_context_iterate (context=context@entry=0x7f32e8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3820 #3 0x7f344c06614c in g_main_context_iteration (context=0x7f32e8000990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7f3451949aeb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f32e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f34518f176a in QEventLoop::exec(QFlags) (this=this@entry=0x7f32f4ed8c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f34517173b3 in QThread::exec() (this=) at thread/qthread.cpp:500 #7 0x7f345171c2d8 in QThreadPrivate::start(void*) (arg=0x28fd6a0) at thread/qthread_unix.cpp:341 #8 0x7f344ccb6474 in start_thread (arg=0x7f32f4ed9700) at pthread_create.c:333 #9 0x7f3450e0f3ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 41 (Thread 0x7f32f7eff700 (LWP 4149)): #0 0x7f344c0aa019 in g_mutex_lock (mutex=mutex@entry=0x7f32fad0) at gthread-posix.c:1335 #1 0x7f344c06601b in g_main_context_iterate (priority=, n_fds=1, fds=0x7f32f0002360, timeout=, context=0x7f32fad0) at gmain.c:4130 #2 0x7f344c06601b in g_main_context_iterate (context=context@entry=0x7f32fad0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7f344c06614c in g_main_context_iteration (context=0x7f32fad0, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7f3451949aeb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f32f940, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f34518f176a in QEventLoop::exec(QFlags) (this=this@entry=0x7f32f7efec80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f34517173b3 in QThread::exec() (this=) at thread/qthread.cpp:500 #7 0x7f345171c2d8 in QThreadPrivate::start(void*) (arg=0x3bb12a0) at thread/qthread_unix.cpp:341 #8 0x7f344ccb6474 in start_thread (arg=0x7f32f7eff700) at pthread_create.c:333 #9 0x7f3450e0f3ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 40 (Thread 0x7f3304912700 (LWP 4135)): #0 0x7f344ccbc09f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f32b129 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f32b840 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f32ba10 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3285cd in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f344ccb6474 in start_thread (arg=0x7f3304912700) at pthread_create.c:333 #6 0x7f3450e0f3ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 39 (Thread 0x7f3306bca700 (LWP 4081)): #0 0x7f344c0aa019 in g_mutex_lock (mutex=mutex@entry=0x7f32f8000990) at gthread-posix.c:1335 #1 0x7f344c065595 in g_main_context_prepare (context=context@entry=0x7f32f8000990, priority=priority@entry=0x7f3306bc9b40) at gmain.c:3444 #2 0x7f344c065f5b in g_main_context_iterate (context=context@entry=0x7f32f8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3820 #3 0x7f344c06614c in g_main_context_iteration (context=0x7f32f8000990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7f3451949aeb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f32f80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f34518f176a in QEventLoop::exec(QFlags) (this=this@entry=0x7f3306bc9c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
[kontact] [Bug 368329] New: Kontact crash on filing through mails
https://bugs.kde.org/show_bug.cgi?id=368329 Bug ID: 368329 Summary: Kontact crash on filing through mails Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kdeb...@munin-soft.de Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I started Kontact with LIBGL_ALWAYS_SOFTWARE=1, as other reports suggested that in order to prevent crashes in conjunction with the noveau driver I also use. I was browsing my mail folders for unread mail to check it. Having already selected and read a number of items in the reading pane, Kontact crashed when selecting another one. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1965923940 (LWP 3325))] Thread 51 (Thread 0x7f17a700 (LWP 3512)): #0 0x7f195e18309f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1843248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f184357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f195e17d474 in start_thread (arg=0x7f17a700) at pthread_create.c:333 #4 0x7f19622d63ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 50 (Thread 0x7f17b4c37700 (LWP 3511)): #0 0x7f195e18309f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1843248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f184357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f195e17d474 in start_thread (arg=0x7f17b4c37700) at pthread_create.c:333 #4 0x7f19622d63ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 49 (Thread 0x7f17b5438700 (LWP 3510)): #0 0x7f195e18309f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1843248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f184357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f195e17d474 in start_thread (arg=0x7f17b5438700) at pthread_create.c:333 #4 0x7f19622d63ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 48 (Thread 0x7f17b5c39700 (LWP 3509)): #0 0x7f195e18309f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1843248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f184357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f195e17d474 in start_thread (arg=0x7f17b5c39700) at pthread_create.c:333 #4 0x7f19622d63ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 47 (Thread 0x7f17b643a700 (LWP 3508)): #0 0x7f195e18309f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1843248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f184357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f195e17d474 in start_thread (arg=0x7f17b643a700) at pthread_create.c:333 #4 0x7f19622d63ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 46 (Thread 0x7f17b6c3b700 (LWP 3507)): #0 0x7f195e18309f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1843248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f184357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f195e17d474 in start_thread (arg=0x7f17b6c3b700) at pthread_create.c:333 #4 0x7f19622d63ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 45 (Thread 0x7f17b743c700 (LWP 3506)): #0 0x7f195e18309f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1843247011 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f184357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f195e17d474 in start_thread (arg=0x7f17b743c700) at pthread_create.c:333 #4 0x7f19622d63ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 44 (Thread 0x7f18013a8700 (LWP 3505)): #0 0x7f195e18309f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f184354da6b in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f184354daa9 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f195e17d474 in start_thread (arg=0x7f18013a8700) at pthread_create.c:333 #4 0x7f19622d63ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 43 (Thread 0x7f1801be9700 (LWP 3470)): #0
[kontact] [Bug 340277] Kontact crashed on startup (~CacheLocker)
https://bugs.kde.org/show_bug.cgi?id=340277 Dominik Haumannchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Dominik Haumann --- *** This bug has been marked as a duplicate of bug 361426 *** -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 368324] New: Using "not read" filter automatically read all articles
https://bugs.kde.org/show_bug.cgi?id=368324 Bug ID: 368324 Summary: Using "not read" filter automatically read all articles Product: akregator Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: gabrimo...@gmail.com kubuntu 15.04 akregator 5.1.3 kde framework 5.18.0 qt 5.5.1 (compiled with 5.5.1) If in a source I use "unread" filter at first it works. However if I select first unread article to read it, after my configured delay (1 sec) it is marked as read. It is then instantly removed (probably this is the fix for bug 117874 "Read articles not instantly removed if filter is set to 'unread'"). The problem is that then next unread article is automatically selected. After a second even this article is set to read and disappears and so on. So after n seconds, all my n articles are marked as read even if I'm still reading first one. Spectacularly if I set delay to 0, reading first unread article is the same to "mark source as read" Speaking for myself I would prefer that read articles were not instantly removed if filter is set to 'unread' (old behaviour), since I can see which article I've read in last source. In any case, after an article is istantly removed, no article should be selected. Right now I cannot use the filter. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368323] New: Applying a filter crashed Kmail and Kontact
https://bugs.kde.org/show_bug.cgi?id=368323 Bug ID: 368323 Summary: Applying a filter crashed Kmail and Kontact Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: christian.saem...@gmx.de Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.0-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I applied a filter (by using the hotkey) which is supposed to move an email to a folder - Unusual behavior I noticed: Kmail/Kontact crashed - Custom settings of the application: My Akonadi setup seems to be problematic. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7facfda17940 (LWP 18422))] Thread 43 (Thread 0x7fab51134700 (LWP 18627)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faced9d4129 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7faced9d4840 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7faced9d4a10 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7faced9d15cd in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #6 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 42 (Thread 0x7fab51ff9700 (LWP 18593)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7fab527fa700 (LWP 18592)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7fab4a7fa700 (LWP 18591)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 39 (Thread 0x7fab52ffb700 (LWP 18590)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7fab537fc700 (LWP 18589)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7fab53ffd700 (LWP 18588)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3248163 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7faba09b2700 (LWP 18587)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe3247011 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe357e781 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7fabb61b8700 (LWP 18586)): #0 0x7facf626509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe354da6b in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fabe354daa9 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7facf625f474 in start_thread () at /lib64/libpthread.so.0 #4 0x7facfa3b83ed in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7faba3140700 (LWP 18524)): #0 0x7facf5653019 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7facf560eff2 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7facf560f14c in
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 --- Comment #61 from Alejandro Lorenzo--- I think each software should be responsible for its own bugs. If the bug is in Owncloud, just fix Owncloud and do not make miserable other projects because of your faults. Workarounds and such usually open the door to bugs ( Code paths that do not execute often or can only be tested to some versions of software), create harder to maintain software and generally, eat kittens, so personally I think it would be a bad idea -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 --- Comment #60 from quazgar--- OK, there seems to be a fix in OwnCloud now: https://github.com/owncloud/calendar/issues/706 https://github.com/owncloud/calendar/pull/707 Still, would it be possible to make the ics file parser "more clever"? Like saying "OK, there is a property PRODID:-//ownCloud calendar v1.2.2 or similar, so let's just assume the VERSION property is missing but would be something reasonable such as 2.0 or whatever." This would be an ugly workaround but it would help people affected by buggy CalDAV servers. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368316] New: Kontact crashes often after minutes of running
https://bugs.kde.org/show_bug.cgi?id=368316 Bug ID: 368316 Summary: Kontact crashes often after minutes of running 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: ra.be.baer...@googlemail.com Application: kontact (5.2.3) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.2-201.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: Since the beginning of the month Kontact crashes often after minutes of running. Kontact is called from the autostart feature of KDE during login procedure. The crashes are repetitiv. When switching to a newly arrived message in KMail Kontact crashes. This happens sometimes when switching between messages in different folders (no matter wether backup or other provider). It happend the other day twice during writting mails. (There where just two mails to write late in the evening the night before.) Kontact is running on a Fedora 24 x64. Installed from the repository packages The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fa8a56cb940 (LWP 2583))] Thread 29 (Thread 0x7fa7bb7fe700 (LWP 3907)): #0 0x7fa8a1e803ed in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa89b05aa06 in g_main_context_poll (priority=, n_fds=1, fds=0x7fa7ac002c20, timeout=, context=0x7fa7ac000990) at gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7fa7ac000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7fa89b05ab1c in g_main_context_iteration (context=0x7fa7ac000990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7fa8a2c9424b in QEventDispatcherGlib::processEvents (this=0x7fa7ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7fa8a2c435ea in QEventLoop::exec (this=this@entry=0x7fa7bb7fdc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fa8a2aa2343 in QThread::exec (this=) at thread/qthread.cpp:500 #7 0x7fa8a2aa699a in QThreadPrivate::start (arg=0x560c230885f0) at thread/qthread_unix.cpp:341 #8 0x7fa89c2985ca in start_thread (arg=0x7fa7bb7fe700) at pthread_create.c:333 #9 0x7fa8a1e8bf6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 28 (Thread 0x7fa7bbfff700 (LWP 3904)): #0 g_main_context_prepare (context=context@entry=0x7fa7b4000990, priority=priority@entry=0x7fa7bbffeb40) at gmain.c:3445 #1 0x7fa89b05a92b in g_main_context_iterate (context=context@entry=0x7fa7b4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3820 #2 0x7fa89b05ab1c in g_main_context_iteration (context=0x7fa7b4000990, may_block=may_block@entry=1) at gmain.c:3901 #3 0x7fa8a2c9424b in QEventDispatcherGlib::processEvents (this=0x7fa7b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7fa8a2c435ea in QEventLoop::exec (this=this@entry=0x7fa7bbffec80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fa8a2aa2343 in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7fa8a2aa699a in QThreadPrivate::start (arg=0x560c2305f9d0) at thread/qthread_unix.cpp:341 #7 0x7fa89c2985ca in start_thread (arg=0x7fa7bbfff700) at pthread_create.c:333 #8 0x7fa8a1e8bf6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 27 (Thread 0x7fa7d8ff9700 (LWP 3813)): #0 g_mutex_unlock (mutex=0x7fa7c990) at gthread-posix.c:1347 #1 0x7fa89b05a419 in g_main_context_check (context=context@entry=0x7fa7c990, max_priority=2147483647, fds=fds@entry=0x7fa7c0003020, n_fds=n_fds@entry=1) at gmain.c:3679 #2 0x7fa89b05a9a4 in g_main_context_iterate (context=context@entry=0x7fa7c990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3837 #3 0x7fa89b05ab1c in g_main_context_iteration (context=0x7fa7c990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7fa8a2c9424b in QEventDispatcherGlib::processEvents (this=0x7fa7c8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7fa8a2c435ea in QEventLoop::exec (this=this@entry=0x7fa7d8ff8c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fa8a2aa2343 in QThread::exec (this=) at thread/qthread.cpp:500 #7 0x7fa8a2aa699a in QThreadPrivate::start (arg=0x560c228a6c10) at thread/qthread_unix.cpp:341 #8 0x7fa89c2985ca in start_thread (arg=0x7fa7d8ff9700) at pthread_create.c:333 #9 0x7fa8a1e8bf6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread
[Akonadi] [Bug 323455] "Filter account is missing" after KMail startup
https://bugs.kde.org/show_bug.cgi?id=323455 j_ka...@arcor.de changed: What|Removed |Added CC||j_ka...@arcor.de --- Comment #16 from j_ka...@arcor.de --- I can confirm this problem for kmail/kontact 5.2.3 and akonadi 5.2.2 (currently in Debian testing). 1. The dialogs pop up when there is an automatic incoming mail filter set to filter only some of all available accounts. (In my case there are four IMAP accounts and I want to spam-filter two of them. I use bogofilter.) 2. The dialogs pop up *before* kmail or kontact are actually started, just after logging in. (Presumably when KDE starts akonadi?) 3. There is more than one dialog. (In my case there are two, presumably for the two checked IMAP accounts I want to filter.) 4. There is no workaround other than turning automatic filtering off and filtering manually. In particular, leaving the message boxes open and restarting akonadi, or leaving them open without doing anything doesn't work — no filtering gets done. 5. I cannot confirm that this is due to a slow CPU or old hardware. I have a fairly modern laptop (Intel i3-3110M @ 2.40GHz, 4GB RAM). I suggest to give the bug high priority. To me, a non-working spam filter is a show stopper for a mail client. -- You are receiving this mail because: You are the assignee for the bug.