[Akonadi] [Bug 373443] Mail Dispatcher Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0
https://bugs.kde.org/show_bug.cgi?id=373443 Mike Goodwin <m...@mgoodwin.net> changed: What|Removed |Added CC||m...@mgoodwin.net -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 385033] New: Kmail fails to start (unknown condition)
https://bugs.kde.org/show_bug.cgi?id=385033 Bug ID: 385033 Summary: Kmail fails to start (unknown condition) Product: kmail2 Version: 5.5.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@mgoodwin.net Target Milestone: --- Application: kmail (5.5.1) Qt Version: 5.7.1 Frameworks Version: 5.36.0 Operating System: Linux 4.12.13-300.fc26.x86_64 x86_64 Distribution: "Fedora release 26 (Twenty Six)" -- Information about the crash: This happens when I attempt to start kmail from the application menu, and immediately a drkonqi window appears. Using Fedora 26 The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f91f7e9d940 (LWP 25117))] Thread 21 (Thread 0x7f9196ffd700 (LWP 25148)): #0 0x7f91f96df89c in srb_callback () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #1 0x7f91f96e011f in srbchannel_rwloop () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #2 0x7f91fb5ca7f8 in pa_mainloop_dispatch () at /lib64/libpulse.so.0 #3 0x7f91fb5cabce in pa_mainloop_iterate () at /lib64/libpulse.so.0 #4 0x7f91fb5cac50 in pa_mainloop_run () at /lib64/libpulse.so.0 #5 0x7f91fb5d8ab9 in thread () at /lib64/libpulse.so.0 #6 0x7f91f96f0078 in internal_thread_func () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #7 0x7f921627936d in start_thread () at /lib64/libpthread.so.0 #8 0x7f921a328bbf in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f91977fe700 (LWP 25147)): #0 0x7f921627fe0a in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f920da58172 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f920da1f38e in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f920d9f9fab in base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f920d9f6828 in base::MessageLoop::RunHandler() () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f920da1326b in base::RunLoop::Run() () at /lib64/libQt5WebEngineCore.so.5 #6 0x7f920da2af66 in base::Thread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #7 0x7f920da2706b in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #8 0x7f921627936d in start_thread () at /lib64/libpthread.so.0 #9 0x7f921a328bbf in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f9197fff700 (LWP 25146)): #0 0x7f921627f90b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f920e1a7ea0 in cc::SingleThreadTaskGraphRunner::Run() () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f920da2a9a1 in base::SimpleThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f920da2706b in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f921627936d in start_thread () at /lib64/libpthread.so.0 #5 0x7f921a328bbf in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f91ad7fa700 (LWP 25145)): #0 0x7f921627f90b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f920da29725 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f920da29c07 in base::SequencedWorkerPool::Worker::Run() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f920da2a9a1 in base::SimpleThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f920da2706b in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f921627936d in start_thread () at /lib64/libpthread.so.0 #6 0x7f921a328bbf in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f91acff9700 (LWP 25144)): #0 0x7f921627f90b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f920da1f409 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f920da1f437 in base::WaitableEvent::Wait() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f920d9f9f5b in base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f920d9f6828 in base::MessageLoop::RunHandler() () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f920da1326b in base::RunLoop::Run() () at /lib64/libQt5WebEngineCore.so.5 #6 0x7f920da2af66 in base::Thread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #7 0x7f920da2706b in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #8 0x7f921627936d in start_thread () at /lib64/libpthread.so.0 #9
[Akonadi] [Bug 332400] IMAP IDLE stops working after some time.
https://bugs.kde.org/show_bug.cgi?id=332400 --- Comment #9 from Mike Goodwin <m...@mgoodwin.net> --- By the way I'm on: Plasma 5.8.5 kf5 5.29 kdepim 16.08 And will continue to be on the latest of what rdieter is doing with Fedora 25+ -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 332400] IMAP IDLE stops working after some time.
https://bugs.kde.org/show_bug.cgi?id=332400 --- Comment #8 from Mike Goodwin <m...@mgoodwin.net> --- I still have this bug I just don't login to this bug tracker very often, and I worked around it so I stopped being annoyed by it. If you configure an IDLE account and disable "Interval mail checking" it basically stops working after it times out, and doesn't reconnect the IDLE session. Thus, I have interval mail checking set at about 20 minutes and that seems to mostly work ok. However, My phone using K9 _always_ receives mail instantly via IDLE (because I can hear the alert) and it takes a substantial amount of time for Kmail to show the same notification on my computer (both of mine) I'm pretty sure most of the time It's just waiting the 20 minutes to check of I'm between checking intervals, so IDLE is probably doing nothing for me still. I'd be willing to work with anyone but I'm not sure where else to progress the bug on my own. I clearly have a configuration and server that is prone to this issue, but again other clients like K9 work flawlessly. -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled
https://bugs.kde.org/show_bug.cgi?id=363723 --- Comment #12 from Mike Goodwin <m...@mgoodwin.net> --- ... And it gets even stranger. There are lots of possibilities here so as I try them all I try to report back here. ONLY "Default' also crashes, so: 1. "Default" - crashes 2. "Default" + "roundcube" (Literal contents are '/* empty script */') with roundcube enabled crashes. 3. "Default" + "~roundcube~" ( same as above but roundcube is now disabled ) does not crash. In other words, it seems like the problem is more or less "Default script crashes unless a second AND disabled script is present" -- 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 363723] Kmail crashes when "Server supports sieve" enabled
https://bugs.kde.org/show_bug.cgi?id=363723 --- Comment #11 from Mike Goodwin <m...@mgoodwin.net> --- Created attachment 99280 --> https://bugs.kde.org/attachment.cgi?id=99280=edit sieve scripts and config that crashes kmail Hmm, I did some more testing. This is turning out to seem like a very specific edge case. I made a new blank script called "test". So now I have 1. Default (has real scripts) - enabled 2. roundcube (blank) - disabled 3. test (blank) - enabled This combination doesn't crash. Nor does 1-disabled, 2-enabled, 3-enabled; or 1-enabled, 2-disabled, 3-disabled. Only 1-enabled, 2-enabled, 3-(n/a or disabled) crashes. The literal contents of the sieve scripts are attached. I confirmed that it crashed kmail before I tarred them directly from my kolab server. Hopefully that helps. I only noticed this because I upgraded from F23 to F24 today. I didn't see this crash in 4.x version of kmail -- 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 363723] Kmail crashes when "Server supports sieve" enabled
https://bugs.kde.org/show_bug.cgi?id=363723 --- Comment #10 from Mike Goodwin <m...@mgoodwin.net> --- Version 5.1.3 Using: KDE Frameworks 5.22.0 Qt 5.6.0 (built against 5.6.0) The xcb windowing system $ rpm -qa | egrep "kmail|kdepim" kdepim-libs-15.12.3-1.fc24.x86_64 kdepimlibs-kxmlrpcclient-4.14.10-13.fc24.x86_64 kmail-15.12.3-1.fc24.x86_64 kdepimlibs-akonadi-4.14.10-13.fc24.x86_64 kdepim-runtime-15.12.3-1.fc24.x86_64 kdepimlibs-4.14.10-13.fc24.x86_64 kmail-libs-15.12.3-1.fc24.x86_64 kdepim-runtime-libs-15.12.3-1.fc24.x86_64 kdepim-common-15.12.3-1.fc24.x86_64 kf5-kmailtransport-15.12.3-1.fc24.x86_64 kdepimlibs-gpgme-4.14.10-13.fc24.x86_64 -- 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 363723] Kmail crashes when "Server supports sieve" enabled
https://bugs.kde.org/show_bug.cgi?id=363723 --- Comment #8 from Mike Goodwin <m...@mgoodwin.net> --- I can enable both in roundcube -- 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 363723] Kmail crashes when "Server supports sieve" enabled
https://bugs.kde.org/show_bug.cgi?id=363723 --- Comment #6 from Mike Goodwin <m...@mgoodwin.net> --- I see that the built-in kmail sieve script editor has a syntax checker (now that I can get to it), and it is reporting "No errors found" for both scripts. -- 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 363723] Kmail crashes when "Server supports sieve" enabled
https://bugs.kde.org/show_bug.cgi?id=363723 --- Comment #5 from Mike Goodwin <m...@mgoodwin.net> --- Some findings: 1. Neither script causes the problem when enabled separately/individually. 2. When both are enabled is when the crash happens, only then. 3. Related problem: a. When using the checkbox action to disable/enable scripts, selecting or unselecting either one results in the message "Sieve operation failed The server responded: script errors:" b. After clicking ok, the circular refreshing icon is perpetually present. You must restart the client for that to go away c. Checking the result of the action with roundcube separately, you can see that it actually carried the enable/disable action before erroring out (i.e. the script that was unchecked/checked is enabled/disabled) I do not believe there to be errors in the scripts as they were generated with roundcube. If you know of a way to syntax check or lint sieve scripts, that would be useful. -- 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 363723] Kmail crashes when "Server supports sieve" enabled
https://bugs.kde.org/show_bug.cgi?id=363723
--- Comment #4 from Mike Goodwin <m...@mgoodwin.net> ---
Yes I do.
Two separate scripts. One named "roundcube" (because that is the default
created by kolab/roundcube on setup" and a separate one I named "Default" that
I currently use.
Default mostly contains stuff like:
# rule:[kde-lists-fpo]
if header :contains "list-id" "kde.lists.fedoraproject.org"
{
fileinto "Mailing Lists/Fedora/kde";
stop;
}
While roundcube empty (but contains a header comment)
I see where this is going so I'll try and do some more sleuthing with regard to
a specific rule, or maybe the empty file and report back if I find 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
[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled
https://bugs.kde.org/show_bug.cgi?id=363723 Mike Goodwin <m...@mgoodwin.net> changed: What|Removed |Added Summary|Kmail crashes on start |Kmail crashes when "Server ||supports sieve" enabled -- 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 363723] Kmail crashes on start
https://bugs.kde.org/show_bug.cgi?id=363723 --- Comment #2 from Mike Goodwin <m...@mgoodwin.net> --- Noticing the sieve remarks in the last thread, I turned off sieve support for my kolab server account and have not been able to reproduce the bug again. I restarted kontact and kmail ten times each to confirm. After enabling sieve again, both crash 1-2 seconds after the main window renders. Changing something from my initial report, it does not *ALWAYS* crash, but does so 90% of the time. Every once in a while it starts normally and functions properly... -- 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 363723] Kmail crashes on start
https://bugs.kde.org/show_bug.cgi?id=363723 --- Comment #1 from Mike Goodwin <m...@mgoodwin.net> --- *** Bug 363722 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 363722] Kontact does not run in Fedora 24 beta
https://bugs.kde.org/show_bug.cgi?id=363722 Mike Goodwin <m...@mgoodwin.net> changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Mike Goodwin <m...@mgoodwin.net> --- *** This bug has been marked as a duplicate of bug 363723 *** -- 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 363723] New: Kmail crashes on start
https://bugs.kde.org/show_bug.cgi?id=363723 Bug ID: 363723 Summary: Kmail crashes on start Product: kmail2 Version: 5.1.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@mgoodwin.net Application: kmail (5.1.3) Qt Version: 5.6.0 Frameworks Version: 5.22.0 Operating System: Linux 4.5.5-300.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Starting kmail from the launcher - Unusual behavior I noticed: Kmail and kontact seem to be segfaulting on launch OS is upgraded Fedora KDE 23 to 24 beta The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f920f4a2940 (LWP 31793))] Thread 22 (Thread 0x7f9167fff700 (LWP 31835)): #0 0x7f92236b3f69 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f922eba6276 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7f922eba1922 in QThreadPoolThread::run() () from /lib64/libQt5Core.so.5 #3 0x7f922eba543f in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #4 0x7f92236ae5ba in start_thread () from /lib64/libpthread.so.0 #5 0x7f922df907cd in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7f917d202700 (LWP 31832)): #0 0x7f92226c6b64 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7f9222681f70 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f922268296b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f9222682b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f922edd369b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f922ed7a8ca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f922eba03f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f922eba543f in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f92236ae5ba in start_thread () from /lib64/libpthread.so.0 #9 0x7f922df907cd in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7f917ebfd700 (LWP 31830)): #0 0x7f922df84c4d in poll () from /lib64/libc.so.6 #1 0x7f9222682a46 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f9222682b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f922edd369b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f922ed7a8ca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f922eba03f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f922eba543f in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f92236ae5ba in start_thread () from /lib64/libpthread.so.0 #8 0x7f922df907cd in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7f917f3fe700 (LWP 31820)): #0 0x7f92226c6b49 in g_mutex_lock () from /lib64/libglib-2.0.so.0 #1 0x7f922268247c in g_main_context_check () from /lib64/libglib-2.0.so.0 #2 0x7f92226829e4 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f9222682b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f922edd369b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f922ed7a8ca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f922eba03f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f922eba543f in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f92236ae5ba in start_thread () from /lib64/libpthread.so.0 #9 0x7f922df907cd in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7f917700 (LWP 31819)): #0 0x7f92236b3bc0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f92277b48a3 in JSC::GCThread::gcThreadMain() () from /lib64/libQt5WebKit.so.5 #2 0x7f9227af0934 in WTF::wtfThreadEntryPoint(void*) () from /lib64/libQt5WebKit.so.5 #3 0x7f92236ae5ba in start_thread () from /lib64/libpthread.so.0 #4 0x7f922df907cd in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f9194bc6700 (LWP 31818)): #0 0x7f92236b3bc0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f92277b48a3 in JSC::GCThread::gcThreadMain() () from /lib64/libQt5WebKit.so.5 #2 0x7f9227af0934 in WTF::wtfThreadEntryPoint(void*) () from /lib64/libQt5WebKit.so.5 #3 0x7f92236ae5ba in start_thread () from /lib64/libpthread.so.0 #4 0x7f922df907cd in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f91953c7700 (LWP 31817)): #0 0x7f92236b3bc0 in
[kontact] [Bug 363722] New: Kontact does not run in Fedora 24 beta
https://bugs.kde.org/show_bug.cgi?id=363722 Bug ID: 363722 Summary: Kontact does not run in Fedora 24 beta Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@mgoodwin.net Application: kontact (5.1.3) Qt Version: 5.6.0 Frameworks Version: 5.22.0 Operating System: Linux 4.5.5-300.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Opened kontact from the application menu, application segfaults and presents drkonqi The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5b90903940 (LWP 16051))] Thread 28 (Thread 0x7f5ace422700 (LWP 16109)): #0 0x7f5ba3574f69 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5ba9b88276 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7f5ba9b83922 in QThreadPoolThread::run() () from /lib64/libQt5Core.so.5 #3 0x7f5ba9b8743f in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #4 0x7f5ba356f5ba in start_thread () from /lib64/libpthread.so.0 #5 0x7f5ba8f727cd in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7f5acf02c700 (LWP 16107)): #0 0x7f5ba3574f69 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5ba9b88276 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7f5ba9b83922 in QThreadPoolThread::run() () from /lib64/libQt5Core.so.5 #3 0x7f5ba9b8743f in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #4 0x7f5ba356f5ba in start_thread () from /lib64/libpthread.so.0 #5 0x7f5ba8f727cd in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f5acf82d700 (LWP 16106)): #0 0x7f5ba8f628cd in read () from /lib64/libc.so.6 #1 0x7f5ba23867a0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f5ba2343524 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f5ba23439e4 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f5ba2343b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f5ba9db569b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f5ba9d5c8ca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f5ba9b823f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f5ba9b8743f in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f5ba356f5ba in start_thread () from /lib64/libpthread.so.0 #10 0x7f5ba8f727cd in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7f5adb7fe700 (LWP 16090)): #0 0x7f5ba2387b60 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7f5ba2343080 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f5ba234396b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f5ba2343b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f5ba9db569b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f5ba9d5c8ca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f5ba9b823f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f5ba9b8743f in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f5ba356f5ba in start_thread () from /lib64/libpthread.so.0 #9 0x7f5ba8f727cd in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f5adbfff700 (LWP 16088)): #0 0x7f5ba9c33276 in QElapsedTimer::clockType() () from /lib64/libQt5Core.so.5 #1 0x7f5ba9c332c9 in QElapsedTimer::isMonotonic() () from /lib64/libQt5Core.so.5 #2 0x7f5ba9db378e in QTimerInfoList::repairTimersIfNeeded() () from /lib64/libQt5Core.so.5 #3 0x7f5ba9db3803 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #4 0x7f5ba9db4b8e in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #5 0x7f5ba2342f7d in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #6 0x7f5ba234396b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #7 0x7f5ba2343b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #8 0x7f5ba9db569b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #9 0x7f5ba9d5c8ca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #10 0x7f5ba9b823f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #11 0x7f5ba9b8743f in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #12 0x7f5ba356f5ba in start_thread () from
[Akonadi] [Bug 332400] IMAP IDLE stops working after some time.
https://bugs.kde.org/show_bug.cgi?id=332400 Mike Goodwin <m...@mgoodwin.net> changed: What|Removed |Added CC||m...@mgoodwin.net --- Comment #5 from Mike Goodwin <m...@mgoodwin.net> --- Is there any resolution to this? I'm seeing this on my kolab cyrus-imapd server as well. Seems to be server related as gmail still receives IDLE events -- 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 290787] KMail shown "Unknown" date when Date field exist
https://bugs.kde.org/show_bug.cgi?id=290787 --- Comment #16 from Mike Goodwin <m...@mgoodwin.net> --- Sorry, I always forget that there's no edit here like github. I wanted to include: Fedora 23: # rpm -qa | grep "kmail\|akonadi" kmail-libs-4.14.10-10.fc23.x86_64 baloo-akonadi-4.14.3-5.fc23.x86_64 akonadi-mysql-1.13.0-20.fc23.x86_64 akonadi-1.13.0-20.fc23.x86_64 kdepimlibs-akonadi-4.14.10-8.fc23.x86_64 kmail-4.14.10-10.fc23.x86_64 -- 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 290787] KMail shown "Unknown" date when Date field exist
https://bugs.kde.org/show_bug.cgi?id=290787 Mike Goodwin <m...@mgoodwin.net> changed: What|Removed |Added CC||m...@mgoodwin.net --- Comment #15 from Mike Goodwin <m...@mgoodwin.net> --- Absolutely, I specifically noticed this when sorting my email by "Date/Time of Most Recent in Subtree" because i've been dealing with mailing lists lately. Once I did that all the "Unknowns" came right to the top where I didn't want them to be. -- 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 #155 from Mike Goodwin <m...@mgoodwin.net> --- I just got hit by this Duplicated 17,000 messages, all did was hit the "apply all filters on folder" button, and then noticed that my phone was freaking out due to all the dupes. kmail-libs-4.14.10-10.fc23.x86_64 baloo-akonadi-4.14.3-5.fc23.x86_64 akonadi-mysql-1.13.0-20.fc23.x86_64 akonadi-1.13.0-20.fc23.x86_64 kdepimlibs-akonadi-4.14.10-8.fc23.x86_64 kmail-4.14.10-10.fc23.x86_64 On Fedora 23. Not happy, rest of the day is going to be fixing this mess -- 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 Mike Goodwin <m...@mgoodwin.net> changed: What|Removed |Added CC||m...@mgoodwin.net -- 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
