[Akonadi] [Bug 414974] New: Akonadi crashed while deleting emails
https://bugs.kde.org/show_bug.cgi?id=414974 Bug ID: 414974 Summary: Akonadi crashed while deleting emails Product: Akonadi Version: 5.11.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: bugs.kde.att...@online.de Target Milestone: --- Application: akonadiserver (5.11.3) Qt Version: 5.12.5 Frameworks Version: 5.64.0 Operating System: Linux 5.3.13-300.fc31.x86_64 x86_64 Distribution: "Fedora release 31 (Thirty One)" -- Information about the crash: - What I was doing when the application crashed: I have deleted a couple of emails. Kmail did not delete them and they were still marked as "new". This happens frequently. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8b6bc32800 (LWP 1679))] Thread 32 (Thread 0x7f8afbfff700 (LWP 2203)): #0 0x7f8b6f70e44c in read () from /lib64/libc.so.6 #1 0x7f8b6e36e4cf in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f8b6e3262e7 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f8b6e326742 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f8b6e3268d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f8b6fcb2cd3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f8b6fc5cceb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x55f546d4e5ce in Akonadi::Server::Connection::handleIncomingData() () #8 0x7f8b6fc94656 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #9 0x7f8b6fc88c15 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #10 0x7f8b6fc5dd55 in doNotify(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #11 0x7f8b6fc5dde8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7f8b6fcb1f78 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #13 0x7f8b6fcb282c in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #14 0x7f8b6e3264a0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #15 0x7f8b6e326830 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #16 0x7f8b6e3268d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #17 0x7f8b6fcb2cb5 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #18 0x7f8b6fc5cceb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #19 0x7f8b6fab5395 in QThread::exec() () from /lib64/libQt5Core.so.5 #20 0x7f8b6fab64e6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #21 0x7f8b6ef274e2 in start_thread () from /lib64/libpthread.so.0 #22 0x7f8b6f71d693 in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f8ae57fa700 (LWP 2137)): #0 0x7ffefc78a6cb in ?? () #1 0x7ffefc78a918 in clock_gettime () #2 0x7f8b6f6e46ab in clock_gettime@GLIBC_2.2.5 () from /lib64/libc.so.6 #3 0x7f8b6fcb24c5 in qt_gettime() () from /lib64/libQt5Core.so.5 #4 0x7f8b6fcb100d in QTimerInfoList::updateCurrentTime() () from /lib64/libQt5Core.so.5 #5 0x7f8b6fcb1419 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #6 0x7f8b6fcb2984 in timerSourcePrepareHelper(GTimerSource*, int*) () from /lib64/libQt5Core.so.5 #7 0x7f8b6fcb2a32 in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #8 0x7f8b6e325d1a in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #9 0x7f8b6e3266cb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #10 0x7f8b6e3268d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #11 0x7f8b6fcb2cd3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #12 0x7f8b6fc5cceb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #13 0x55f546d4e5ce in Akonadi::Server::Connection::handleIncomingData() () #14 0x7f8b6fc94656 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #15 0x7f8b6fc88c15 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7f8b6fc5dd55 in doNotify(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7f8b6fc5dde8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f8b6fcb1f78 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #19 0x7f8b6fcb282c in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #20 0x7f8b6e3264a0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x7f8b6e326830 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #22 0x7f8b6e3268d3 in
[Akonadi] [Bug 414966] Akonadi crash when performing search with already-present Last Search results
https://bugs.kde.org/show_bug.cgi?id=414966 --- Comment #1 from Marcus Harrison --- Created attachment 124392 --> https://bugs.kde.org/attachment.cgi?id=124392=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 414966] New: Akonadi crash when performing search with already-present Last Search results
https://bugs.kde.org/show_bug.cgi?id=414966 Bug ID: 414966 Summary: Akonadi crash when performing search with already-present Last Search results Product: Akonadi Version: 5.12.3 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Application: akonadiserver (5.12.3) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 4.15.0-72-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I used the search function (under Tools -> Find Messages...) to create a search folder called Last Search. The first search was successful. Consecutive attempts to use the same search function with different parameters failed, searching forever without updating the Last Search folder. Sometimes the Last Search folder would populate with all messages in the searched folders. Finally, quiting Kontact caused both Kontact and Akonadi server to crash. Performing these steps in sequence fairly reliably causes the crash in my experience. The crash can be reproduced every time. -- Backtrace (Reduced): #6 _mm_crc32_u64 (__V=, __C=) at /usr/lib/gcc/x86_64-linux-gnu/7/include/smmintrin.h:848 #7 crc32 (ptr=0xfe0600044fe0, len=, h=) at tools/qhash.cpp:112 #8 0x7f03a144e3c2 in hash (seed=, len=, p=) at tools/qhash.cpp:223 #9 qHash (key=..., seed=) at tools/qhash.cpp:239 #10 0x55ba0511201b in QHash::findNode (this=this@entry=0x55ba0609b328, akey=..., ahp=ahp@entry=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:934 Possible duplicates by query: bug 414229, bug 413844, bug 413385, bug 413205, bug 413201. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 410167] Cannot change or enter time for calendar entry
https://bugs.kde.org/show_bug.cgi?id=410167 --- Comment #9 from B Rhodes --- I think the problem has to do with time zones. I went into my System Settings -> Regional Settings -> Date & Time, changed the time zone and then changed it back. The problem seems to be better now. I think somewhere along the pike KOrg couldn't read the time zone values properly, so it would mess up calculating event times and then default to 00:00 - 23:59. See if this works for you. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 412751] Invalid RRULE in Timezone Component with libical 3.0.6
https://bugs.kde.org/show_bug.cgi?id=412751 --- Comment #19 from m...@visu.li --- (In reply to Fabian Vogt from comment #18) > With libical 3.0.6 there's an empty RRULE:, while with 3.0.5 there is an > invalid one instead. The other way around. 3.0.5 fine, 3.0.6 invalid. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 397677] Folder list shows all mails as unread
https://bugs.kde.org/show_bug.cgi?id=397677 Saeid Akbari changed: What|Removed |Added CC||saeidsc...@yahoo.com --- Comment #3 from Saeid Akbari --- Having this issue for quite some time. Used to work around it by using: akonadictl fsck while KMail is running and then restarting KMail afterward. But even this doesn't work anymore. It is really annoying and makes KMail unusable. KMail 19.08.3 KDE Frameworks 5.64.0 Qt 5.12.5 PostgreSQL 10.9 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 414955] KMail stops responding when preview pane active on Wayland-Plasma
https://bugs.kde.org/show_bug.cgi?id=414955 Sandro Knauß changed: What|Removed |Added Severity|crash |normal --- Comment #1 from Sandro Knauß --- It is reported as Debian Bug: https://bugs.debian.org/946365 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 414955] New: KMail stops responding when preview pane active on Wayland-Plasma
https://bugs.kde.org/show_bug.cgi?id=414955 Bug ID: 414955 Summary: KMail stops responding when preview pane active on Wayland-Plasma Product: kmail2 Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: pug...@yahoo.de Target Milestone: --- SUMMARY KMail stops responding when preview pane active on Wayland-Plasma STEPS TO REPRODUCE Started kmail on wayland-plasma with active preview pane. The preview stays black at the beginning. When e.g. hovering with the mouse over the preview, clicking on a different email or changing the folder the whole kmail software stops reacting and the title bar shows an unresponsive notification. No crash notification. When not interacting with the enabled preview pane the software stays responsive, even the settings can be reached to disable preview, which makes kmail work fine. EMail content can then be viewed in separately opened windows by doubleclicking them. Disabling HTML preference does not help. This problem does not happen with the preview pane disabled and in either configuration on X-Window. OBSERVED RESULT KMail stops reacting. EXPECTED RESULT EMail is displayed SOFTWARE/OS VERSIONS Running Debian testing, KMail 19.08.3 and 19.08.3 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 414839] Folder expiration not automatic
https://bugs.kde.org/show_bug.cgi?id=414839 aux...@gmail.com changed: What|Removed |Added CC||aux...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
