[kmail2] [Bug 323911] New: Failure when closing kmail
https://bugs.kde.org/show_bug.cgi?id=323911 Bug ID: 323911 Summary: Failure when closing kmail Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: hugo_m...@online.ms Application: kmail (4.10.5) KDE Platform Version: 4.10.5 release 1 Qt Version: 4.8.4 Operating System: Linux 3.7.10-1.16-default x86_64 Distribution: openSUSE 12.3 (x86_64) -- Information about the crash: - What I was doing when the application crashed: I worked with kmail. Clicking on the the top right button to close the window I get the error report screen. This happened yesterday and now. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f43266cf780 (LWP 2630))] Thread 4 (Thread 0x7f43075c4700 (LWP 2635)): #0 0x7f432184c964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4316fc27c7 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f4316fc27f9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f4321848e0f in start_thread () from /lib64/libpthread.so.0 #4 0x7f4323a1b7dd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f4306cbb700 (LWP 2636)): #0 0x7f4323a1287d in poll () from /lib64/libc.so.6 #1 0x7f431bc89aa4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f431bc89bc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f43243a92e6 in QEventDispatcherGlib::processEvents (this=0x7f4308c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f4324379adf in QEventLoop::processEvents (this=this@entry=0x7f4306cbae00, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f4324379d68 in QEventLoop::exec (this=0x7f4306cbae00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f432427c0f0 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #7 0x7f432427f0cc in QThreadPrivate::start (arg=0xd2dbd0) at thread/qthread_unix.cpp:338 #8 0x7f4321848e0f in start_thread () from /lib64/libpthread.so.0 #9 0x7f4323a1b7dd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f42bf97a700 (LWP )): [KCrash Handler] #5 lockInline (this=0x40) at /usr/include/QtCore/qmutex.h:187 #6 QMutexLocker (m=0x40, this=synthetic pointer) at /usr/include/QtCore/qmutex.h:109 #7 Nepomuk2::ResourceData::load (this=this@entry=0x0) at /usr/src/debug/nepomuk-core-4.10.5/libnepomukcore/resource/resourcedata.cpp:345 #8 0x7f431c271f2e in Nepomuk2::ResourceData::property (this=0x0, uri=...) at /usr/src/debug/nepomuk-core-4.10.5/libnepomukcore/resource/resourcedata.cpp:238 #9 0x7f431c2829b3 in Nepomuk2::Resource::property (this=0x7f42bf979d90, uri=...) at /usr/src/debug/nepomuk-core-4.10.5/libnepomukcore/resource/resource.cpp:226 #10 0x7f431fb00eb2 in MessageCore::NepomukResourceRetrieverRunnable::run (this=0x1e3cc60) at /usr/src/debug/kdepim-4.10.5/messagecore/asyncnepomukresourceretriever.cpp:49 #11 0x7f4324272c9d in QThreadPoolThread::run (this=0x18ddb50) at concurrent/qthreadpool.cpp:107 #12 0x7f432427f0cc in QThreadPrivate::start (arg=0x18ddb50) at thread/qthread_unix.cpp:338 #13 0x7f4321848e0f in start_thread () from /lib64/libpthread.so.0 #14 0x7f4323a1b7dd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f43266cf780 (LWP 2630)): #0 0x7f432184c964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f432427f62b in wait (time=18446744073709551615, this=0x226eeb0) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=optimized out, mutex=0x1791b78, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f432427246f in QThreadPoolPrivate::waitForDone (this=0x1791af0, msecs=msecs@entry=-1) at concurrent/qthreadpool.cpp:298 #4 0x7f4324273f1d in QThreadPool::~QThreadPool (this=0x1791908, __in_chrg=optimized out) at concurrent/qthreadpool.cpp:440 #5 0x7f431faff9f1 in ~AsyncNepomukResourceRetrieverPrivate (this=0x1791900, __in_chrg=optimized out) at /usr/src/debug/kdepim-4.10.5/messagecore/asyncnepomukresourceretriever.cpp:60 #6 MessageCore::AsyncNepomukResourceRetriever::~AsyncNepomukResourceRetriever (this=0x182a160, __in_chrg=optimized out) at /usr/src/debug/kdepim-4.10.5/messagecore/asyncnepomukresourceretriever.cpp:125 #7 0x7f431f5176a2 in ~CallbackNepomukResourceRetriever (this=0x182a160, __in_chrg=optimized out) at /usr/src/debug/kdepim-4.10.5/messagelist/core/callbacknepomukresourceretriever.h:32 #8 MessageList::CallbackNepomukResourceRetriever::~CallbackNepomukResourceRetriever
[kmail2] [Bug 323911] Failure when closing kmail
https://bugs.kde.org/show_bug.cgi?id=323911 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- a lot of fixes was done in 4.11 could you retry with 4.11 ? -- 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 323872] Failure to read write-protected mbox files
https://bugs.kde.org/show_bug.cgi?id=323872 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- Will look at soon. but mixedmaildir is just for compatibility not necessary to use it for new account. -- 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 323724] Getting spammed with wrong notifications
https://bugs.kde.org/show_bug.cgi?id=323724 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org Component|general |New Mail Notifier Assignee|kdepim-bugs@kde.org |mon...@kde.org Product|kmail2 |Akonadi -- 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 215032] Smart Card - pkcs#11 Support
https://bugs.kde.org/show_bug.cgi?id=215032 Martin Bünemann mar...@buenemann.de changed: What|Removed |Added CC||mar...@buenemann.de --- Comment #4 from Martin Bünemann mar...@buenemann.de --- Leider funktionert das nicht unter Windows -- 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 323915] New: Wish: new mail notifications should indicate the account when more than one is configured
https://bugs.kde.org/show_bug.cgi?id=323915 Bug ID: 323915 Summary: Wish: new mail notifications should indicate the account when more than one is configured Classification: Unclassified Product: kmail2 Version: 4.11 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: a.b...@ukoln.ac.uk With the detailed new mail notifications, when more than one mail is received the notification says something like 2 new messages received in Inbox. When more than one account is configured, this is ambiguous. Worse, if the received mails come from more than one account, the message can appear contradictory: 2 new messages received in Inbox. One new message received in Inbox. My wish is for the message to disambiguate from which account the mails were received, when more than one account is configured. Reproducible: Always Steps to Reproduce: 1. Set up multiple email accounts 2. Enable detailed new mail notifications 3. Receive new emails from more than one account, within the same mail check Actual Results: Notification pops up with text similar to the following: 2 new messages received in Inbox. One new message received in Inbox. Expected Results: Notification pops up with text similar to the following: 2 new messages received in Inbox (Home). One new message received in Inbox (Work). Here I've suggested putting the account name in parentheses after the folder name, but you may have a better solution. -- 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 215032] Smart Card - pkcs#11 Support
https://bugs.kde.org/show_bug.cgi?id=215032 --- Comment #5 from Martin Bünemann mar...@buenemann.de --- (In reply to comment #4) Leider funktionert das nicht unter Windows Wenn ich dort auf das Kleopatrasymbol mit der re. Maustaste gehe, komme ich bis ... Zertifikat von NteKey Karte lernen. Ist hellgrau unterlegt -- 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 323916] New: Kmail Crashes when hitting cancel on PGP decrypt passphrase query
https://bugs.kde.org/show_bug.cgi?id=323916 Bug ID: 323916 Summary: Kmail Crashes when hitting cancel on PGP decrypt passphrase query Classification: Unclassified Product: kmail2 Version: 4.11 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jonathan.h...@live.de Application: kmail (4.11) KDE Platform Version: 4.11.00 Qt Version: 4.8.4 Operating System: Linux 3.8.0-29-generic x86_64 Distribution: Ubuntu 13.04 -- Information about the crash: - What I was doing when the application crashed: 1. I accidentially selected a pgp encrypted mail and kmail asked me for passphrase 2. As I didn't actually wanted to decrpyt it, I hit cancel. 3. For some reason I was asked again for passphrase, hit cancel again 4. Kmail crashed The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f6f079407c0 (LWP 22527))] Thread 5 (Thread 0x7f6ee0b66700 (LWP 22533)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6ef96f5575 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f6ef96f55c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f6f025c4f8e in start_thread (arg=0x7f6ee0b66700) at pthread_create.c:311 #4 0x7f6f04ccce1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 4 (Thread 0x7f6e9bb6f700 (LWP 22534)): #0 0x7f6f04cdb0c0 in pthread_mutex_unlock (mutex=0x7f6e94000a60) at forward.c:194 #1 0x7f6efce9c5f1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6efce5c8f3 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6efce5d0fe in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6efce5d304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6f06308036 in QEventDispatcherGlib::processEvents (this=0x7f6e940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f6f062d838f in QEventLoop::processEvents (this=this@entry=0x7f6e9bb6ed90, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f6f062d8618 in QEventLoop::exec (this=this@entry=0x7f6e9bb6ed90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f6f061da410 in QThread::exec (this=this@entry=0x1db5230) at thread/qthread.cpp:542 #9 0x7f6f062b9edf in QInotifyFileSystemWatcherEngine::run (this=0x1db5230) at io/qfilesystemwatcher_inotify.cpp:256 #10 0x7f6f061dcbec in QThreadPrivate::start (arg=0x1db5230) at thread/qthread_unix.cpp:338 #11 0x7f6f025c4f8e in start_thread (arg=0x7f6e9bb6f700) at pthread_create.c:311 #12 0x7f6f04ccce1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7f6e9aadf700 (LWP 22535)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6ef943b9f9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f6ef9723cde in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f6f025c4f8e in start_thread (arg=0x7f6e9aadf700) at pthread_create.c:311 #4 0x7f6f04ccce1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f6e9945c700 (LWP 22537)): #0 0x7f6f04cc03cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f6efce5d1dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6efce5d304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6f06308036 in QEventDispatcherGlib::processEvents (this=0x7f6e840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f6f062d838f in QEventLoop::processEvents (this=this@entry=0x7f6e9945bdc0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f6f062d8618 in QEventLoop::exec (this=this@entry=0x7f6e9945bdc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f6f061da410 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #7 0x7f6f061dcbec in QThreadPrivate::start (arg=0x1d64320) at thread/qthread_unix.cpp:338 #8 0x7f6f025c4f8e in start_thread (arg=0x7f6e9945c700) at pthread_create.c:311 #9 0x7f6f04ccce1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7f6f079407c0 (LWP 22527)): [KCrash Handler] #6 0x7f6f01a8a0c4 in KMime::Content::parent (this=this@entry=0x25cd6e0) at ../../kmime/kmime_content.cpp:953 #7 0x7f6f0118b2b6 in MessageCore::NodeHelper::nextSibling (node=node@entry=0x25cd6e0) at ../../messagecore/helpers/nodehelper.cpp:32 #8 0x7f6efe0a0786 in MessageViewer::ObjectTreeParser::parseObjectTreeInternal
[kmail2] [Bug 321089] Kmail hangs on Retrieving folder contents ... please wait
https://bugs.kde.org/show_bug.cgi?id=321089 --- Comment #5 from Dj YB yehi...@mail.ru --- I have removed the akonadi database (~/.local/share/akonadi) and things move way way faster now. my guess is my database got corrupted over the years... -- 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 323873] kmail adding new filter crashes kontact
https://bugs.kde.org/show_bug.cgi?id=323873 Jekyll Wu adap...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #5 from Jekyll Wu adap...@gmail.com --- Then close this report for now. -- 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 323872] Failure to read write-protected mbox files
https://bugs.kde.org/show_bug.cgi?id=323872 Volker Kuhlmann list0...@paradise.net.nz changed: What|Removed |Added CC||list0...@paradise.net.nz --- Comment #2 from Volker Kuhlmann list0...@paradise.net.nz --- Thanks! But especially for compatibility I would expect write-protected historic mbox files to be accessible easily. -- 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 215032] Smart Card - pkcs#11 Support
https://bugs.kde.org/show_bug.cgi?id=215032 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #6 from Laurent Montel mon...@kde.org --- (In reply to comment #5) (In reply to comment #4) Leider funktionert das nicht unter Windows Wenn ich dort auf das Kleopatrasymbol mit der re. Maustaste gehe, komme ich bis ... Zertifikat von NteKey Karte lernen. Ist hellgrau unterlegt English please -- 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
[Akonadi] [Bug 323915] Wish: new mail notifications should indicate the account when more than one is configured
https://bugs.kde.org/show_bug.cgi?id=323915 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org Component|general |New Mail Notifier Assignee|kdepim-bugs@kde.org |mon...@kde.org Product|kmail2 |Akonadi -- 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 323586] nepomuk_tag_resource crashes when switching from offline to online mode
https://bugs.kde.org/show_bug.cgi?id=323586 --- Comment #8 from Daniel Vrátil dvra...@redhat.com --- Perfect! Thank you -- 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 323911] Failure when closing kmail
https://bugs.kde.org/show_bug.cgi?id=323911 --- Comment #2 from hugo_m...@online.ms --- Ok. I will retry it. According to http://de.opensuse.org/KDE_Repositorys I could use an upstream Release: KDE SC 4.11. -- 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 323911] Failure when closing kmail
https://bugs.kde.org/show_bug.cgi?id=323911 --- Comment #3 from hugo_m...@online.ms --- Ok. I will retry it. According to http://de.opensuse.org/KDE_Repositorys I could use an upstream Release: KDE SC 4.11. -- 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 323929] New: kmail high cpu load, seems stuck looping on fetching mails from akonadi
https://bugs.kde.org/show_bug.cgi?id=323929
Bug ID: 323929
Summary: kmail high cpu load, seems stuck looping on fetching
mails from akonadi
Classification: Unclassified
Product: kmail2
Version: 4.11
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: cousinm...@gmail.com
Hi,
I have been having this problem for quite a while, in fact, but I just have
taken the time to diagnose it.
Kmail eats a lot of CPU on my machine, specifically when one account is
activated.
If I use the akonadi console, I see it doing
KMail Kernel ETM (0x104c840) * 9518 FETCH (UID 9518 REV 0 REMOTEID 3 MIMETYPE
message/rfc822 COLLECTIONID 23 SIZE 5571 FLAGS (\ANSWERED \SEEN) ANCESTORS
((23 .dlb-admin) (14 imap://marc.cou...@dalibo.com@mail.dalibo.com/) (0
)) PLD:ENVELOPE[1] {299} (Thu, 04 Oct 2012 00:34:18 +0200 Reboot
telemaque ((damien clochard NIL damien.clochard dalibo.com)) ((NIL NIL
dlb-admin-bounces listes.dalibo.com)) ((NIL NIL dlb-admin
listes.dalibo.com)) ((NIL NIL dlb-admin listes.dalibo.com)) NIL NIL NIL
506cbd6a.9010...@dalibo.com NIL))
KMail Kernel ETM (0x104c840) * 9517 FETCH (UID 9517 REV 0 REMOTEID 2 MIMETYPE
message/rfc822 COLLECTIONID 23 SIZE 7224 FLAGS (\SEEN) ANCESTORS ((23
.dlb-admin) (14 imap://marc.cou...@dalibo.com@mail.dalibo.com/) (0 ))
PLD:ENVELOPE[1] {382} (Wed, 03 Oct 2012 18:17:10 +0200 DONE : Monitorer le
yang collector ((Nicolas Thauvin NIL nicolas.thauvin dalibo.com)) ((NIL
NIL dlb-admin-bounces listes.dalibo.com)) ((NIL NIL dlb-admin
listes.dalibo.com)) ((NIL NIL dlb-admin listes.dalibo.com)) NIL NIL
506bfb16.9060...@dalibo.info 20121003181710.712f7...@dalibo.com
506bfb16.9060...@dalibo.info))
KMail Kernel ETM (0x104c840) * 9516 FETCH (UID 9516 REV 0 REMOTEID 1 MIMETYPE
message/rfc822 COLLECTIONID 23 SIZE 5486 FLAGS (\SEEN) ANCESTORS ((23
.dlb-admin) (14 imap://marc.cou...@dalibo.com@mail.dalibo.com/) (0 ))
PLD:ENVELOPE[1] {310} (Wed, 03 Oct 2012 10:45:10 +0200 TODO : Monitorer le
yang collector ((damien clochard NIL damien dalibo.info)) ((NIL NIL
dlb-admin-bounces listes.dalibo.com)) ((NIL NIL dlb-admin
listes.dalibo.com)) ((NIL NIL dlb-admin listes.dalibo.com)) NIL NIL NIL
506bfb16.9060...@dalibo.info NIL))
KMail Kernel ETM (0x104c840) 1986 OK FETCH completed
all the time, with tens of thousands of messages. The akonadi console cannot
keep up… I have to activate debug only for one second, then it scrolls for at
least 10 seconds. These messages never stop. And if I try to capture for a
minute or so, akonadiconsole gets out of RAM.
I guess there is something it doesn't like in an imap folder... It's been doing
this on this account for at least 2 years. I have tried Kmail2 again at each
KDE release, and switched back because of that. I know I should have given it a
look before...
I tried to let it run for 24 hours, hoping it would settle. But it doesn't and
always comes back to fetching all emails in these few folders (always the same
3 or 4 collectionids).
I have 3 other accounts with no problem. Can I provide some more information ?
A log , a debug trace, whatever may help you solve this problem ?
--
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 323929] kmail high cpu load, seems stuck looping on fetching mails from akonadi
https://bugs.kde.org/show_bug.cgi?id=323929 Marc Cousin cousinm...@gmail.com changed: What|Removed |Added CC||cousinm...@gmail.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
[kmail2] [Bug 323287] Kmail doesn't send email, Mail Dispatcher Agent doesn't work
https://bugs.kde.org/show_bug.cgi?id=323287 Chet Murthy chet...@gmail.com changed: What|Removed |Added CC||chet...@gmail.com --- Comment #1 from Chet Murthy chet...@gmail.com --- I also find this problem. I'm running Ubuntu Raring, akonadi 4:4.10.5-0ubuntu0.1, on x86. I find that often for long periods, I can fetch mail from gmail (via IMAP) and send mail just fine. But then, for some reason, akonadi will fail to fetch mail from gmail, and fail to send mail, too. As the OP reports, the message will sit in my outbox folder, and repeated attempts to send queue messages will do nothing. When this happens, it happens for two different gmail accounts I've added to akonadi. Sometimes, if I reboot my laptop and log back in, akonadi will send the message, and will start fetching mail from gmail again. Sometimes, rebooting doesn't help. Eventually, after a while, something changes, and the next reboot will fix the problem. I am unable to debug, b/c I can't find a way to get a trace of what the mail dispatcher agent is doing, that could be useful. In akonadiconsole I see nothing related to actual IMAP transport, in the tab for the akonadi_maildispatcher_agent_. I see nothing in the akonadi_map_resource_NNN tabs, either. If there were some instructions someplace, to clue knowledgeable technical users into how to go about debugging akonadi problems, that'd be really helpful. -- 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 323936] New: The read/HAM/important flag will not be copied when flagging and copying is in the same filter rule
https://bugs.kde.org/show_bug.cgi?id=323936 Bug ID: 323936 Summary: The read/HAM/important flag will not be copied when flagging and copying is in the same filter rule Classification: Unclassified Product: kmail2 Version: 4.11 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: pro...@gmx.net I've made this filter rule: Criteria: Match all messages Actions: 1) Mark As: Important (or read, or HAM) 2) Copy Into Folder: Local Folders/Store Advanced tab: If this filter matches, stop processing here Add this filter to the Apply Filter menu Everything works as expected except that the copied e-mail is not marked as important, even though the e-mail was marked as important first before copied to the Store folder. Reproducible: Always Steps to Reproduce: 1. Make the rule described above 2. Select an e-mail and apply this rule Actual Results: The original e-mail is marked as important (as expected); There is a copied version of this e-mail is in the Store folder (as expected); The copied version of this e-mail IS NOT marked as important. Expected Results: The copied version of this e-mail is also marked as important because the original e-mail is marked important before it is copied to the Store 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
[kmail2] [Bug 323939] New: kmail/akonadi repeatedly asking for password to open KDE wallet (on behalf of IMAP resource)
https://bugs.kde.org/show_bug.cgi?id=323939 Bug ID: 323939 Summary: kmail/akonadi repeatedly asking for password to open KDE wallet (on behalf of IMAP resource) Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: chet...@gmail.com kmail and akonadi repeatedly ask (at intervals of 10-60mins, so not a problem) for password to open KDE wallet on behalf of one of the IMAP resources (same one every time). But kmail never manages to actually fetch any mail from that IMAP resource. I think this might be related to [Bug 323287] Kmail doesn't send email, Mail Dispatcher Agent doesn't work in that the cited behaviour only happens when I also see the cannot fetch mail that we know exists in gmail folder behaviour described in that other bug. Reproducible: Always Steps to Reproduce: don't really know what causes this 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
[Akonadi] [Bug 323672] Feeder crash on killing FindUnindexedItems Job
https://bugs.kde.org/show_bug.cgi?id=323672 Weng Xuetian wen...@gmail.com changed: What|Removed |Added CC||wen...@gmail.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
[kmail2] [Bug 323948] New: Reply doesn't select identity to use from email being replied to
https://bugs.kde.org/show_bug.cgi?id=323948 Bug ID: 323948 Summary: Reply doesn't select identity to use from email being replied to Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: list0...@paradise.net.nz Reply to an email does not select the correct identity to use for the reply. It always uses the default identity, but it should use the identity matching my email adddress in the email I'm replying to. Reproducible: Always Steps to Reproduce: 1. Click reply on an email sent to one of your identities that is NOT your default one. 2. 3. Actual Results: The reply has the default identity selected. Expected Results: Reply uses the same identity as the email being replied to! This is a regression from kmail 1. Matching for identity selection should be made on email address only - not on other parts like name, that can change, especially when replying to an older email. -- 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 294215] Maildir resource doesn't see subfolders.
https://bugs.kde.org/show_bug.cgi?id=294215 --- Comment #15 from Peter Lewis p...@muddygoat.org --- Just a thought, but I wondered if it might be easier to just have a new resource for Maildir (which correctly follows the spec), and then call the current one something else (KMaildir, or similar). Might make more sense than trying to come up with a resource to deal with both cases. Let me know if I can help. -- 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 310864] Select failed, server replied: A000154 NO Mailbox does not exist, or must be subscribed to.
https://bugs.kde.org/show_bug.cgi?id=310864 Mathieu Jobin somek...@somekool.net changed: What|Removed |Added CC||somek...@somekool.net --- Comment #3 from Mathieu Jobin somek...@somekool.net --- this is so annoying. running KDE 4.11, it is doing for only 1 of my IMAP account. I think I will trash the account and recreate it, that might fix it. the think I have many similar IMAP accounts on the same server... I'm not sure how this is related with the crash on bug #285653 -- 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 310864] Select failed, server replied: A000154 NO Mailbox does not exist, or must be subscribed to.
https://bugs.kde.org/show_bug.cgi?id=310864 --- Comment #4 from Mathieu Jobin somek...@somekool.net --- deleted the account in my kmail settings and recreated them. getting the same error. let me know what other info I can provide. -- 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 319289] filter rules for incoming messages on pop3 account do not seem to work
https://bugs.kde.org/show_bug.cgi?id=319289 bugzy bugzylit...@gmail.com changed: What|Removed |Added CC||bugzylit...@gmail.com --- Comment #3 from bugzy bugzylit...@gmail.com --- I am experiencing the same problem Kontact 4.10.5 on Fedora 19. I always have to apply all my filters manually in order to get them to work. I also think that this bug may be related to Bug 322871 (https://bugs.kde.org/show_bug.cgi?id=322871) which plagues KDE 4.11 -- 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
