[kmail2] [Bug 358840] kmail composer: menu item "send" missing
https://bugs.kde.org/show_bug.cgi?id=358840
--- Comment #2 from Christian Boltz <kde-b...@cboltz.de> ---
The menu entry is back in KMail 5.1.2 :-) - thanks!
However it has a slightly strange name: it's named "E-Mail mit Kurzbefehlen
versenden" ("send mail with shortcuts") - and I wonder if the "mit
Kurzbefehlen" / "with shortcuts" part was intentional.
--
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 308968] certificate is not remembered
https://bugs.kde.org/show_bug.cgi?id=308968 Christian Heller <christian.hel...@tuxtax.de> changed: What|Removed |Added CC||christian.hel...@tuxtax.de -- 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 356431] no address autocompletion
https://bugs.kde.org/show_bug.cgi?id=356431 Christian Trippe <christiande...@web.de> changed: What|Removed |Added CC||christiande...@web.de -- 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 357481] KMail doesn't honor the "always sign with GPG" flag in idendity when replying
https://bugs.kde.org/show_bug.cgi?id=357481 --- Comment #10 from Christian Boltz <kde-b...@cboltz.de> --- I don't want to force you to do superfluous backporting work (better spend your time on fixing other bugs;-) ) so I'll trust you that you got everything right. Just tell me which version will have the fixed code, and I'll report back as soon as it is released and packaged for openSUSE Tumbleweed ;-) -- 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 357481] KMail doesn't honor the "always sign with GPG" flag in idendity when replying
https://bugs.kde.org/show_bug.cgi?id=357481 --- Comment #8 from Christian Boltz <kde-b...@cboltz.de> --- Just for the records: a debugging session on IRC (thanks for doing that!) showed that - the test works (fails without my patch, and succeeds with it) - the test needs GPG signing enabled in the default idendity to work - my patch fixes the issue -- 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 358840] New: kmail composer: menu item "send" missing
https://bugs.kde.org/show_bug.cgi?id=358840 Bug ID: 358840 Summary: kmail composer: menu item "send" missing Product: kmail2 Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: kde-b...@cboltz.de In KMail 4.x, the "messages" menu in the composer had the following menu items: - send email - send email with [transport submenu] - send later - send later with [transport submenu] In KMail 5.1.1, the "send email" menu item is missing, so you can't send a mail now with the default transport. The workaround is to use the toolbar or the keyboard shortcut, but I'd like to have the menu entry back ;-) -- 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 357481] KMail doesn't honor the "always sign with GPG" flag in idendity when replying
https://bugs.kde.org/show_bug.cgi?id=357481 --- Comment #5 from Christian Boltz <kde-b...@cboltz.de> --- The line you mentioned is line 1310, but my patch applies around line 1644 *). I'm not sure what exactly happens, but I'd guess something is overwriting/setting mLastSignActionState to false somewhere in between. That said - the difference between my patch and the actual code is simple: With my patch, it works - without, it doesn't ;-) (tested with KMail 5.1.1 aka kdepim-15.12.1.tar.xz) *) line numbers fro git as shown on https://quickgit.kde.org/?p=kdepim.git=blob=dd45b50a50934ac22c05c240d883f3acfcd2a477=1af4bde89d080692b7dbb90ce00e4f5136af2144=kmail%2Feditor%2Fkmcomposewin.cpp -- 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 358802] New: KMail settings - key expire warning doesn't enable apply button
https://bugs.kde.org/show_bug.cgi?id=358802 Bug ID: 358802 Summary: KMail settings - key expire warning doesn't enable apply button Product: kmail2 Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-bugs@kde.org Reporter: kde-b...@cboltz.de In the KMail settings dialog, you can setup a warning if keys or certificates expire soon. Unfortunately, changing those values doesn't enable the 'apply' button and also doesn't cause a question when switching to another part of the config dialog. Reproducer: - open the KMail config dialog - go to "security" - go to the "misc" tab - in the "warn if certificates/keys expire soon", change one of the values (for example 20 days instead of 14) Expected results: - the 'apply' button gets enabled - when switching to another area of the config dialog (for example "idendities"), KMail asks if the changes should be saved Actual result: none of the above The good news is that the changed values get saved when clicking the "OK" button. (KMail 5.1.1 on openSUSE Tumbleweed) -- 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 357481] KMail doesn't honor the "always sign with GPG" flag in idendity when replying
https://bugs.kde.org/show_bug.cgi?id=357481 Christian Boltz <kde-b...@cboltz.de> changed: What|Removed |Added Version|unspecified |5.1 --- Comment #3 from Christian Boltz <kde-b...@cboltz.de> --- For the records: KMail 5.1.1 is more consistent - it never enables the GPG signing ;-) Therefore this patch is still needed in KMail 5.1.1 - and still works with it. As I said on IRC, I'm not familiar with phabricator etc. and am too busy to learn it (sorry!), so I'd prefer if you can push this patch. -- 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
[kleopatra] [Bug 358210] New: Add support for secure checksums: SHA-2 instead of SHA-1 and MD5
https://bugs.kde.org/show_bug.cgi?id=358210 Bug ID: 358210 Summary: Add support for secure checksums: SHA-2 instead of SHA-1 and MD5 Product: kleopatra Version: 2.2.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: dah5a...@genodeftest.de CC: kdepim-bugs@kde.org, m...@kde.org Currently Kleopatra supports md5sum and sha1sum to generate checksums. Using sha256sum and sha512sum would be highly appreciated since MD5 is known to be broken for years and SHA-1 is very weak, its use is highly discouraged. Reproducible: Always Steps to Reproduce: 1. Open preferences 2. go to crypto operations, tab "File operations" 3. choose "Checksum program to use" Actual Results: only md5sum (broken) and sha1sum (very weak) are available Expected Results: sha256sum and sha512sum should be available. If possible (violation of standards?) one of those commands based on SHA-2 should be default. -- 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 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook
https://bugs.kde.org/show_bug.cgi?id=354400 Christian Heller <christian.hel...@tuxtax.de> changed: What|Removed |Added CC||christian.hel...@tuxtax.de -- 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
[kleopatra] [Bug 341293] Kleopatra self-test should not expect gpg-agent to be running for GnuPG >= 2.1
https://bugs.kde.org/show_bug.cgi?id=341293 Christian Stadelmann <dah5a...@genodeftest.de> changed: What|Removed |Added CC||dah5a...@genodeftest.de -- 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 357481] New: KMail doesn't honor the "always sign with GPG" flag in idendity when replying
https://bugs.kde.org/show_bug.cgi?id=357481 Bug ID: 357481 Summary: KMail doesn't honor the "always sign with GPG" flag in idendity when replying Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: kde-b...@cboltz.de KMail 4.14.10 on KDE 4.14.14 on openSUSE Tumbleweed In one of my idendities, I have set my PGP key and enabled the "Automatically sign messages" option. Also, I have assigned that idendity for one IMAP account and selected a folder inside that account. When writing a _new_ message, the editor opens with the "Sign message" button pre-selected - as expected. Good. However, when I reply to a message, the editor always opens with the "Sign message" button _not_ selected. Bad. This even happens when replying to signed mails, which enables the "Sign message" button in other folders if using an idendity without the "Automatically sign message" setting. Bad again. Reproducer: - setup an idendity with "Automatically sign messages" and your GPG key - assign that idendity to an IMAP account (assigning to a folder might be enough) - store at least two mails in that folder, one GPG-signed, one not signed. - reply to both mails - in the mail editor, check if the "Sign message" button is pre-selected Expected behaviour: The mail editor should have the "Sign message" button pre-selected because of the idendity settings (remember: the idendity has "Automatically sign message" set) -- 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 323168] GPG signature validation fails due to KMail modifying headers within received mails
https://bugs.kde.org/show_bug.cgi?id=323168 Christian Boltz <kde-b...@cboltz.de> changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #11 from Christian Boltz <kde-b...@cboltz.de> --- The requested information was provided long ago, back to confirmed. -- 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 357481] KMail doesn't honor the "always sign with GPG" flag in idendity when replying
https://bugs.kde.org/show_bug.cgi?id=357481 --- Comment #1 from Christian Boltz <kde-b...@cboltz.de> --- Created attachment 96433 --> https://bugs.kde.org/attachment.cgi?id=96433=edit patch This patch seems to work - "Sign message" is now always enabled in the composer when starting a new mail or a reply in a folder using an idendity with "Automatically sign messages". Also, when replying to a signed mail, "Sign message" still (and now always) gets enabled. Notes: - I tested this patch with various combinations (folder using an idendity with / without "Automatically sign messages", signed / unsigned mails, new mail / reply), and it seems to do the expected thing everywhere - I'm not a C or C++ developer, so please double-check the patch - even if it's short and seems to work, it's still copy ;-) - I don't have (and don't want, sorry) write access to the KDE git, so please someone take the patch and apply it -- 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 357139] New: Kontact crashed when choosing "configure completion" in kmail composer
https://bugs.kde.org/show_bug.cgi?id=357139 Bug ID: 357139 Summary: Kontact crashed when choosing "configure completion" in kmail composer 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: christiande...@web.de Application: kontact (5.1) Qt Version: 5.5.0 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: 1.)Open kontact with kmail included. 2.) Open the kmail composer 3.) RIght click in the address field 4.) Choose "configure completion" (guessed from German "Vervollständigung einrichten ..." 5.) kontact crashes (sometimes but not always) The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe54ccb9800 (LWP 7990))] Thread 25 (Thread 0x7fe52edb3700 (LWP 7991)): #0 0x7fe549900c1d in poll () from /lib64/libc.so.6 #1 0x7fe5430a3422 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fe5430a500f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fe530f02c29 in QXcbEventReader::run (this=0xfe8420) at qxcbconnection.cpp:1214 #4 0x7fe54a20e55f in QThreadPrivate::start (arg=0xfe8420) at thread/qthread_unix.cpp:331 #5 0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7fe54990904d in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7fe5275ef700 (LWP 7992)): #0 0x7fe542c8405f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe5474644a3 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7fe5474644c9 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7fe54990904d in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7fe4e2d0b700 (LWP 7993)): #0 postEventSourcePrepare (s=0x7fe4dc0012d0, timeout=0x7fe4e2d0ac14) at kernel/qeventdispatcher_glib.cpp:248 #1 0x7fe5424624ad in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe542462d80 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe542462f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe54a43fa5b in QEventDispatcherGlib::processEvents (this=0x7fe4dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fe54a3e6a63 in QEventLoop::exec (this=this@entry=0x7fe4e2d0add0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fe54a20984a in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fe54a20e55f in QThreadPrivate::start (arg=0x11796b0) at thread/qthread_unix.cpp:331 #8 0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe54990904d in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7fe4dbfff700 (LWP 7994)): #0 0x7fe542c8405f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe5471704cd in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7fe547492da1 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7fe54990904d in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7fe4db7fe700 (LWP 7995)): #0 0x7fe542c8405f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe5471714a3 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x7fe547492da1 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7fe54990904d in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7fe4ca4f4700 (LWP 7996)): #0 0x7fe549900c1d in poll () from /lib64/libc.so.6 #1 0x7fe542462e64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe542462f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe54a43fa5b in QEventDispatcherGlib::processEvents (this=0x7fe4c40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fe54a3e6a63 in QEventLoop::exec (this=this@entry=0x7fe4ca4f3dd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fe54a20984a in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fe54a20e55f in QThreadPrivate::start (arg=0x15cc760) at thread/qthread_unix.cpp:331 #7 0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe54990904d in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7fe4c9cf3700 (LWP 7997)): #0 0x7fe5424a4d14 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fe5424628e9 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe542462df8 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe542462f7c in g_main_context_iteration
[Akonadi] [Bug 353957] Akonadi IMAP resource crashed when checked maildir
https://bugs.kde.org/show_bug.cgi?id=353957 --- Comment #12 from Christian Bayer <christian_...@gmx.de> --- Since no one seems to acknowledge that this is an important bug that needs to be fixed, here is a script for people who can't wait. Replace akonadi_imap_resource_3 with the name of the akonadi resource that crashes. $ cat imap_resource_respawn #!/bin/bash while [ /bin/true ] do PID=`pgrep -f "/usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_3"` if [ -z $PID ] then echo process $PID died. Respawning. /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_3& fi sleep 10s done -- 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 353957] Akonadi IMAP resource crashed when checked maildir
https://bugs.kde.org/show_bug.cgi?id=353957 Christian Bayer <christian_...@gmx.de> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #8 from Christian Bayer <christian_...@gmx.de> --- *** This bug has been confirmed by popular vote. *** -- 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 353957] Akonadi IMAP resource crashed when checked maildir
https://bugs.kde.org/show_bug.cgi?id=353957 --- Comment #9 from Christian Bayer <christian_...@gmx.de> --- Wow, this bug stinks. I have to restart the Akonadi service everytime it crashes, otherwise I feel like back in the 90's when you got only one email per day. -- 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 353957] Akonadi IMAP resource crashed when checked maildir
https://bugs.kde.org/show_bug.cgi?id=353957 --- Comment #7 from Christian Bayer <christian_...@gmx.de> --- More information: This never crashed on the Ubuntu 15.04 version of akonadi. I have two imap inboxes, an outlook.com one and a big gmail inbox. The latter is the one that crashes now. I just have to wait for about an hour, sometimes even less. It will crash 4-8 times a day. -- 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 353957] Akonadi IMAP resource crashed when checked maildir
https://bugs.kde.org/show_bug.cgi?id=353957 Christian Bayer <christian_...@gmx.de> changed: What|Removed |Added CC||christian_...@gmx.de --- Comment #5 from Christian Bayer <christian_...@gmx.de> --- Also had the same backtrace on Ubuntu 15.10: Application: Akonadi Resource (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbbef562840 (LWP 5821))] Thread 5 (Thread 0x7fbbec8a5700 (LWP 5822)): #0 0x7fbbfeebc8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fbbfa684bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fbbfa68674f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fbbef052a39 in QXcbEventReader::run (this=0xea2fe0) at qxcbconnection.cpp:1105 #4 0x7fbbff7c62be in QThreadPrivate::start (arg=0xea2fe0) at thread/qthread_unix.cpp:337 #5 0x7fbbfa8a36aa in start_thread (arg=0x7fbbec8a5700) at pthread_create.c:333 #6 0x7fbbfeec7eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fbbe5a3c700 (LWP 5827)): #0 0x7fbbf9d8a869 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fbbf9d45789 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbbf9d4611b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbbf9d462fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbbff9fd29b in QEventDispatcherGlib::processEvents (this=0x7fbbe8e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fbbff9a375a in QEventLoop::exec (this=this@entry=0x7fbbe5a3bd80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fbbff7c13d4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fbbff7c62be in QThreadPrivate::start (arg=0xffcdd0) at thread/qthread_unix.cpp:337 #8 0x7fbbfa8a36aa in start_thread (arg=0x7fbbe5a3c700) at pthread_create.c:333 #9 0x7fbbfeec7eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fbbe523b700 (LWP 5828)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7fbbff7c7496 in QWaitConditionPrivate::wait_relative (time=3, this=0x7fbbe0019840) at thread/qwaitcondition_unix.cpp:126 #2 QWaitConditionPrivate::wait (time=3, this=0x7fbbe0019840) at thread/qwaitcondition_unix.cpp:134 #3 QWaitCondition::wait (this=this@entry=0x7fbbe0019300, mutex=mutex@entry=0x7fbbe0019440, time=3) at thread/qwaitcondition_unix.cpp:208 #4 0x7fbbff7c3003 in QThreadPoolThread::run (this=0x7fbbe00192f0) at thread/qthreadpool.cpp:127 #5 0x7fbbff7c62be in QThreadPrivate::start (arg=0x7fbbe00192f0) at thread/qthread_unix.cpp:337 #6 0x7fbbfa8a36aa in start_thread (arg=0x7fbbe523b700) at pthread_create.c:333 #7 0x7fbbfeec7eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fbbd700 (LWP 5836)): #0 0x7fbbfeeb849d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fbbf658af75 in ?? () from /usr/lib/nvidia-352-updates/tls/libnvidia-tls.so.352.41 #2 0x7fbbf9d894e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbbf9d45cd4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbbf9d46190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fbbf9d462fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fbbff9fd29b in QEventDispatcherGlib::processEvents (this=0x7fbbd40008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #7 0x7fbbff9a375a in QEventLoop::exec (this=this@entry=0x7fbbdfffed80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x7fbbff7c13d4 in QThread::exec (this=) at thread/qthread.cpp:503 #9 0x7fbbff7c62be in QThreadPrivate::start (arg=0xffdf80) at thread/qthread_unix.cpp:337 #10 0x7fbbfa8a36aa in start_thread (arg=0x7fbbd700) at pthread_create.c:333 #11 0x7fbbfeec7eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fbbef562840 (LWP 5821)): [KCrash Handler] #6 0x7fbc0259d693 in Akonadi::Entity::id (this=this@entry=0x7fbbffa75518 <QArrayData::shared_null+24>) at ../../../../akonadi/src/core/entity.cpp:72 #7 0x0045833e in ImapResourceBase::retrieveItems (this=this@entry=0xfb1da0, col=...) at ../../../resources/imap/imapresourcebase.cpp:435 #8 0x7fbc0294232d in Akonadi::ResourceBasePrivate::slotItemRetrievalCollectionFetchDone (this=, job=0x104bcb0) at ../../../../akonadi/src/agentbase/resourcebase.cpp:954 #9 0x7fbc02944200 in Akonadi::ResourceBase::qt_static_metacall (_o=_o@entry=0xfb1
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 Christian <gen...@moin.fi> changed: What|Removed |Added CC|gen...@moin.fi | -- 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 354519] New: Kmail crashes when opening attachment
https://bugs.kde.org/show_bug.cgi?id=354519 Bug ID: 354519 Summary: Kmail crashes when opening attachment 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: christian_...@gmx.de Application: kontact (5.0.2) Qt Version: 5.4.2 Operating System: Linux 4.2.0-16-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: Kmail crashed when I clicked the link to an attachment in an email. After the crash I restarted KMail and clicked the link again, but this time it worked. The link pointed to a PDF document that was successfully opened in Okular. Happened with brand new Kubuntu 15.10. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd3e9ea3880 (LWP 3348))] Thread 10 (Thread 0x7fd3e5514700 (LWP 3355)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd40572f48b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fd40572f4c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fd400eaf6aa in start_thread (arg=0x7fd3e5514700) at pthread_create.c:333 #4 0x7fd406621eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7fd39df20700 (LWP 3364)): #0 0x7fd4066168dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fd4002321ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd4002322fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd40715729b in QEventDispatcherGlib::processEvents (this=0x7fd3980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fd4070fd75a in QEventLoop::exec (this=this@entry=0x7fd39df1fd40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fd406f1b3d4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fd406f202be in QThreadPrivate::start (arg=0xe72800) at thread/qthread_unix.cpp:337 #7 0x7fd400eaf6aa in start_thread (arg=0x7fd39df20700) at pthread_create.c:333 #8 0x7fd406621eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7fd39d4cd700 (LWP 3367)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd40543d5b4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fd40575f341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fd400eaf6aa in start_thread (arg=0x7fd39d4cd700) at pthread_create.c:333 #4 0x7fd406621eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7fd39ccad700 (LWP 3368)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd40543e5e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fd40575f341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fd400eaf6aa in start_thread (arg=0x7fd39ccad700) at pthread_create.c:333 #4 0x7fd406621eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fd397fff700 (LWP 3369)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd40543e5e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fd40575f341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fd400eaf6aa in start_thread (arg=0x7fd397fff700) at pthread_create.c:333 #4 0x7fd406621eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fd3977fe700 (LWP 3370)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd40543e5e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fd40575f341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fd400eaf6aa in start_thread (arg=0x7fd3977fe700) at pthread_create.c:333 #4 0x7fd406621eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fd396ffd700 (LWP 3371)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd40543e5e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fd40575f341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fd400eaf6aa in start_thread (arg=0x7fd396ffd700) at pthread_create.c:333 #4 0x7fd406621eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fd3967fc700 (LWP 3372)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #139 from Christian Boltz <kde-b...@cboltz.de> --- Renè, the workaround from comment #118 still works for me: Add a filter like "From contains @" and let it execute "/usr/bin/sleep 0.5" (the time you need may vary, 0.3 wasn't enough for me). -- 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 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #133 from Christian Hilberg <hilb...@kernelconcepts.de> --- Confirming this still happens with KF5 Kontact/Kmail 4.14.10 on today's debian/stretch (where it seems almost all KF5 packages have materialized). -- 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
[plasma4] [Bug 292601] Fetch job error on login
https://bugs.kde.org/show_bug.cgi?id=292601 Christian <gen...@moin.fi> changed: What|Removed |Added CC|gen...@moin.fi | -- 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 267884] akonadi imap doesn't work with gssapi authentication
https://bugs.kde.org/show_bug.cgi?id=267884 --- Comment #26 from Christian Mollekopf <mollek...@kolabsys.com> --- The patch looks indeed harmless. If you can give it a try (to see wether non GSSAPI usage breaks somehow) we could indeed merge it if it solves the issue. -- 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 331826] Emails based on template go to local sent folder instead of that configured
https://bugs.kde.org/show_bug.cgi?id=331826 --- Comment #9 from Christian Gonzalez christian.gonza...@medworx.at --- Full ACK. In fact, this is the main bug why I don't (can't) use Kmail as Email client. -- 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 340759] deleting duplicate mails has no effect
https://bugs.kde.org/show_bug.cgi?id=340759 --- Comment #11 from Christian Hilberg hilb...@kernelconcepts.de --- Update: After following the instructions outlined in [0] for clearing up the akonadi cache directory, it seems that choosing delete duplicate mails on an IMAP folder has the desired effect again. N.B.: I've updated to akonadi 1.13.0-3 from Debian/Unstable in the meantime. [0] https://bugs.kde.org/show_bug.cgi?id=341884 -- 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 236600] KMimeType Crash
https://bugs.kde.org/show_bug.cgi?id=236600 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|REOPENED|RESOLVED CC||mollek...@kolabsys.com Resolution|--- |WORKSFORME -- 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 345992] Keyboard shortcut assigned to archive mail works once, unconfigures itself
https://bugs.kde.org/show_bug.cgi?id=345992 --- Comment #3 from Christian Kalkhoff e...@softmetz.de --- It works after a crash of kmail and restart. But it still does't work more than once after setting the key binding. In older versions it didn't even work after a regular restart. I was only able to reassign the keybinding again, use it once and than it was gone again. -- 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 345992] New: Keyboard shortcut assigned to archive mail works once, unconfigures itself
https://bugs.kde.org/show_bug.cgi?id=345992 Bug ID: 345992 Summary: Keyboard shortcut assigned to archive mail works once, unconfigures itself Product: kmail2 Version: 4.14.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: e...@softmetz.de Since I discovered kmail has an archive feature (which made me move from Thunderbird) I was not able to bind a keyboard shortcut to the archive mail function so it lasted longer than one usage. Reproducible: Always Steps to Reproduce: 1. Open Keyboard Shortcurts and select archive mail 2. Assign some (doesn't matter which) shortcut 3. Use the shortcut to archive some mail 4. Use it again to another Mail Actual Results: In step 4 the mail is not archived. The shortcut is no longer bound to the function in the settings. Expected Results: The keyboard shortcut works more than once. -- 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 345992] Keyboard shortcut assigned to archive mail works once, unconfigures itself
https://bugs.kde.org/show_bug.cgi?id=345992 --- Comment #1 from Christian Kalkhoff e...@softmetz.de --- As it turns out, after kmail2 crashed the key binding now works as expected. Now the toolbar icon I added is gone. Some strange things are going on here. -- 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 345497] Expiry options on folder properties doesn't move mails
https://bugs.kde.org/show_bug.cgi?id=345497 --- Comment #3 from Christian cnngime...@gmail.com --- (In reply to Laurent Montel from comment #2) Work fine here. Do you have error in console ? I get this: $ kmail --nofork libpng warning: iCCP: Not recognizing known sRGB profile that has been edited loaded the Generic plugin libpng warning: iCCP: too many profiles libpng warning: iCCP: too many profiles [almost 40 times the same libpng warning] ~StorageServiceJobConfigPrivate I think is not of much help. If there's a way to start some kind of debug output, please tell me how. -- 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 345497] New: Expiry options on folder properties doesn't move mails
https://bugs.kde.org/show_bug.cgi?id=345497 Bug ID: 345497 Summary: Expiry options on folder properties doesn't move mails Product: kmail2 Version: 4.14.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: cnngime...@gmail.com I try to use the expiry options under the folder properties of some folders, setted to expire readed mails after 30 days and, instead of using permanently delete expired mails, I setted Move expired mails to and selected an existent folder. When I click on Save preferences and expire now it should move my readed mails more than 30 days long to the designated folder, but instead, **it just copy them**. P.D.: I'm using KMail in spanish, the labels I said may not correspond to the actual english labels. Sorry for that. Reproducible: Always Steps to Reproduce: 1. Open folder preferences and go to the expiry slope, or right click on a folder and select the expiry option. 2. Set Expire readed mails after on and set a number of days. 3. Set Move expired days to on, and select an existent folder (preferable empty so you can see the results). 4. Click on the Save preferences and expire now button, wait and press again. (You may need to close the folder-property dialog check that it didn't move anything and open again). Actual Results: Kmail only copy the correct mails to the designated folder. Expected Results: Kmail should *move* these mails to the designated folder, and they shouldn't appear of the original folder anymore. -- 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 345497] Expiry options on folder properties doesn't move mails
https://bugs.kde.org/show_bug.cgi?id=345497 --- Comment #1 from Christian cnngime...@gmail.com --- At first, I thought it was because KMail downloaded mails again because of my account configuration, so after posted this bug I checked for this matter. I tested again activating the leave the message on the server 7 days, I downloaded the mails (KMail displayed the deleting mails on server status) and then try the expiry options clicking on the Save preferences and expire now: same results, it just copy the mails and don't move anything. -- 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 339449] caldav protocol: Items older than a 3 months (hard coded) are not fetched
https://bugs.kde.org/show_bug.cgi?id=339449 --- Comment #6 from Christian Fowelin fowe...@chemie.uni-hamburg.de --- I do have the same problem with my calendar. After reverting akonadi_davgroupware_ressource to the 4.14.0 version my calendar is working as expected again. This change needs be reverted, user need to see older entries as they do on their mobile devices, for example. -- 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 342268] Incomplete CalDav sync
https://bugs.kde.org/show_bug.cgi?id=342268 Christian Fowelin fowe...@chemie.uni-hamburg.de changed: What|Removed |Added CC||fowe...@chemie.uni-hamburg. ||de -- 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 339449] caldav protocol: Items older than a 3 months (hard coded) are not fetched
https://bugs.kde.org/show_bug.cgi?id=339449 Christian Fowelin fowe...@chemie.uni-hamburg.de changed: What|Removed |Added CC||fowe...@chemie.uni-hamburg. ||de -- 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 340599] CalDAV events are not shown before a given date
https://bugs.kde.org/show_bug.cgi?id=340599 Christian Fowelin fowe...@chemie.uni-hamburg.de changed: What|Removed |Added CC||fowe...@chemie.uni-hamburg. ||de -- 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 308968] certificate is not remembered
https://bugs.kde.org/show_bug.cgi?id=308968 --- Comment #8 from Christian Hilberg hilb...@kernelconcepts.de --- Let me add that I am having the same issue for a certificate that was signed by CACert.org and kdepim 4.14.2 (debian/sid). I was able to sort of fix this by manually importing that cert's CACert root certificate into the KDE cert store via System Settings--Network and Connections--SSL Settings. I still get some messages about aborted IMAP operations now and then, which I can simply retry and it usually works, but the certificate requester does not show any longer for this certificate. -- 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 308968] certificate is not remembered
https://bugs.kde.org/show_bug.cgi?id=308968 Christian Hilberg hilb...@kernelconcepts.de changed: What|Removed |Added CC||hilb...@kernelconcepts.de --- Comment #7 from Christian Hilberg hilb...@kernelconcepts.de --- Confirming the issue with self-signed cert and kdepim 4.14.2 (debian/sid) -- 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 340759] deleting duplicate mails has no effect
https://bugs.kde.org/show_bug.cgi?id=340759 Christian Hilberg hilb...@kernelconcepts.de changed: What|Removed |Added CC||hilb...@kernelconcepts.de --- Comment #4 from Christian Hilberg hilb...@kernelconcepts.de --- KDEPIM 4.14.2 (Debian/Sid) does not remove duplicates for me. Sometimes, the progress bar will show some progress, sometimes not even that. The effect on the folder is the same for both: none. -- 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 340759] deleting duplicate mails has no effect
https://bugs.kde.org/show_bug.cgi?id=340759 --- Comment #5 from Christian Hilberg hilb...@kernelconcepts.de --- I should add, unlike the OP, I'm seeing this with IMAP(S), with Kmail set to always download the IMAP folder contents. -- 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 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 Christian Hilberg hilb...@kernelconcepts.de changed: What|Removed |Added CC||hilb...@kernelconcepts.de --- Comment #128 from Christian Hilberg hilb...@kernelconcepts.de --- Seeing the same issue on Debian for 4.14.1 (jessie) as well as 4.14.2 (sid). For me, duplicates occur only if mail filtering does NOT move the mail to a folder different from INBOX (using IMAP), where I let the filtering happen. Moreover, Folder-Remove Duplicate Messages does not work. Of multiple duplicates, two will remain (if the operation is started at all after selecting this action, which does not seem to reliably be the case for me). I've seen an open bug report for this somewhere but I cannot seem to find it now. Maybe there is some issue here in that Kmail/Akonadi do not reliably detect what ought to be considered the same mail object, and hence the duplication occurs after the filters did not move the mail to a different folder? -- 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 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #129 from Christian Hilberg hilb...@kernelconcepts.de --- Duplicate of this bug: https://bugs.kde.org/show_bug.cgi?id=95064 Possibly related: https://bugs.kde.org/show_bug.cgi?id=288040 Possibly related: https://bugs.kde.org/show_bug.cgi?id=333035 -- 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 341192] Moving messages does not synchronize to disk
https://bugs.kde.org/show_bug.cgi?id=341192 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com Component|IMAP resource |Maildir Resource Assignee|chrig...@fastmail.fm|kdepim-bugs@kde.org -- You are receiving this mail because: You are on the CC list for the bug. 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 308968] certificate is not remembered
https://bugs.kde.org/show_bug.cgi?id=308968 Christian Trippe christiande...@web.de changed: What|Removed |Added CC||christiande...@web.de --- Comment #5 from Christian Trippe christiande...@web.de --- (In reply to Laurent Montel from comment #1) Get Certificate warning, ?:) I don't know how to have a certificate warning :) If you have a self-signed certificate. See bug 233628 which claims to have this fixed in kio but I still have the problem with mail form KDE 4.14 -- 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 340614] assertion failure in KIMAP::ImapInterval::setBegin
https://bugs.kde.org/show_bug.cgi?id=340614 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com --- Comment #8 from Christian Mollekopf mollek...@kolabsys.com --- As pointed out by christophe, fixed in af03ba2b. -- 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 340622] New: IMAP Requests should be split if they get too large
https://bugs.kde.org/show_bug.cgi?id=340622 Bug ID: 340622 Summary: IMAP Requests should be split if they get too large Product: Akonadi Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: mollek...@kolabsys.com CC: kdepim-bugs@kde.org, vkra...@kde.org Useful information by Jan Kundrat: A client should limit the length of the command lines it generates to approximately 1000 octets (including all quoted strings but not including literals). If the client is unable to group things into ranges so that the command line is within that length, it should split the request into multiple commands. -- http://tools.ietf.org/html/rfc2683#section-3.2.1.5 This got recently upgraded on QRESYNC-compliant servers to read: a client should limit the length of the command lines it generates to approximately 8192 octets (including all quoted strings but not including literals) https://tools.ietf.org/html/rfc7162#section-4 As a random data point, Trojita doesn't attempt to do these bits. At the same time, we do use the UID ranges pretty heavily, so that the numbers often go out as e.g. 100:200. As a first step we could ensure that intervals are always compressed. This doesn't always happen as we can i.e. see in BUG 332323 for UID STORE \Deleted (mass message removal). -- 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 340622] IMAP Requests should be split if they get too large
https://bugs.kde.org/show_bug.cgi?id=340622 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- 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 332323] Error in IMAP command UID: Too long argument
https://bugs.kde.org/show_bug.cgi?id=332323 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com --- Comment #3 from Christian Mollekopf mollek...@kolabsys.com --- Thanks for the report, I'll track this in a separate ticket. *** This bug has been marked as a duplicate of bug 340622 *** -- 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 340622] IMAP Requests should be split if they get too large
https://bugs.kde.org/show_bug.cgi?id=340622 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||m...@apache.org --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- *** Bug 332323 has been marked as a duplicate of this bug. *** -- 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 339393] Akonadi fail to fetch IMAP folder content with over 100MiB of messages (akonadi try to fetch too many UIDs at once)
https://bugs.kde.org/show_bug.cgi?id=339393 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com -- 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 333762] Certificate dialog loops
https://bugs.kde.org/show_bug.cgi?id=333762 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- 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 340622] IMAP Requests should be split if they get too large
https://bugs.kde.org/show_bug.cgi?id=340622 --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- In theory, UID ranges work nicely but in practice, they only work if you don't delete emails. You can still use them as the server is required to ignore any UIDs not present at the server. I.e. you delete five adjacent e-mails with UID 123, 160, 177, 190 and 205, you can do that via 123:205. Yes, doing this requires extra intelligence at a wrong layer, so there are not that many benefits in doing it. = We can probably compress the ranges even more if we know that certain uid's are not available on the server. -- 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 340614] assertion failure in KIMAP::ImapInterval::setBegin
https://bugs.kde.org/show_bug.cgi?id=340614 --- Comment #11 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to RJVB from comment #10) PS: wouldn't it be of interest to know why this issue was triggered on a GMail imap account, which AFAIK no longer provides Exchange features? The codepath is not exchange specific, it's just that the chunking is not actually used if it's not exchange (one large chunk). It would still hit the error after the first chunk though. The only thing that is a bit strange is that the error should be hit every time, meaning it should have shown up during testing? -- 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 340052] New: akonadi lockup on sync 'trash' (sqlite backend)
https://bugs.kde.org/show_bug.cgi?id=340052 Bug ID: 340052 Summary: akonadi lockup on sync 'trash' (sqlite backend) Product: Akonadi Version: 1.13.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: wildc...@tzi.org Dear developers, a while back I reported a bug (https://bugs.kde.org/show_bug.cgi?id=337366) concerning lock-ups in the akonadi server. After switching to the QSQLITE driver, as suggested in the comments, everything worked fine. Now I upgraded to KDE 4.14 / akonadi-runtime 1.13.0 and the server locks up again. However, the symptoms are quite different from what I reported in the previous bug report (so I am not sure if this bug reported is related the old report, I am still using the QSQLITE driver according to my akonadiserverrc). This time, akonadi / kontakt only locks up when trying to sync trash folders (as far as I can tell) and only if the folders contains more than XXX number of mails and/or YYY number of unread mails. Today, XXX was about 400 and YYY was about 240. I have mailing list folders containing many more mails than this (a few thousand) but generally less unread mails, except one containing about 550 unread mails and 4000 mails in total but these folders work fine. The main difference is that mails in the mailing list folders are automatically moved to these folders by the mail server, not akonadi / kontakt. Compared to last time when shutting down akonadi took 20 or more seconds, this time akonadi shuts down immediately (within two or three seconds) when using `akonadictl stop`. But akonadi / kontakt locks up as soon as the trash folder is accessed either by selecting it manually, or by moving mails to that folder. Also, it doesn't matter how long akonadi / kontakt was running before the lock-ups as compared to the previous bug report. When I empty the trash folder using the web interface of the mail server then akonadi / kontakt work fine until the trash folder fills up again. This has happened two or three times before on both configured IMAP accounts and emptying the trash folders always helped. This problem started when updating to 4.14.0. Currently, I run 4.14.2 and I still have the problem. On my laptop I am still running 4.13.x I don't have this problem connecting to the same IMAP servers, using the same settings while the trash folders are filled up. I didn't notice anything of particular interest in the akonadi / kontakt output when starting the programs from the command line. Platform: opensuse 13.1 using the KDE stable build service Software versions: akonadi-4.14.2-1.1.x86_64 akonadi-runtime-1.13.0-1.1.x86_64 baloo-pim-4.14.1-2.1.x86_64 kdepim4-4.14.2-1.1.x86_64 kdepim4-runtime-4.14.2-1.1.x86_64 kdepimlibs4-4.14.2-1.1.x86_64 libakonadi4-4.14.2-1.1.x86_64 libakonadiprotocolinternals1-1.13.0-1.1.x86_64 libbaloopim4-4.14.1-2.1.x86_64 libkdepim4-4.14.2-1.1.x86_64 libkdepimlibs4-4.14.2-1.1.x86_64 libkdepimlibs4-devel-4.14.2-1.1.x86_64 Reproducible: Only if thrash folders contain a few hundred (unread) mails. Steps to Reproduce: 1. normally use kmail / akonadi 2. delete unread mails that pile up in the trash folder Actual Results: At some point akonadi / kmail locks up when trying to sync trash folders. Expected Results: Trash folder will be synced -- 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 340015] Filter rules no longer matching after upgrade
https://bugs.kde.org/show_bug.cgi?id=340015 Christian Trippe christiande...@web.de changed: What|Removed |Added CC||christiande...@web.de --- Comment #1 from Christian Trippe christiande...@web.de --- I can confirm this also for a pop3 setup. -- 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 339687] New: Asks 4 times for password when decrypting GPG symmetric messages
https://bugs.kde.org/show_bug.cgi?id=339687 Bug ID: 339687 Summary: Asks 4 times for password when decrypting GPG symmetric messages Product: kmail2 Version: 4.11.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: cnngime...@gmail.com I use symmetric encryption with GPG to encrypt my mails to specific senders by using the gpg konsole command. Kmail understand it so well (and I thank you for your work on that!) that search for the tipical encripted region and ask me the password. I tipe it once, KMail shows me the region with the original (decripted) text, but then ask me for the password twice. After the second time, if I clicked cancel then it replace the region with couldn't decipher message. So, for no reason, KMail asks for the GPG region more than once despite you write it correctly. This behaviour is anoying. I tried to disable the try to decipher message automaticaly when previewing option at the Configure dialog box (Preferences Configure KMail Security panel (Encripted messages section)) but with no effect. Reproducible: Always Steps to Reproduce: 1. Encript a message with a symmetric algorithm and with ASCII armor (for example, executing: gpg --cipher-algo AES256 -a -c at the terminal). 2. Paste the encripted message into an email and send it to yourself. 3. Recieve the encripted mail and clic to preview it. Actual Results: KMail will ask you for the password four times... So anoying! Expected Results: If the option try to decipher message automaticaly when previewing is on KMail should ask for the password just once when previewing. Else, KMail should not ask you for the password and instead a link or button decipher message should appear. -- 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 335776] IMAP agent crashes frequently
https://bugs.kde.org/show_bug.cgi?id=335776 --- Comment #6 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to Daniel Vrátil from comment #5) I discovered one of the possible causes of the crash: In ItemSync, when the ItemCreateJob fails, the TransactionSequence is rolled back and ItemSync emits finished() - to which ResourceBase reacts by marking the task as done and scheduling another task. However the BatchFetcher in IMAP resource is not aware of this and keeps feeding more items through ResourceBase::itemsRetrieved() - which eventually hits the assert in ResourceBase, because ResourceBase has already moved on to another non-sync task. Interesting, I actually checked this codepath and though it's fine. ItemSync::slotResult is supposed to handle this case by silently ignoring errors and continuing anyways. I take that somehow doesn't work then? Not sure how to solve this - ItemSync is internal to ResourceBase, so there's no way how to tell resource implementation that ItemSync has failed and so that they should stop sending more items. Just as we can ask for more items, we should also be able to signal that the task was aborted. But it's in any case a mess to pass this through the current API, so I'd prefer to postpone that for a new API. Good-enough fix would probably be to make TransactionSequence in ItemSync to ignore ItemCreateJob failures and handle the error manually (somehow) and continue, or just abort, but let the caller to feed ItemSync all its items (just do nothing with them) and then terminate - i.e. prevent ItemSync for ever aborting prematurely. Proper fix would be to make Sync a cancellable operation, so that we can tell resource to stop feeding ResourceBase with items because there was an error. I'm for simply continuing with the sync. Regarding the reasons for ItemCreateJob failure: in my case this was happening because somehow I had two items with the same RID in one Collection (probably the RID wasn't reset during MOVE or something), so MERGE handler will abort with Multiple merge candidates error and so the ItemCreateJob fails. Something to investigate. -- 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 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kdep ||im-runtime/ff02785839e9b41b ||587fac5ca9bc2768a2729eec Resolution|--- |FIXED --- Comment #69 from Christian Mollekopf chrig...@fastmail.fm --- Git commit ff02785839e9b41b587fac5ca9bc2768a2729eec by Christian Mollekopf. Committed on 10/09/2014 at 08:21. Pushed by cmollekopf into branch 'KDE/4.14'. IMAP-Resource: Detect invalid UIDNEXT values and fall-back to sequence number based fetches. We run into this codepath with courier imap. M +7-0resources/imap/batchfetcher.cpp M +35 -11 resources/imap/retrieveitemstask.cpp M +36 -1resources/imap/tests/testretrieveitemstask.cpp http://commits.kde.org/kdepim-runtime/ff02785839e9b41b587fac5ca9bc2768a2729eec -- 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 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #70 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to Marcel Naziri from comment #67) (In reply to Christian Mollekopf from comment #65) A proper fix would be to implement the STATUS command. I won't do that but you're welcome to supply patches. After reading in RFC 3501 about the STATUS command I doubt that it would be the right way. :( It says that STATUS should not be used on the currently selected mailbox. This could be worked around by deselecting first. Also this command can be quite slow. Yeah, I guess it depends on the definition on slow. If you want something fast you better use another IMAP server. On the other hand I found by chatting with a Courier IMAP server via netcat that the STATUS result values like MESSAGES, RECENT, UIDNEXT, UIDVALIDITY and UNSEEN are only updated if prior to this a SELECT or EXAMINE command was executed. So Courier seems not to be conform to the RFC. Indeed, but in that case we could run STATUS after a SELECT that didn't return UIDNEXT. Anways, I'm not going to work on this any further. -- 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 335776] IMAP agent crashes frequently
https://bugs.kde.org/show_bug.cgi?id=335776 --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- dfaure reported a disconnect just before a similar crash, so let's assume that's the cause. This happens due to the CollectionFetchJob that is not aborted on disconnect, so we need to fix that. -- 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 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #72 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to Rigo Wenning from comment #71) (In reply to Christian Mollekopf from comment #70) Christian, if I change to another imap-server than Courier, the performance improvements would still work, right? You haven't just reverted to the 4.13.3 state, I hope. No, I simply added an additional codepath that is only used if UIDNEXT is not delivered on SELECT. So other imap servers should not be affected at all by this change. -- 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 335776] IMAP agent crashes frequently
https://bugs.kde.org/show_bug.cgi?id=335776 --- Comment #3 from Christian Mollekopf mollek...@kolabsys.com --- Created attachment 88644 -- https://bugs.kde.org/attachment.cgi?id=88644action=edit debug info by dfaure I suppose this version of the crash could be explained if for some reason the the task was killed (although we don't see a disconnect), and the batchfetcher continued afterwards. I.e. the abortActivity codepath disconnects the sessions which in turns triggers cancelTask in ResourceTask (thus ending the task). However, the internal BatchFetcher job continues to run as it only get's deleted once the session is deleted. Further both the session and the task are deleted via deleteLater, meaning the BatchFetcher still gets a chance to issues a signal through the ResourceTask that then triggers itemsRetrieved (resulting in a crash since cancelTask has already been called). -- 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 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Attachment #88482|0 |1 is obsolete|| --- Comment #65 from Christian Mollekopf mollek...@kolabsys.com --- Created attachment 88636 -- https://bugs.kde.org/attachment.cgi?id=88636action=edit version 3 of patch for fallback with invalid uidnext I think this should now restore functionality as before. Can somebody try if it works? A proper fix would be to implement the STATUS command. I won't do that but you're welcome to supply patches. -- 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 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Attachment #88453|0 |1 is obsolete|| --- Comment #42 from Christian Mollekopf mollek...@kolabsys.com --- Created attachment 88482 -- https://bugs.kde.org/attachment.cgi?id=88482action=edit version 2 of patch for fallback with invalid uidnext The last patch was indeed incomplete, sorry about that. This one should do better. -- 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 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #44 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to Carsten Pfeiffer from comment #43) Thanks Christian, that one works. Great, thanks for testing. kmail shows all mails again, but everytime I switch folders, it will synchronize the entire folder. Yes, that is expected. I guess that was to be expected from the discussion here, so I hope that this is a quick fix and not the solution. I don't plan on working on this any further. It could be improved, but courier should just send UIDNEXT which is what is specified in RFC 3501 (IMAP). Note that this simply reestablishes what was done before (You just didn't have any debug messages telling you that a full sync was executed). -- 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 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #53 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to Marcel Naziri from comment #51) (In reply to Carsten Pfeiffer from comment #50) (In reply to Marcel Naziri from comment #49) Anyone tested my patch for ImapInterval in kdepimlibs? Will do so tonight or tomorrow night. Completely missed that the patch is attached. I realized that with my patch flags (e.g. read/unread) changed by another client aren't reflected in kmail when refreshing the folder. not until mailbox content is changed (new mail arrived or something moved) the flags are updated. Is this also happening with Christians patch v2? Please note that your patch is really rather a workaround that cannot be upstreamed. Thanks a lot for your analysis though as it pointed me in the right direction. What's currently missing from my patch is that we are not using the optimization that avoid downloading all messages on every sync. This is because we usually rely on a combination of message-count and uidnext to detect if new messages are available or old ones have been deleted. Whitout uidnext we could still avoid a sync if the messagecount remains the same, but then we would run into the problem that we for instance would never notice if i.e. one message has been removed and another one added (which is nasty because it's very unpredictable). -- 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 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #39 from Christian Mollekopf mollek...@kolabsys.com --- Created attachment 88453 -- https://bugs.kde.org/attachment.cgi?id=88453action=edit patch for fallback with invalid uidnext Can somebody try this patch for kdepim-runtime? -- 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 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #27 from Christian Mollekopf mollek...@kolabsys.com --- So kdepim-runtime seems to be affected. RetrieveItemsTask::onFinalSelectDone gets -1 values for nextUid which are not correctly mapped to an IMAP interval like 1:* instead it results in 1:-1 That does sound like a server bug, or at least I don't know when UIDNEXT 0 would make any sense. I suppose we can catch this case and just fallback a very large UIDNEXT value. Can other's confirm this is indeed the problem? -- 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 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #16 from Christian Mollekopf mollek...@kolabsys.com --- We'll need an imap log (https://techbase.kde.org/Projects/PIM/Akonadi/Debug_IMAP) and what imap server this is failing with. -- 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 335795] IMAP namespace support is incomplete/insufficient on large imap accounts
https://bugs.kde.org/show_bug.cgi?id=335795 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com Resolution|--- |WONTFIX --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- subscriptions allow you to not download what you don't want. I disagree that specifing a prefix path adds anything useful. Therefore I have to close this, sorry. Thanks for the elaborate suggestion though (no irony intended). -- 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 319776] Akonadi crashed, possibly because of sudden lack of network connection, caused by the laptop going into suspend-to-ram
https://bugs.kde.org/show_bug.cgi?id=319776 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||mollek...@kolabsys.com --- Comment #19 from Christian Mollekopf mollek...@kolabsys.com --- I just ran into this again after resuming from suspend. Can't really explain what's happending though. akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection christian.mollekopfatgmail.com/Be[156/47975] parent (christian.mollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection christian.mollekopfatgmail.com/Reisen with parent (christian.mollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Archive with parent (cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/INBOX with parent ( cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Personal with parent (cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Receipts with parent (cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Sent with parent ( cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Trash with parent ( cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Travel with parent (cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Work with parent ( cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection new folder with parent () akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection outbox with parent () akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection sent-mail with parent () akonadi_kolab_resource_2(9740)/libakonadi Akonadi::CollectionSync::Private::execute: void Akonadi::CollectionSync::Private::execute() localListDo ne: false deliveryDone: true akonadi_kolab_resource_2(9740)/libakonadi Akonadi::CollectionSync::Private::execute: void Akonadi::CollectionSync::Private::execute() localListDo ne: true deliveryDone: true drkonqi(18437) KCrashBackend::stopAttachedProcess: Sending SIGSTOP to process akonadi_kolab_resource_2(9740)/kdepimlibs (kimap) KIMAP::SessionThread::doCloseSocket: close drkonqi(18437) KCrashBackend::continueAttachedProcess: Sending SIGCONT to process QSocketNotifier: Invalid socket 10 and type 'Read', disabling... The crash can be reproduced sometimes. -- Backtrace: Application: IMAP Account 12 of type Kolab Groupware Server (akonadi_kolab_resource), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. 81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fa6f84018c0 (LWP 9739))] Thread 2 (Thread 0x7fa6ec08d700 (LWP 18418)): #0 0x0034ef0ea9dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x0034f20495b4 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7fa6e400e990, timeout=-1, context=0x7fa6e401b420) at gmain.c:4007 #2 g_main_context_iterate (context=context@entry=0x7fa6e401b420, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3708 #3 0x0034f20496dc in g_main_context_iteration (context=0x7fa6e401b420, may_block=1) at gmain.c:3774 #4 0x0034afdb5af6 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #5 0x0034afd8595f in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #6 0x0034afd85cad in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #7 0x0034afc79e8f in QThread::exec() () from /lib64/libQtCore.so.4 #8 0x0034afc7c6bf in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #9 0x0034ef807f33 in start_thread (arg=0x7fa6ec08d700) at pthread_create.c:309 #10 0x0034ef0f4ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7fa6f84018c0 (LWP 9739)): [KCrash Handler] #6 0x0001
[Akonadi] [Bug 319776] Akonadi crashed, possibly because of sudden lack of network connection, caused by the laptop going into suspend-to-ram
https://bugs.kde.org/show_bug.cgi?id=319776 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|REOPENED|CONFIRMED Platform|Ubuntu Packages |Compiled Sources Version|4.10|GIT (master) -- 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 319776] Akonadi crashed, possibly because of sudden lack of network connection, caused by the laptop going into suspend-to-ram
https://bugs.kde.org/show_bug.cgi?id=319776 --- Comment #20 from Christian Mollekopf mollek...@kolabsys.com --- That was the wrong console output... akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::SessionPrivate::responseReceived: Received BYE: idle for too long akonadi_kolab_resource_11(9739) ImapResourceBase::doSetOnline: online= false akonadi_kolab_resource_11(9739) ImapResourceBase::doSetOnline: online= true akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::SessionThread::doCloseSocket: close akonadi_kolab_resource_11(9739)/kdeui (Wallet) KWallet::Wallet::openWallet: Pass a valid window to KWallet::Wallet::openWallet(). kwalletd(9040)/kdeui (Wallet) KWalletD::openAsync: openAsync for :1.1163 klauncher(9023)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from /var/tmp/kdesycoca-custom klauncher(9023)/kio (KLauncher) KLauncher::processRequestReturn: /usr/bin/kwalletmanager (pid 18048) up and running. akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::LoginJob: KIMAP::LoginJob(0x248b280) akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::SessionThread::reconnect: connectToHost 192.168.122.10 993 akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::doStart: KIMAP::LoginJob(0x248b280) akonadi_kolab_resource_11(9739)/kssl KTcpSocket::showSslErrors: The host name did not match any of the valid hosts for this certificate akonadi_kolab_resource_11(9739)/kssl KTcpSocket::showSslErrors: The certificate is self-signed, and untrusted akonadi_kolab_resource_11(9739)/kssl KTcpSocket::showSslErrors: The certificate has expired akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::SessionThread::sslConnected: Initial SSL handshake failed. cipher.isNull() is false , cipher.usedBits() is 256 , the socket says: Unknown error and the list of SSL errors contains 3 items. akonadi_kolab_resource_11(9739)/kssl KIO::SslUi::askIgnoreSslErrors: Error list empty after removing errors to be ignored. Continuing. kwalletmanager(18050)/kdeui (KNotification) KStatusNotifierItemDBus::KStatusNotifierItemDBus: service is org.kde.StatusNotifierItem-18050-1 akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::handleResponse: Capability * akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::handleResponse: Capabilities updated: (IMAP4rev1, LITERAL+, ID, ENABLE, ACL, RIGHTS=kxte, QUOTA, MAILBOX-REFERRALS, NAMESPACE, UIDPLUS, NO_ATOMIC_RENAME, UNSELECT, CHILDREN, MULTIAPPEND, BINARY, CATENATE, CONDSTORE, ESEARCH, SORT, SORT=MODSEQ, SORT=DISPLAY, THREAD=ORDEREDSUBJECT, THREAD=REFERENCES, ANNOTATEMORE, LIST-EXTENDED, WITHIN, QRESYNC, SCAN, XLIST, URLAUTH, URLAUTH=BINARY, X-NETSCAPE, AUTH=PLAIN, AUTH=LOGIN, SASL-IR, COMPRESS=DEFLATE, IDLE) akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::handleResponse: Capability A01 akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::handleResponse: Login A02 akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::~LoginJob: KIMAP::LoginJob(0x248b280) akonadi_kolab_resource_11(9739) ImapResourceBase::doSetOnline: online= true akonadi_kolab_resource_11(9739)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection INBOX with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Arbeit with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Belege with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Calendar with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Configuration with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Contacts with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Default List with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Drafts with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Freebusy with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Journal with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Mobile List with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Notes with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Privat with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Reisen
[Akonadi] [Bug 335795] IMAP namespace support is incomplete/insufficient on large imap accounts
https://bugs.kde.org/show_bug.cgi?id=335795 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to RJVB from comment #2) Have you actually tried to use subscriptions in a use case like the one I described? Your claim about subscriptions is true only in theory, in practice one has to wait longer for a possibility to subscribe to only the desired mailboxes than it takes to decide to install another email client, install, configure and start using it. Much longer. Erm, what? So is the problem that the syncing starts before you have the chance to adjust subscriptions? If that is so, you have an entierly valid point, and we can fix it whenever I get around to it. Please open an according bugreport in that case. We could also add the subscription dialog as part of the setup-dialog, which would probably improve the visibility of the feature (I know the subscription support in the UI is currently pretty bad, and I'm already working on that). So yeah, if speed and ease of use (= not having to subscribe to ALL folders inside/under the mailbox repository folder) aren't useful then I guess the majority of other readers that do provide a prefix path setting are just plain wrong to do so. No irony intended either (sarcasm and cynicism are a different matter) ... I pretty sure subscriptions do in fact solve the problem. It's entierly possible that the implementation isn't perfect and that it requires some adjustments, but that's the solution then, and not adding yet another workaround. BTW, nothing has been resolved here, so I'm setting a more appropriate status. Please don't. I'm the one that has to deal with the tickets, and it helps noone keeping a tickets open that has been declined already. There is only Resolved and if you set it back to unconfirmed there is no way for me to distinguish it from other tickets that I haven't processed yet. Even if it's set to resolved we can keep the discussion going here if you like. -- 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 337744] New: Subscriptions should be configurable before the first sync
https://bugs.kde.org/show_bug.cgi?id=337744 Bug ID: 337744 Summary: Subscriptions should be configurable before the first sync Product: Akonadi Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: mollek...@kolabsys.com CC: kdepim-bugs@kde.org, vkra...@kde.org Otherwise the sync potentially starts downloading loads of data no one needs. -- 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 335795] IMAP namespace support is incomplete/insufficient on large imap accounts
https://bugs.kde.org/show_bug.cgi?id=335795 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #5 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to RJVB from comment #4) Yes, there are 2 things which make (made) the current implementation unworkable for me. Most importantly, the fact that there is no way to obtain the list of folders (not) to subscribe to before the whole account is scanned. (And again, on a typical workstation also running an imapd that amounts to transferring all files under your account, possibly even trying to parse them.) Agreed, it should be possible to make that selection before the sync starts. https://bugs.kde.org/show_bug.cgi?id=337744 The other thing is that there is nothing recursive to a subscription, i.e. there is no way I found to select all mailboxes in the directory where one keeps them. It would be nice if the UI allowed recursive actions indeed. I'm aware the UI side isn't pretty in general, and I plan to improve that. One could argue that that's a once-only action, but in reality that would go against the fact that IMAP has always been designed to allow access from multiple locations (i.e., mailboxes might be created or deleted while connecting from a different location). I don't get that part. Server-side subscriptions are for all devices which you may or may not desire, but we allow to override that setting on a per-folder basis using local subscriptions, which should cover all use-cases, no? Isn't there a closed - wontfix status? Indeed there is, once the status was resolved (it's a workflow thingy I suppose...). -- 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 319776] Akonadi crashed, possibly because of sudden lack of network connection, caused by the laptop going into suspend-to-ram
https://bugs.kde.org/show_bug.cgi?id=319776 --- Comment #21 from Christian Mollekopf mollek...@kolabsys.com --- It crashes in qobject on: const QMetaObject *smeta = sender-metaObject(); so it's indeed the session that is invalid. -- 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 337366] akonadi sqlite lockup when checking imap resources
https://bugs.kde.org/show_bug.cgi?id=337366 --- Comment #3 from Christian Quast wildc...@tzi.org --- I've been using the QSQLITE driver for almost four days now and I didn't need to restart akonadi during this time. It seems as if the problems have been solved. thanks... -- 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 337366] akonadi sqlite lockup when checking imap resources
https://bugs.kde.org/show_bug.cgi?id=337366 --- Comment #2 from Christian Quast wildc...@tzi.org --- I just switched over to the QSQLITE driver as suggested. Lets see... I'll report back on failure or success. -- 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 292399] Kmail message list does not show attachment icons
https://bugs.kde.org/show_bug.cgi?id=292399 Christian Hille li...@hillux.de changed: What|Removed |Added CC||li...@hillux.de -- 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 292399] Kmail message list does not show attachment icons
https://bugs.kde.org/show_bug.cgi?id=292399 --- Comment #26 from Christian Hille li...@hillux.de --- Can confirm the error. Inbox messages have no icon for attachments. K-Mail is not suitable for professional use with this error. -- 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 337366] New: akonadi sqlite lockup when checking imap resources
https://bugs.kde.org/show_bug.cgi?id=337366 Bug ID: 337366 Summary: akonadi sqlite lockup when checking imap resources Classification: Unclassified Product: Akonadi Version: 4.13 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: wildc...@tzi.org Since upgrading to 4.13 I am experiencing lockup problems using akonadi's sqlite backend. At a random point after starting akonadi / kontact, akonadi gets stuck when syncing folders or retrieving mails. The process list in kontact (status bar lower right side) shows something like syncing folder XXX %Y but it stays at Y%. At that point a cannot access any mails, calendar items, or contacts. Running akonadi from console I get a debug message: [QSQLITE3: 140502062065408] sqlite3_blocking_step: Entering while loop Searching for this on the Internet I'll find among other things a commit message removing the code to print this message: http://permalink.gmane.org/gmane.comp.kde.cvs/1316401 (message date Apr. 6 2014 - Enable concurrency in our copy of QSQLITE driver) and other links pointing to older(?) versions (ie. 1.3.90) of akonadi where the code seems to active. After restarting akonadi (`akonadictl stop`, wait until akonadi server exits which takes a 20 seconds or so and then `akonadictl start`) everything works find for a while - sometimes a could of hours up to a day. I found a similar bug report from Nov. 2012 which might be related but in my case everything works fine until a certain point (not gettings stuck in init). Also, I am able to normal close the applications and stop akonadi (which takes some time though): https://bugs.kde.org/show_bug.cgi?id=310652 Maybe of interest: I have to IMAP accounts set-up and two DavCal Groupware resources (a total of 3 address books + 1 calendar / 1 task imported from the first resource, and 6 calendars / 6 tasks imported from the second source). Platform: opensuse 13.1 using the KDE stable build service Software versions: akonadi-4.13.2-10.1.x86_64 plasma-addons-akonadi-4.13.2-4.1.x86_64 python-kde4-akonadi-4.13.2-4.2.x86_64 libakonadiprotocolinternals1-1.12.1-3.1.x86_64 akonadi-runtime-1.12.1-3.1.x86_64 libakonadi4-4.13.2-4.1.x86_64 kontact-4.13.2-10.1.x86_64 kmail-4.13.2-10.1.x86_64 PS: I cannot simply switch to other backends as I am running akonadi / kontact on a thin client set-up (SunRays) host multiple users and starting a database server on such a system wouldn't be my first choice. Reproducible: Always Steps to Reproduce: 1. start akonadi and kontact 2. work normally and wait Actual Results: At some point (hours up to a day) akonadi / kontact gets stuck when trying to sync IMAP folders / mails. Expected Results: Folders / Mails will be synced -- 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 331826] Emails based on template go to local sent folder instead of that configured
https://bugs.kde.org/show_bug.cgi?id=331826 Christian A. Reiter christian.a.rei...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||christian.a.rei...@gmail.co ||m Ever confirmed|0 |1 --- Comment #1 from Christian A. Reiter christian.a.rei...@gmail.com --- Can confirm exact that behaviour. -- 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 336163] autocompletion shows multiple entries for one contact with different quotes
https://bugs.kde.org/show_bug.cgi?id=336163 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- Note that the problem is not necessarily that multiple entires are shown (as covered by 316036), but rather that entires make it into the selection that are not actually valid email addresses, causing the email to be rejected by the server. One reason is possibly faulty indexing of the addresses, perhaps there are others. In any case it probably would make sense to ensure a selected email address is valid before copying into the mail, or even hiding it completely from the selection. From the rfc excerpt I take a name has to be quoted if it contains spaces, otherwise not. So valid would be: John Doe j...@doe.com John j...@doe.com -- 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 335235] kmail akonadi: imap resource cannot be accessed
https://bugs.kde.org/show_bug.cgi?id=335235 --- Comment #5 from Christian Mollekopf mollek...@kolabsys.com --- I'm aware of the GETACL problem, because we don't respect MYRIGHTS (that's on my todolist already), but I don't understand why we're issuing MYRIGHTS if ACL's are disabled. I assume the CAPABILITIES string doesn't contain ACL? If it does that seems like a server bug. -- 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 335235] kmail akonadi: imap resource cannot be accessed
https://bugs.kde.org/show_bug.cgi?id=335235 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #3 from Christian Mollekopf mollek...@kolabsys.com --- For the Too many invalid IMAP commands. problem we would probably need a imap log. You can find here http://techbase.kde.org/Projects/PIM/Akonadi/Debug_IMAP how to obtain one. -- 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 328421] Refactor session related codepaths to use jobs
https://bugs.kde.org/show_bug.cgi?id=328421 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Priority|NOR |LO Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- 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 335776] IMAP agent crashes frequently
https://bugs.kde.org/show_bug.cgi?id=335776 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- Can you check in the debug output if the online state changed just before it crashed? You should see a message in doSetOnline (online=), -- 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 331703] Auto refresh of the IMAP email accounts no longer works
https://bugs.kde.org/show_bug.cgi?id=331703 --- Comment #7 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to comment #6) What you indicate is definitely different than my issue. But I never saw that all folders were kept in sync instantly. But maybe this is dependent on the email provider. What I see and what I also saw in 4.12 is that kmail retrieves changes on the indicated interval. IDLE is only used on the INBOX, and the interval is used for all folders. The interval is working AFAIK, and IDLE is supposed to pick up flag changes and new mail for INBOX only. -- 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 328625] Allow forcing encryption protocol version
https://bugs.kde.org/show_bug.cgi?id=328625 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |im-runtime/32aaf98fd2d7387f |im-runtime/423632618ed30781 |1313cf0d135c82dffa643d9a|7a088ae99607d19f3cce98ed --- Comment #9 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 423632618ed307817a088ae99607d19f3cce98ed by Christian Mollekopf. Committed on 07/05/2014 at 14:20. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. IMAP-Resource: Allow to override the encryption mode. Some ssl servers advertise an ssl version they don't actually support. This config-only option allows to override the used encryption mode, and supports all available options, so the auto-negotiation can be skipped. M +3-0resources/imap/imapresource.kcfg M +24 -0resources/imap/settings.cpp http://commits.kde.org/kdepim-runtime/423632618ed307817a088ae99607d19f3cce98ed -- 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 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |im-runtime/7f3e279cf79ef8e2 |im-runtime/7802a783189adbe4 |4eb64986d538e0075452b91c|e3e67cd9bb60867c82c36d69 --- Comment #13 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 7802a783189adbe4e3e67cd9bb60867c82c36d69 by Christian Mollekopf. Committed on 05/05/2014 at 21:10. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. IMAP-Resource: Check available UID's first retrieve 50 time more flags. This way we avoid the UID fragmentation problem (we try to fetch a lot of messages that are not available on the server). It's also a nice first step towards only syncing a certain time-frame. Retrieving 50 times more flags than full messages should still result in low memory consumption while greatly reducing roundtrips. M +68 -33 resources/imap/retrieveitemstask.cpp M +49 -25 resources/imap/tests/testretrieveitemstask.cpp http://commits.kde.org/kdepim-runtime/7802a783189adbe4e3e67cd9bb60867c82c36d69 -- 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 329805] After disabling all local subscriptions and restarting kmail akonadi_imap_resource always crashes
https://bugs.kde.org/show_bug.cgi?id=329805 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |im-runtime/e376267dda6972ff |im-runtime/5e8808a6e2eb7171 |c2eeea215901f08145e3c993|b8aafeeb0f553a8e89ae3a8f --- Comment #4 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 5e8808a6e2eb7171b8aafeeb0f553a8e89ae3a8f by Christian Mollekopf. Committed on 08/05/2014 at 15:18. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. IMAP-Resource: Don't crash if IDLE collection is not subscribed locally. M +12 -11 resources/imap/imapresource.cpp http://commits.kde.org/kdepim-runtime/5e8808a6e2eb7171b8aafeeb0f553a8e89ae3a8f -- 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 334218] synchronizations of large folders with filesystem contents hogs a Sandybridge core for minutes
https://bugs.kde.org/show_bug.cgi?id=334218 --- Comment #16 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 1af2704a63c6641867eaf2b67976f5309a994cca by Christian Mollekopf, on behalf of Martin Steigerwald. Committed on 03/05/2014 at 14:52. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. Do not sort the directory entry list in listNew() and listCurrent(): According to callgrind dumps at https://bugs.kde.org/show_bug.cgi?id=334218#c4 QDir sorts the list of directory entries unless specified otherwise. After disabling the sorting the callgrind is quite different already: https://bugs.kde.org/show_bug.cgi?id=334218#c7 This already helps shortening the time to synchronize folders visibly, but KMail gets still blocked for half a minute or more. There is another occurence of QDir entry sorting in keycache.cpp which the next commit will address. Thanks to Sergio and David for help and pointing out how to disable the sorting. REVIEW: 117975 DIGEST: Huge performance improvement for POP3 users with large maildir. M +2-0resources/maildir/libmaildir/maildir.cpp http://commits.kde.org/kdepim-runtime/1af2704a63c6641867eaf2b67976f5309a994cca -- 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 334218] synchronizations of large folders with filesystem contents hogs a Sandybridge core for minutes
https://bugs.kde.org/show_bug.cgi?id=334218 --- Comment #17 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 81f30e18c975f9cc44da7c904ed612df804200da by Christian Mollekopf, on behalf of Martin Steigerwald. Committed on 03/05/2014 at 14:53. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. Also do not sort directory entries in listCurrent and listNew in key cache: QDir sorts the list of directory entries unless specified otherwise. The last commit already disabled the sorting in maildir.cpp. This commit completes the work and makes the remaining sorting calls in the callgrind dumps at https://bugs.kde.org/show_bug.cgi?id=334218#c7 go away completely as demonstrated in the callgrind dumps at: https://bugs.kde.org/show_bug.cgi?id=334218#c12 Subjectively this has a huge impact on the performance of KMail with huge maildir. KMail hardly blocks anymore on folder changes and feels much more responsive now. Akonadi maildir resource went from hogging a Sandy Bridge core for minutes to not appearing using 100% of one core in even one averaged 10 second interval in atop. I hardly see it in atop at all anymore, except when accessing very large folders such as one with Linux Kernel mailing list and more than 245000 unread mails. Thanks to Sergio for pointing out the remaining sorting calls in the second callgrind dump and for help. Now the bottleneck appears to be MaildirResource::listRecursive but I do not know whether further optimization is necessary at this point. Both changes tested with kdepimlibs master as of today and KMail 4.12.4 from Debian unstable packages with an enormous maildir including a folder for Linux Kernel mailing list with more than 245000 unread mails. REVIEW: 117975 DIGEST: Huge performance improvement for POP3 users with large maildirs. M +2-0resources/maildir/libmaildir/keycache.cpp http://commits.kde.org/kdepim-runtime/81f30e18c975f9cc44da7c904ed612df804200da -- 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 334448] imap stuck on Retrieving extra folder information for some folders.
https://bugs.kde.org/show_bug.cgi?id=334448 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |im-runtime/c876ae9e9ea92f2f |im-runtime/9442452028441736 |61d127899272cda3ab478770|6159ea8e358a9e7eb0ee5d5f --- Comment #2 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 94424520284417366159ea8e358a9e7eb0ee5d5f by Christian Mollekopf. Committed on 07/05/2014 at 12:04. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. IMAP-Resource: Properly count started and completed jobs. I.e. if no job was started because of no metadata capabilities the job would get stuck otherwise. M +14 -7resources/imap/retrievecollectionmetadatatask.cpp http://commits.kde.org/kdepim-runtime/94424520284417366159ea8e358a9e7eb0ee5d5f -- 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 334269] Email retrieval comes to a full HALT after BatchFetcher::fetchNextBatch: fetchNextBatch called while fetch is in process error
https://bugs.kde.org/show_bug.cgi?id=334269 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |im-runtime/c8763c863111afe9 |im-runtime/0de7f0faef78b570 |9cda997bb9ca7e481d0e5142|b3930ec34f0320de7f2f055b --- Comment #6 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 0de7f0faef78b570b3930ec34f0320de7f2f055b by Christian Mollekopf. Committed on 04/05/2014 at 19:29. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. IMAP-Resource: Fixed stuck BatchFetcher The continuation request can be delivered while a fetch job is in progress if we deliver too many messages (which is likely with the uid based fetches where we can't predict the exact amount of fetched messages). In this case we need to remember the continuation request, and automatically proceed. This causes m_fetchedItemsInCurrentBatch to be off by the messages we delivered too many, but that's not a problem as it means we just deliver too many messages during every batch. M +11 -1resources/imap/retrieveitemstask.cpp http://commits.kde.org/kdepim-runtime/0de7f0faef78b570b3930ec34f0320de7f2f055b -- 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
