[kmail2] [Bug 283020] Store Kmail (Akonadi) tags in IMAP flags to enable syncing between mail clients
https://bugs.kde.org/show_bug.cgi?id=283020 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 446104] QtWebengine-based views broken in master - affects Kmail + Akregator + more in wayland session
https://bugs.kde.org/show_bug.cgi?id=446104 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 449514] KMail crashes when closing it
https://bugs.kde.org/show_bug.cgi?id=449514 --- Comment #5 from Dennis Schridde --- Created attachment 151591 --> https://bugs.kde.org/attachment.cgi?id=151591=edit New crash information added by DrKonqi kmail (5.21.0 (22.08.0)) using Qt 5.15.5 KMail came up showing "Unknown" next to the loading bar in the bottom border of the application and now folders or emails in the main part of the application. I closed it and received the crash report. -- Backtrace (Reduced): #4 0x7ff1bb926354 in QAction::setText(QString const&) () at /usr/lib64/libQt5Widgets.so.5 #5 0x7ff1c3ee0212 in KMMainWidget::updateFolderMenu() (this=0x556a23d08ef0) at /tmp/portage/kde-apps/kmail-22.08.0/work/kmail-22.08.0/src/kmmainwidget.cpp:4045 #6 0x7ff1c3eeaa6c in KMMainWidget::setupActions() (this=) at /tmp/portage/kde-apps/kmail-22.08.0/work/kmail-22.08.0/src/kmmainwidget.cpp:3405 #7 0x7ff1c3ef00b2 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) (this=this@entry=0x556a23d08ef0, parent=parent@entry=0x556a23da71a0, aGUIClient=aGUIClient@entry=0x556a23da7220, actionCollection=, config=...) at /tmp/portage/kde-apps/kmail-22.08.0/work/kmail-22.08.0/src/kmmainwidget.cpp:242 #8 0x7ff1c3e995c3 in KMMainWin::KMMainWin(QWidget*) (this=this@entry=0x556a23da71a0, __in_chrg=, __vtt_parm=) at /tmp/portage/kde-apps/kmail-22.08.0/work/kmail-22.08.0/src/kmmainwin.cpp:55 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 455472] Reminders crashes on login
https://bugs.kde.org/show_bug.cgi?id=455472 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 449514] KMail crashes when closing it
https://bugs.kde.org/show_bug.cgi?id=449514 --- Comment #3 from Dennis Schridde --- Created attachment 150361 --> https://bugs.kde.org/attachment.cgi?id=150361=edit New crash information added by DrKonqi kmail (5.20.2 (22.04.2)) using Qt 5.15.5 I changed Sieve filters and closed KMail afterwards. Then it crashed -- Backtrace (Reduced): #4 0x7ff77d57f815 in QAction::setText(QString const&) () at /usr/lib64/libQt5Widgets.so.5 #5 0x7ff785ae3ec2 in KMMainWidget::updateFolderMenu() (this=0x5612de398bc0) at /tmp/portage/kde-apps/kmail-22.04.2/work/kmail-22.04.2/src/kmmainwidget.cpp:4037 #6 0x7ff785aeea57 in KMMainWidget::setupActions() (this=0x5612de398bc0) at /tmp/portage/kde-apps/kmail-22.04.2/work/kmail-22.04.2/src/kmmainwidget.cpp:3399 #7 0x7ff785af44e9 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) (this=this@entry=0x5612de398bc0, parent=parent@entry=0x5612d331a4d0, aGUIClient=aGUIClient@entry=0x5612d331a548, actionCollection=actionCollection@entry=0x5612decdf8c0, config=...) at /tmp/portage/kde-apps/kmail-22.04.2/work/kmail-22.04.2/src/kmmainwidget.cpp:242 #8 0x7ff785a9d9fa in KMMainWin::KMMainWin(QWidget*) (this=this@entry=0x5612d331a4d0, __in_chrg=, __vtt_parm=) at /tmp/portage/kde-apps/kmail-22.04.2/work/kmail-22.04.2/src/kmmainwin.cpp:49 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453753] New: Akonadi crashes when opening KMail
https://bugs.kde.org/show_bug.cgi?id=453753 Bug ID: 453753 Summary: Akonadi crashes when opening KMail Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadiserver (5.20.0 (22.04.0)) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.17.7-gentoo-dist x86_64 Windowing System: Wayland Distribution: "Gentoo Base System release 2.8" DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: When I open KMail, it tries to start Akonadi, which immediately crashes. This is reproducible every time I open KMail. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x565000140274 in Akonadi::Server::SchemaVersion::generation (this=this@entry=0x7fb6a5bdc850) at /usr/include/qt5/QtCore/qshareddata.h:82 #5 0x5650001f97ba in Akonadi::Server::NotificationSubscriber::NotificationSubscriber (this=this@entry=0x7fb6983186f0, manager=manager@entry=0x565000581070, socketDescriptor=socketDescriptor@entry=163) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:307 #6 0x5650001f61bf in Akonadi::Server::NotificationManager::registerConnection (this=0x565000581070, socketDescriptor=163) at /tmp/portage/kde-apps/akonadi-22.04.0/work/akonadi-22.04.0/src/server/notificationmanager.cpp:87 #7 0x7fb6aae63d16 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #8 0x7fb6aae38415 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #9 0x7fb6aae3bab5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #10 0x7fb6aae8ab73 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/libQt5Core.so.5 #11 0x7fb6a935d60b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #12 0x7fb6a935d8c8 in ?? () from /usr/lib64/libglib-2.0.so.0 #13 0x7fb6a935d97f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #14 0x7fb6aae8a604 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #15 0x7fb6aae36e3b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #16 0x7fb6aac817aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #17 0x7fb6aac82949 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #18 0x7fb6aa808f5a in ?? () from /usr/lib64/libc.so.6 #19 0x7fb6aa88e6fc in ?? () from /usr/lib64/libc.so.6 Thread 2 (Thread 0x7fb6a6aa6640 (LWP 19369) "QDBusConnection"): #1 0x7fb6aa8541a9 in clock_gettime () from /usr/lib64/libc.so.6 #2 0x7fb6aae89ec1 in qt_gettime() () from /usr/lib64/libQt5Core.so.5 #3 0x7fb6aae88809 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5 #4 0x7fb6aae88c85 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/libQt5Core.so.5 #5 0x7fb6aae8a8de in timerSourcePrepare(_GSource*, int*) () from /usr/lib64/libQt5Core.so.5 #6 0x7fb6a935cd4b in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #7 0x7fb6a935d783 in ?? () from /usr/lib64/libglib-2.0.so.0 #8 0x7fb6a935d97f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #9 0x7fb6aae8a68e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #10 0x7fb6aae36e3b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #11 0x7fb6aac817aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #12 0x7fb6ab173537 in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #13 0x7fb6aac82949 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #14 0x7fb6aa808f5a in ?? () from /usr/lib64/libc.so.6 #15 0x7fb6aa88e6fc in ?? () from /usr/lib64/libc.so.6 Thread 1 (Thread 0x7fb6a6ed8cc0 (LWP 19362) "akonadiserver"): #1 0x7fb6aa808624 in pthread_cond_timedwait () from /usr/lib64/libc.so.6 #2 0x7fb6aac882a5 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #3 0x7fb6aac82681 in QThread::wait(QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #4 0x7fb6aac8149c in QThread::wait(unsigned long) () from /usr/lib64/libQt5Core.so.5 #5 0x565000223a40 in Akonadi::Server::AkThread::quitThread (this=this@entry=0x565000581070) at /tmp/portage/kde-apps/akonadi-22.04.0/work/akonadi-22.04.0/src/server/akthread.cpp:55 #6 0x5650001f527e in Akonadi::Server::NotificationManager::~NotificationManager (this=0x565000581070, __in_chrg=) at
[kmail2] [Bug 449514] KMail crashes when closing it
https://bugs.kde.org/show_bug.cgi?id=449514 --- Comment #2 from Dennis Schridde --- Created attachment 148656 --> https://bugs.kde.org/attachment.cgi?id=148656=edit New crash information added by DrKonqi kmail (5.20.0 (22.04.0)) using Qt 5.15.3 - What I was doing when the application crashed: I selected an email address in KRunner, KMail opened with the email editor, then it crashed while I was looking at the email list, I did not write the email or close the editor window yet. -- Backtrace (Reduced): #4 0x7f80d0abf7d5 in QAction::setText(QString const&) () at /usr/lib64/libQt5Widgets.so.5 #5 0x7f80d9043072 in KMMainWidget::updateFolderMenu() (this=0x555b575424e0) at /tmp/portage/kde-apps/kmail-22.04.0/work/kmail-22.04.0/src/kmmainwidget.cpp:4036 #6 0x7f80d904db92 in KMMainWidget::setupActions() (this=0x555b575424e0) at /tmp/portage/kde-apps/kmail-22.04.0/work/kmail-22.04.0/src/kmmainwidget.cpp:3398 #7 0x7f80d9053659 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) (this=this@entry=0x555b575424e0, parent=parent@entry=0x555b56cb8530, aGUIClient=aGUIClient@entry=0x555b56cb85a8, actionCollection=actionCollection@entry=0x555b58220300, config=...) at /tmp/portage/kde-apps/kmail-22.04.0/work/kmail-22.04.0/src/kmmainwidget.cpp:242 #8 0x7f80d8ffcbba in KMMainWin::KMMainWin(QWidget*) (this=this@entry=0x555b56cb8530, __in_chrg=, __vtt_parm=) at /tmp/portage/kde-apps/kmail-22.04.0/work/kmail-22.04.0/src/kmmainwin.cpp:49 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 449514] KMail crashes when closing it
https://bugs.kde.org/show_bug.cgi?id=449514 --- Comment #1 from Dennis Schridde --- Created attachment 147789 --> https://bugs.kde.org/attachment.cgi?id=147789=edit New crash information added by DrKonqi kmail (5.19.3 (21.12.3)) using Qt 5.15.2 - What I was doing when the application crashed: I clicked on a `mailto:...` link in a browser. KMail opened and immediately closed again. Then the crash report appeared. -- Backtrace (Reduced): #4 0x7f9ae69bd7d5 in QAction::setText(QString const&) () at /usr/lib64/libQt5Widgets.so.5 #5 0x7f9aeef22862 in KMMainWidget::updateFolderMenu() (this=0x55afa94239d0) at /tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwidget.cpp:4043 #6 0x7f9aeef2d3b5 in KMMainWidget::setupActions() (this=0x55afa94239d0) at /tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwidget.cpp:3405 #7 0x7f9aeef32ce9 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) (this=this@entry=0x55afa94239d0, parent=parent@entry=0x55afaafee8a0, aGUIClient=aGUIClient@entry=0x55afaafee918, actionCollection=actionCollection@entry=0x55afaaf8f140, config=...) at /tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwidget.cpp:251 #8 0x7f9aeeedc4fa in KMMainWin::KMMainWin(QWidget*) (this=this@entry=0x55afaafee8a0, __in_chrg=, __vtt_parm=) at /tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwin.cpp:49 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 449514] KMail crashes when closing it
https://bugs.kde.org/show_bug.cgi?id=449514 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 449557] Akonadi Server crashes when starting KMail after booting the computer
https://bugs.kde.org/show_bug.cgi?id=449557 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.gentoo.org/sho ||w_bug.cgi?id=832012 Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Dennis Schridde --- This seems to be an issue between MariaDB 10.6.5 and Linux 5.16.5: https://bugs.gentoo.org/show_bug.cgi?id=832012 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 449557] New: Akonadi Server crashes when starting KMail after booting the computer
https://bugs.kde.org/show_bug.cgi?id=449557 Bug ID: 449557 Summary: Akonadi Server crashes when starting KMail after booting the computer Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadiserver (5.19.1 (21.12.1)) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.16.5-gentoo-dist x86_64 Windowing System: Wayland Distribution: "Gentoo Base System release 2.8" DrKonqi: 5.23.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: 1. I restarted my computer. 2. I logged in. 3. I opened KMail. 4. I saw the notification that Akonadi Server had crashed. (Split-second after starting KMail. Not entirely sure what came first.) 5. KMail says it tries to start the PIM system, but eventually turns to say "the akonadi personal information managment service is not operational" The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted [KCrash Handler] #4 0x7fd999ac6d2c in ?? () from /usr/lib64/libc.so.6 #5 0x7fd999a79a82 in raise () from /usr/lib64/libc.so.6 #6 0x7fd999a64449 in abort () from /usr/lib64/libc.so.6 #7 0x7fd999cf78b2 in __gnu_cxx::__verbose_terminate_handler () at /var/tmp/portage/sys-devel/gcc-11.2.1_p20220115/work/gcc-11-20220115/libstdc++-v3/libsupc++/vterminate.cc:95 #8 0x7fd999d035e6 in __cxxabiv1::__terminate (handler=) at /var/tmp/portage/sys-devel/gcc-11.2.1_p20220115/work/gcc-11-20220115/libstdc++-v3/libsupc++/eh_terminate.cc:48 #9 0x7fd999d03651 in std::terminate () at /var/tmp/portage/sys-devel/gcc-11.2.1_p20220115/work/gcc-11-20220115/libstdc++-v3/libsupc++/eh_terminate.cc:58 #10 0x7fd999d038f3 in __cxxabiv1::__cxa_throw (obj=, tinfo=0x559a830ee260 , dest=0x559a82fd8870 ) at /var/tmp/portage/sys-devel/gcc-11.2.1_p20220115/work/gcc-11-20220115/libstdc++-v3/libsupc++/eh_throw.cc:95 #11 0x559a82ee77f1 in Akonadi::Server::DbIntrospector::hasIndex(QString const&, QString const&) [clone .cold] () #12 0x559a82fda85b in Akonadi::Server::DbInitializer::checkIndexes(Akonadi::Server::TableDescription const&) () #13 0x559a82fdbb96 in Akonadi::Server::DbInitializer::updateIndexesAndConstraints() () #14 0x559a82fbd743 in Akonadi::Server::DataStore::init() () #15 0x559a82ef7f18 in Akonadi::Server::AkonadiServer::setupDatabase() () #16 0x559a82efa0d5 in Akonadi::Server::AkonadiServer::init() () #17 0x7fd99a119b36 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #18 0x7fd99a0ee275 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #19 0x7fd99a0f1915 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #20 0x7fd99a140963 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/libQt5Core.so.5 #21 0x7fd99862735b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #22 0x7fd998627618 in ?? () from /usr/lib64/libglib-2.0.so.0 #23 0x7fd9986276cf in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #24 0x7fd99a1403f4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #25 0x7fd99a0ecc9b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #26 0x7fd99a0f52cd in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #27 0x559a82ef395e in main () [Inferior 1 (process 2504) detached] The reporter indicates this bug may be a duplicate of or related to bug 434236. Possible duplicates by query: bug 448616, bug 448195, bug 446579, bug 445746, bug 445496. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 449514] New: KMail crashes when closing it
https://bugs.kde.org/show_bug.cgi?id=449514 Bug ID: 449514 Summary: KMail crashes when closing it Product: kmail2 Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: kmail (5.19.1 (21.12.1)) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.15.18-gentoo-dist x86_64 Windowing System: Wayland Distribution: "Gentoo Base System release 2.8" DrKonqi: 5.23.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I open and then immediately close KMail. It crashes. It also crashes after reading emails for some time. This is 100% reproducible. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7efdf1af87d5 in QAction::setText(QString const&) () at /usr/lib64/libQt5Widgets.so.5 #5 0x7efdfa0776d2 in KMMainWidget::updateFolderMenu() () at /usr/lib64/libkmailprivate.so.5 #6 0x7efdfa082236 in KMMainWidget::setupActions() () at /usr/lib64/libkmailprivate.so.5 #7 0x7efdfa087b79 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) () at /usr/lib64/libkmailprivate.so.5 #8 0x7efdfa03137a in KMMainWin::KMMainWin(QWidget*) () at /usr/lib64/libkmailprivate.so.5 #9 0x7efdfa042797 in KMKernel::openReader(bool, bool) () at /usr/lib64/libkmailprivate.so.5 #10 0x7efdfa047bcf in KMKernel::action(bool, bool, bool, QString const&, QString const&, QString const&, QString const&, QString const&, QUrl const&, QList const&, QStringList const&, QString const&, QString const&, QString const&) () at /usr/lib64/libkmailprivate.so.5 #11 0x7efdfa049520 in KMKernel::handleCommandLine(bool, QStringList const&, QString const&) () at /usr/lib64/libkmailprivate.so.5 #12 0x5592ba12b9f2 in KMailApplication::activate(QStringList const&, QString const&) () #13 0x7efdfa192123 in () at /usr/lib64/libKF5KontactInterface.so.5 #14 0x7efdfa1923d3 in KontactInterface::PimUniqueApplication::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/libKF5KontactInterface.so.5 #15 0x7efdf079896b in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () at /usr/lib64/libQt5DBus.so.5 #16 0x7efdf079c4b3 in QDBusConnectionPrivate::activateCall(QObject*, int, QDBusMessage const&) [clone .part.0] () at /usr/lib64/libQt5DBus.so.5 #17 0x7efdf079cd6e in QDBusConnectionPrivate::activateObject(QDBusConnectionPrivate::ObjectTreeNode&, QDBusMessage const&, int) () at /usr/lib64/libQt5DBus.so.5 #18 0x7efdf079f2e8 in QDBusActivateObjectEvent::placeMetaCall(QObject*) () at /usr/lib64/libQt5DBus.so.5 #19 0x7efdf10f8b36 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #20 0x7efdf1afc96f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #21 0x7efdf10cd2a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #22 0x7efdf10d0915 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #23 0x7efdf111f963 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /usr/lib64/libQt5Core.so.5 #24 0x7efdeac0335b in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #25 0x7efdeac03618 in () at /usr/lib64/libglib-2.0.so.0 #26 0x7efdeac036cf in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #27 0x7efdf111f3f4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #28 0x7efdf10cbc9b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #29 0x7efdf10d42cd in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #30 0x5592ba12b605 in main () [Inferior 1 (process 2424) detached] Possible duplicates by query: bug 448024, bug 447360, bug 443988, bug 362085, bug 361094. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 440874] Folder list scrolls up when trying to drag message into folder
https://bugs.kde.org/show_bug.cgi?id=440874 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=437155 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 440874] New: Folder list scrolls up when trying to drag message into folder
https://bugs.kde.org/show_bug.cgi?id=440874 Bug ID: 440874 Summary: Folder list scrolls up when trying to drag message into folder Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- SUMMARY When trying to drag a message from the message list of one folder into another folder (by moving it over a folder in the folder list), the folder list starts to scroll up to the top, moving the folders under the mouse and scrolling the intended folder out of view. A workaround to be able to drag and drop messages into the target folder is to collapse all folders in the list, so that it cannot scroll further up. This only works, if the target folder is visible when the list is fully scrolled up. STEPS TO REPRODUCE 1. Expand some folders in the folder list 2. Open a folder so that its messages are shown in the message list 3. Drag a message from the message list over the folder list OBSERVED RESULT The folder list starts scrolling up once the mouse is moved over it. It will keep moving even when the mouse is still. EXPECTED RESULT The folder list does not move on its own. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.8 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 2400G with Radeon Vega Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon™ Vega 11 Graphics ADDITIONAL INFORMATION KMail 5.17.3 Under some circumstances, very seldomly, this magic scrolling does not happen. I was however so far unable to reproduce that. -- You are receiving this mail because: You are the assignee for the bug.
[kmime] [Bug 387423] Attachment icon not shown in message list for multipart/alternative attachments
https://bugs.kde.org/show_bug.cgi?id=387423 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[kmime] [Bug 387423] Attachment icon not shown in message list for multipart/alternative attachments
https://bugs.kde.org/show_bug.cgi?id=387423 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=395687 CC||m...@naraesk.eu --- Comment #6 from Dennis Schridde --- *** Bug 395687 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 393417] Some mails don't have the "has attachment" flag
https://bugs.kde.org/show_bug.cgi?id=393417 Dennis Schridde changed: What|Removed |Added Status|REPORTED|RESOLVED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=387423 Resolution|--- |DUPLICATE CC||devuran...@gmx.net --- Comment #4 from Dennis Schridde --- *** This bug has been marked as a duplicate of bug 387423 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmime] [Bug 387423] Attachment icon not shown in message list for multipart/alternative attachments
https://bugs.kde.org/show_bug.cgi?id=387423 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=393417 CC||aa...@kde.org --- Comment #7 from Dennis Schridde --- *** Bug 393417 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395687] Mails from Apple Mail are shown without attachment
https://bugs.kde.org/show_bug.cgi?id=395687 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=387423 --- Comment #4 from Dennis Schridde --- *** This bug has been marked as a duplicate of bug 387423 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 423675] Akonadi IMAP resource crashes immediately when synchronising IMAP account
https://bugs.kde.org/show_bug.cgi?id=423675 Dennis Schridde changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Dennis Schridde --- As of today, 2020-12-09, the issue is no longer reproducible on my Fedora 33 system with: * kf5-akonadi-server-20.08.3-1.fc33 * kf5-pimcommon-akonadi-20.08.3-1.fc33 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418844] Akonadi IMAP resource crash after attempted offline/online
https://bugs.kde.org/show_bug.cgi?id=418844 --- Comment #14 from Dennis Schridde --- As of today, 2020-12-09, the issue is no longer reproducible on my Fedora 33 system with: * kf5-akonadi-server-20.08.3-1.fc33 * kf5-pimcommon-akonadi-20.08.3-1.fc33 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 428459] Akonadi IMAP resource crashes right after being restarted
https://bugs.kde.org/show_bug.cgi?id=428459 Dennis Schridde changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Dennis Schridde --- As of today, 2020-12-09, the issue is no longer reproducible on my Fedora 33 system with: * kf5-akonadi-server-20.08.3-1.fc33 * kf5-pimcommon-akonadi-20.08.3-1.fc33 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418844] Akonadi IMAP resource crash after attempted offline/online
https://bugs.kde.org/show_bug.cgi?id=418844 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=428459 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 423675] Akonadi IMAP resource crashes immediately when synchronising IMAP account
https://bugs.kde.org/show_bug.cgi?id=423675 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=428459 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 428459] Akonadi IMAP resource crashes right after being restarted
https://bugs.kde.org/show_bug.cgi?id=428459 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=423675, ||https://bugs.kde.org/show_b ||ug.cgi?id=418844 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 428459] Akonadi IMAP resource crashes right after being restarted
https://bugs.kde.org/show_bug.cgi?id=428459 --- Comment #1 from Dennis Schridde --- Created attachment 133572 --> https://bugs.kde.org/attachment.cgi?id=133572=edit New crash information added by DrKonqi akonadi_imap_resource (5.15.3 (20.08.3)) using Qt 5.15.1 - What I was doing when the application crashed: Still reproducible with latest updates on Fedora 33 with KDE 20.08.3. Akonadi IMAP resource will crash right after toggling the resource offline and then back to online in Akonadi Console. Bug #429344 seems like it describes the exact same problem. -- Backtrace (Reduced): #5 0x7fcfc998903f in qobject_cast(QObject*) (object=) at /usr/include/qt5/QtCore/qobject.h:519 #6 QtPrivate::QVariantValueHelper::object(QVariant const&) (v=...) at /usr/include/qt5/QtCore/qvariant.h:753 #7 QtPrivate::ObjectInvoker, QVariant const&, Akonadi::RecursiveMover*>::invoke(QVariant const&) (a=...) at /usr/include/qt5/QtCore/qvariant.h:107 #8 qvariant_cast(QVariant const&) (v=...) at /usr/include/qt5/QtCore/qvariant.h:879 #9 QVariant::value() const (this=0x557b8606a748) at /usr/include/qt5/QtCore/qvariant.h:367 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 428459] Akonadi IMAP resource crashes right after being restarted
https://bugs.kde.org/show_bug.cgi?id=428459 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 428459] New: Akonadi IMAP resource crashes right after being restarted
https://bugs.kde.org/show_bug.cgi?id=428459 Bug ID: 428459 Summary: Akonadi IMAP resource crashes right after being restarted Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadi_imap_resource (5.15.1 (20.08.1)) Qt Version: 5.15.1 Frameworks Version: 5.73.0 Operating System: Linux 5.8.16-300.fc33.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 33 (Thirty Three) -- Information about the crash: - What I was doing when the application crashed: Whenever I restart one of my Akonadi IMAP resources (using Akonadi Console, since normally Akonadi does not even seem to start it anymore), it immediately crashes. I receive no emails via this resource in KMail. The crash can be reproduced every time. -- Backtrace: Application: Mailbox.org (akonadi_imap_resource), signal: Segmentation fault [KCrash Handler] #4 0x0007fc02fc04 in () #5 0x7f139c9f5f0a in QMetaObject::cast(QObject const*) const (this=0x7f139e331320 , obj=0x5627bec82430) at kernel/qmetaobject.cpp:382 #6 0x7f139e30dc0f in qobject_cast(QObject*) (object=) at /usr/include/qt5/QtCore/qobject.h:519 #7 QtPrivate::QVariantValueHelper::object(QVariant const&) (v=...) at /usr/include/qt5/QtCore/qvariant.h:753 #8 QtPrivate::ObjectInvoker, QVariant const&, Akonadi::RecursiveMover*>::invoke(QVariant const&) (a=...) at /usr/include/qt5/QtCore/qvariant.h:107 #9 qvariant_cast(QVariant const&) (v=...) at /usr/include/qt5/QtCore/qvariant.h:879 #10 QVariant::value() const (this=0x5627bec2e4e8) at /usr/include/qt5/QtCore/qvariant.h:367 #11 Akonadi::ResourceScheduler::executeNext() (this=) at /usr/src/debug/kf5-akonadi-server-20.08.1-2.fc33.x86_64/src/agentbase/resourcescheduler.cpp:423 #12 0x7f139ca14e2e in QObject::event(QEvent*) (this=0x5627bec2e470, e=0x5627bedb85f0) at kernel/qobject.cpp:1314 #13 0x7f139d56815f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x5627bec2e470, e=0x5627bedb85f0) at kernel/qapplication.cpp:3630 #14 0x7f139c9edbf8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5627bec2e470, event=0x5627bedb85f0) at ../../include/QtCore/5.15.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #15 0x7f139c9f0837 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x5627be80c040) at kernel/qcoreapplication.cpp:1817 #16 0x7f139ca38f63 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x5627be8e0010) at kernel/qeventdispatcher_glib.cpp:277 #17 0x7f139ac4ffd7 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #18 0x7f139aca0d88 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #19 0x7f139ac4d41f in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #20 0x7f139ca38a2f in QEventDispatcherGlib::processEvents(QFlags) (this=0x5627be8f2d80, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7f139c9ec65b in QEventLoop::exec(QFlags) (this=0x7ffd5a2634e0, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #22 0x7f139c9f4020 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x5627be60d6bf in main () [Inferior 1 (process 85879) detached] Possible duplicates by query: bug 428403, bug 428084, bug 428071, bug 427323, bug 426999. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 396663] Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=415339 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 415339] Akonadi IMAP crashed on waking up from sleep
https://bugs.kde.org/show_bug.cgi?id=415339 --- Comment #13 from Dennis Schridde --- (In reply to Ahmad Samir from comment #12) > *** Bug 418599 has been marked as a duplicate of this bug. *** I carried over the See-Alsos from bug #418599, which reference issues that appeared on the same systems with the same accounts and might be related to each other. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 423675] Akonadi IMAP resource crashes immediately when synchronising IMAP account
https://bugs.kde.org/show_bug.cgi?id=423675 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=415339 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 415339] Akonadi IMAP crashed on waking up from sleep
https://bugs.kde.org/show_bug.cgi?id=415339 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418593, ||https://bugs.kde.org/show_b ||ug.cgi?id=418595, ||https://bugs.kde.org/show_b ||ug.cgi?id=418912, ||https://bugs.kde.org/show_b ||ug.cgi?id=396663, ||https://bugs.kde.org/show_b ||ug.cgi?id=423675, ||https://bugs.kde.org/show_b ||ug.cgi?id=418599 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418599] Crash when moving emails from one IMAP server to another
https://bugs.kde.org/show_bug.cgi?id=418599 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=415339 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418912] Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=415339 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418595] Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=415339 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418593] Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0
https://bugs.kde.org/show_bug.cgi?id=418593 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=415339 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 414436] Akonadi crashes when opening a certain mailbox folder in KMail
https://bugs.kde.org/show_bug.cgi?id=414436 Dennis Schridde changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Dennis Schridde --- (In reply to Ahmad Samir from comment #2) > The backtraces aren't very useful, but the error logs are much more > informative in such cases (see ~/.xsession-errors or > ~/.local/share/sddm/xorg-session.log for sddm users). KMail and Akonadi have been relatively stable on my Gentoo system recently. I will close this and open a new report, if I should notice new crashes in the future. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 424509] New: KMail crashed on exit
https://bugs.kde.org/show_bug.cgi?id=424509 Bug ID: 424509 Summary: KMail crashed on exit Product: kmail2 Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: kmail (5.14.3 (20.04.3)) Qt Version: 5.15.0 Frameworks Version: 5.72.0 Operating System: Linux 5.7.9 x86_64 Windowing system: X11 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: I exited KMail and disconnected the monitor of the computer. When I reconnected it a few hours later, I found the crash report about KMail. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7f318b75ad66 in QScopedPointer >::operator->() const (this=0x8) at /tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/include/QtCore/../../src/corelib/tools/qscopedpointer.h:116 #5 qGetPtrHelper > >(QScopedPointer >&) (ptr=...) at /tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/include/QtCore/../../src/corelib/global/qglobal.h:1133 #6 QObject::d_func() (this=0x0) at /tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/include/QtCore/../../src/corelib/kernel/qobject.h:132 #7 QObjectPrivate::get(QObject*) (o=0x0) at /tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/kernel/qobject_p.h:339 #8 QEventLoopLocker::QEventLoopLocker() (this=0x55caa714cf50) at /tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/src/corelib/kernel/qeventloop.cpp:437 #9 0x7f318c6f69ab in KJobPrivate::KJobPrivate() () at /usr/lib64/libKF5CoreAddons.so.5 #10 0x7f318c6f3659 in KCompositeJobPrivate::KCompositeJobPrivate() () at /usr/lib64/libKF5CoreAddons.so.5 #11 0x7f318c6f369f in KCompositeJob::KCompositeJob(QObject*) () at /usr/lib64/libKF5CoreAddons.so.5 #12 0x7f31896772a6 in Akonadi::Job::Job(Akonadi::JobPrivate*, QObject*) (this=0x55caaf1d4490, dd=0x55cab92ee1a0, parent=0x55caaf83ea20) at /tmp/portage/kde-apps/akonadi-20.04.3/work/akonadi-20.04.3/src/core/jobs/job.cpp:304 #13 0x7f31896625a5 in Akonadi::CollectionFetchJob::CollectionFetchJob(Akonadi::Collection const&, Akonadi::CollectionFetchJob::Type, QObject*) (this=0x55caaf1d4490, collection=..., type=Akonadi::CollectionFetchJob::Base, parent=0x55caaf83ea20) at /usr/include/qt5/QtCore/qarraydata.h:257 #14 0x7f31895d4cd5 in Akonadi::EntityCache::createFetchJob(long long, Akonadi::CollectionFetchScope const&) (scope=..., id=, this=0x7f3118031ac0) at /tmp/portage/kde-apps/akonadi-20.04.3/work/akonadi-20.04.3/src/core/entitycache_p.h:274 #15 Akonadi::EntityCache::request(long long, Akonadi::CollectionFetchScope const&) (this=0x7f3118031ac0, id=, scope=...) at /tmp/portage/kde-apps/akonadi-20.04.3/work/akonadi-20.04.3/src/core/entitycache_p.h:174 #16 0x7f3189621d73 in Akonadi::EntityCache::ensureCached(long long, Akonadi::CollectionFetchScope const&) (scope=..., id=1881, this=) at /tmp/portage/kde-apps/akonadi-20.04.3/work/akonadi-20.04.3/src/core/entitycache_p.h:154 #17 Akonadi::EntityCache::ensureCached(long long, Akonadi::CollectionFetchScope const&) (scope=..., id=1881, this=) at /tmp/portage/kde-apps/akonadi-20.04.3/work/akonadi-20.04.3/src/core/entitycache_p.h:154 #18 Akonadi::MonitorPrivate::ensureDataAvailable(QSharedPointer const&) (this=0x55cab1958430, msg=...) at /tmp/portage/kde-apps/akonadi-20.04.3/work/akonadi-20.04.3/src/core/monitor_p.cpp:406 #19 0x7f3189622841 in Akonadi::MonitorPrivate::dispatchNotifications() (this=0x55cab1958430) at /tmp/portage/kde-apps/akonadi-20.04.3/work/akonadi-20.04.3/src/core/monitor_p.cpp:1001 #20 0x7f318b78bbf0 in doActivate(QObject*, int, void**) (sender=0x7f3118031ac0, signal_index=3, argv=0x7ffce568a170) at /tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #21 0x7f318b78bbf0 in doActivate(QObject*, int, void**) (sender=0x55caa6ee80c0, signal_index=6, argv=0x7ffce568a2b0) at /tmp/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #22 0x7f318c6f434c in KJob::result(KJob*, KJob::QPrivateSignal) () at /usr/lib64/libKF5CoreAddons.so.5 #23 0x7f318c6f4eab in KJob::finishJob(bool) () at /usr/lib64/libKF5CoreAddons.so.5 #24 0x7f318c6f4f2b in KJob::kill(KJob::KillVerbosity) () at /usr/lib64/libKF5CoreAddons.so.5 #25 0x7f3189648eb1 in Akonadi::SessionPrivate::clear(bool) (this=0x55caa7cc6690, forceReconnect=forceReconnect@entry=false) at /tmp/portage/kde-apps/akonadi-20.04.3/work/akonadi-20.04.3/src/core/session.cpp:427
[Akonadi] [Bug 423672] org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: ... NO Mailbox already exists ... [ ALREADYEXISTS ]"
https://bugs.kde.org/show_bug.cgi?id=423672 --- Comment #4 from Dennis Schridde --- (In reply to Christophe Giboudeaux from comment #3) > Please create a merge request: https://invent.kde.org/pim/kimap https://invent.kde.org/pim/kimap/-/merge_requests/3 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 423672] org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: ... NO Mailbox already exists ... [ ALREADYEXISTS ]"
https://bugs.kde.org/show_bug.cgi?id=423672 --- Comment #2 from Dennis Schridde --- Created attachment 129920 --> https://bugs.kde.org/attachment.cgi?id=129920=edit kimap-20.04.2-create-alreadyexists-is-not-an-error.patch Attached patch fixes the issue in in KIMAP 20.04.2 by making CREATE and DELETE idempotent. If CREATE fails with an ALREADYEXISTS response code, that is not an error since the intended result (the object existing at the target location) has been achieved. Likewise, if DELETE fails with an NONEXISTENT response code, that is not an error since the intended result (the object being gone from the target location) has been achieved. Please note that for RENAME response code ALREADYEXISTS *is* an error since the content of the source folder was not moved as intended. cf. https://tools.ietf.org/html/rfc5530#section-3 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 423681] New: Akonadi Console crashed upon close
https://bugs.kde.org/show_bug.cgi?id=423681 Bug ID: 423681 Summary: Akonadi Console crashed upon close Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: akonadiconsole Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadiconsole (5.13.2 (19.12.2)) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.6.19-300.fc32.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 32 (Thirty Two) -- Information about the crash: - What I was doing when the application crashed: I closed the Akonadi Console window and shortly thereafter received the information that it has crashed. -- Backtrace: Application: Akonadi Console (akonadiconsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4a0d1b2f00 (LWP 18792))] Thread 18 (Thread 0x7f496bfff700 (LWP 18875)): #0 0x7f4a1a384e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4a14264f4c in base::ConditionVariable::Wait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:75 #2 0x7f4a14265b14 in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:235 #3 0x7f4a14265c1f in base::WaitableEvent::Wait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:155 #4 0x7f4a1421f438 in base::internal::WorkerThread::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task/thread_pool/worker_thread.cc:33 #5 0x7f4a1422383b in base::internal::WorkerThread::RunWorker () at ./../../3rdparty/chromium/base/task/thread_pool/worker_thread.cc:317 #6 0x7f4a14223cf4 in base::internal::WorkerThread::RunSharedWorker () at ./../../3rdparty/chromium/base/task/thread_pool/worker_thread.cc:235 #7 0x7f4a14267f3a in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81 #8 0x7f4a1a37e432 in start_thread () from /lib64/libpthread.so.0 #9 0x7f4a1b6319d3 in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f49a0f4e700 (LWP 18873)): #0 0x7f4a1b626b6f in poll () from /lib64/libc.so.6 #1 0x7f49bc213246 in poll_func () from /lib64/libpulse.so.0 #2 0x7f49bc204991 in pa_mainloop_poll () from /lib64/libpulse.so.0 #3 0x7f49bc205013 in pa_mainloop_iterate () from /lib64/libpulse.so.0 #4 0x7f49bc2050c0 in pa_mainloop_run () from /lib64/libpulse.so.0 #5 0x7f49bc21331d in thread () from /lib64/libpulse.so.0 #6 0x7f49bc1af5cc in internal_thread_func () from /usr/lib64/pulseaudio/libpulsecommon-13.99.so #7 0x7f4a1a37e432 in start_thread () from /lib64/libpthread.so.0 #8 0x7f4a1b6319d3 in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f49a17fa700 (LWP 18861)): #0 0x7f4a1a384e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4a14264f4c in base::ConditionVariable::Wait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:75 #2 0x7f4a14265b14 in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:235 #3 0x7f4a14265c1f in base::WaitableEvent::Wait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:155 #4 0x7f4a1421f438 in base::internal::WorkerThread::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task/thread_pool/worker_thread.cc:33 #5 0x7f4a1422383b in base::internal::WorkerThread::RunWorker () at ./../../3rdparty/chromium/base/task/thread_pool/worker_thread.cc:317 #6 0x7f4a14223d34 in base::internal::WorkerThread::RunDedicatedWorker () at ./../../3rdparty/chromium/base/task/thread_pool/worker_thread.cc:247 #7 0x7f4a14267f3a in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81 #8 0x7f4a1a37e432 in start_thread () from /lib64/libpthread.so.0 #9 0x7f4a1b6319d3 in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f49a1ffb700 (LWP 18857)): #0 0x7f4a1a384e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4a14264f4c in base::ConditionVariable::Wait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:75 #2 0x7f4a14265b14 in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:235 #3 0x7f4a14265c1f in base::WaitableEvent::Wait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:155 #4 0x7f4a141c92e5 in base::MessagePumpDefault::Run () at ./../../3rdparty/chromium/base/message_loop/message_pump_default.cc:55 #5 0x7f4a1421029f in
[Akonadi] [Bug 418914] org.kde.pim.davresource: Error when uploading item: 400 "There was a problem with the request. The item has not been created on the server.\nThe file or folder dav.mailbox.org d
https://bugs.kde.org/show_bug.cgi?id=418914 --- Comment #1 from Dennis Schridde --- The log message changed: org.kde.pim.davresource: Error when uploading item: 420 "There was a problem with the request. The item was not modified on the server.\nThe file or folder dav.mailbox.org does not exist. (0)." akonadictl 5.13.2 (19.12.2) Operating System: Fedora 32 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.6.19-300.fc32.x86_64 OS Type: 64-bit Processors: 4 × Intel® Core™ m3-6Y30 CPU @ 0.90GHz Memory: 7,2 GiB of RAM -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 396663] Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418599 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418595] Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=396663 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418599] Crash when moving emails from one IMAP server to another
https://bugs.kde.org/show_bug.cgi?id=418599 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=396663 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418599] Crash when moving emails from one IMAP server to another
https://bugs.kde.org/show_bug.cgi?id=418599 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=423675 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418595] Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=423675 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418912] Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=423675 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418593] Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0
https://bugs.kde.org/show_bug.cgi?id=418593 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=423675 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 396663] Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=423675 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 423675] Akonadi IMAP resource crashes immediately when synchronising IMAP account
https://bugs.kde.org/show_bug.cgi?id=423675 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418912, ||https://bugs.kde.org/show_b ||ug.cgi?id=418593, ||https://bugs.kde.org/show_b ||ug.cgi?id=396663, ||https://bugs.kde.org/show_b ||ug.cgi?id=418595, ||https://bugs.kde.org/show_b ||ug.cgi?id=418599 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 396663] Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418595 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418593] Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0
https://bugs.kde.org/show_bug.cgi?id=418593 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=396663 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418912] Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=396663 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 396663] Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418912 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 396663] Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418593 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 423675] New: Akonadi IMAP resource crashes immediately when synchronising IMAP account
https://bugs.kde.org/show_bug.cgi?id=423675 Bug ID: 423675 Summary: Akonadi IMAP resource crashes immediately when synchronising IMAP account Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadi_imap_resource (5.13.2 (19.12.2)) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.6.19-300.fc32.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 32 (Thirty Two) -- Information about the crash: - What I was doing when the application crashed: * In KMail I trigger a sync of one of my IMAP accounts - The fetch mail button at the top left, where I can select an account by long-clicking it, has no effect - Thus I right-click on the IMAP account in the folder view and click "update folder and sub-folders" * I immediately receive a crash report of the associated Akonadi IMAP resource This problem has been reproducible since a long time and since several versions / through several updates of KDE / Akonadi for this specific account. The crash can be reproduced every time. -- Backtrace: Application: Mailbox.org (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffa145a59c0 (LWP 4541))] Thread 10 (Thread 0x7ff9e25ed700 (LWP 5168)): #0 0x7ffa214d4406 in qt_gettime() () at kernel/qelapsedtimer_unix.cpp:173 #1 0x7ffa214d2d5d in QTimerInfoList::updateCurrentTime() (this=this@entry=0x7ff9d4004260) at kernel/qtimerinfo_unix.cpp:91 #2 0x7ffa214d31a9 in QTimerInfoList::timerWait(timespec&) (this=0x7ff9d4004260, tm=...) at kernel/qtimerinfo_unix.cpp:388 #3 0x7ffa214d48be in timerSourcePrepareHelper (timeout=0x7ff9e25eca04, src=) at kernel/qeventdispatcher_glib.cpp:162 #4 timerSourcePrepare(GSource*, gint*) (source=, timeout=0x7ff9e25eca04) at kernel/qeventdispatcher_glib.cpp:166 #5 0x7ffa1f726fe2 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #6 0x7ffa1f7279fb in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #7 0x7ffa1f727c03 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #8 0x7ffa214d4b8b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7ff9d4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #9 0x7ffa2148791b in QEventLoop::exec(QFlags) (this=this@entry=0x7ff9e25ecbe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #10 0x7ffa212f3427 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #11 0x7ffa212f4690 in QThreadPrivate::start(void*) (arg=0x560f8d472150) at thread/qthread_unix.cpp:342 #12 0x7ffa205b3432 in start_thread () at /lib64/libpthread.so.0 #13 0x7ffa20f5a9d3 in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7ff9e35ef700 (LWP 4697)): #0 0x7ffa20f4fb6f in poll () at /lib64/libc.so.6 #1 0x7ffa1f727ace in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #2 0x7ffa1f727c03 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7ffa214d4b8b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7ff9d8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7ffa2148791b in QEventLoop::exec(QFlags) (this=this@entry=0x7ff9e35eebe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7ffa212f3427 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7ffa212f4690 in QThreadPrivate::start(void*) (arg=0x560f8d26b8b0) at thread/qthread_unix.cpp:342 #7 0x7ffa205b3432 in start_thread () at /lib64/libpthread.so.0 #8 0x7ffa20f5a9d3 in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7ff9f8a98700 (LWP 4653)): #0 0x7ffa20f4fb6f in poll () at /lib64/libc.so.6 #1 0x7ffa1f727ace in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #2 0x7ffa1f727c03 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7ffa214d4b8b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7ff9dc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7ffa2148791b in QEventLoop::exec(QFlags) (this=this@entry=0x7ff9f8a97be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7ffa212f3427 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7ffa212f4690 in QThreadPrivate::start(void*) (arg=0x560f8d265e40) at thread/qthread_unix.cpp:342 #7 0x7ffa205b3432 in start_thread () at /lib64/libpthread.so.0 #8 0x7ffa20f5a9d3 in clone () at /lib64/libc.so.6 Thread 7 (Thread
[Akonadi] [Bug 423672] org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: ... NO Mailbox already exists ... [ ALREADYEXISTS ]"
https://bugs.kde.org/show_bug.cgi?id=423672 --- Comment #1 from Dennis Schridde --- P.S. Expected behaviour on code-level: When the error is ALREADYEXISTS, Akonadi should consider the creation of the mailbox successful and continue the sync, i.e. mailbox creation should be idempotent. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 423672] New: org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: ... NO Mailbox already exists ... [ ALREADYEXISTS ]"
https://bugs.kde.org/show_bug.cgi?id=423672 Bug ID: 423672 Summary: org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: ... NO Mailbox already exists ... [ ALREADYEXISTS ]" Product: Akonadi Version: 5.14.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- SUMMARY It appears that the Akonadi IMAP resource aborts synchronisation with a server if a mailbox it is supposed to create already exists: When I try to synchronise one of my IMAP accounts from KMail, the synchronisation quickly aborts and on the console where ran `akonadictl restart` I see: org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: A000239 NO Mailbox already exists ( 0.001 + 0.000 secs ) . [ ALREADYEXISTS ]" It could be that the mailbox was created through another Akonadi IMAP resource on another computer, or it could have been created by the same Akonadi IMAP resource on this computer, but with it crashing during the sync. For examples of reports of the latter, see these bugs: * bug #418593 * bug #418595 * bug #418599 * bug #418912 STEPS TO REPRODUCE (assumption) 1. Create a new folder for an IMAP account using an Akonadi client 2. Have Akonadi go out of sync with the IMAP server 3. Have the folder already on the IMAP server, e.g. due to an incomplete sync 4. Try to synchronise the Akonadi IMAP resource with that same server OBSERVED RESULT * org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: A000239 NO Mailbox already exists ( 0.001 + 0.000 secs ) . [ ALREADYEXISTS ]" * Emails are not being synchronised to my computer EXPECTED RESULT * No error output in the console where I started `akonadictl restart` * Synchronisation with the IMAP server succeeds and the freshest emails are available for me on my computer SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 Kernel Version: 5.7.6 OS Type: 64-bit Processors: 8 × AMD Ryzen 5 2400G with Radeon Vega Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD RAVEN ADDITIONAL INFORMATION Portage 2.3.103 (python 3.6.9-final-0, default/linux/amd64/17.1/desktop/plasma/systemd, gcc-10.1.0, glibc-2.31-r5, 5.7.6 x86_64) = System uname: Linux-5.7.6-x86_64-AMD_Ryzen_5_2400G_with_Radeon_Vega_Graphics-with-gentoo-2.7 KiB Mem:14128436 total,627308 free KiB Swap: 0 total, 0 free Timestamp of repository gentoo: Mon, 29 Jun 2020 19:45:01 + Head commit of repository gentoo: 394fae18295de1e22d897cd0ad31b1dc5b3ca6b0 Head commit of repository flatpak-overlay: 35c52dcaeffa51a7b3c681c5ade8a6f0978e3d54 Head commit of repository local: 4efaf55c4086be09ab650f5ae4137e8eeae4dbb5 sh bash 5.0_p17 ld GNU gold (Gentoo 2.34 p4 2.34.0) 1.16 ccache version 3.7.10 [disabled] app-shells/bash: 5.0_p17::gentoo dev-java/java-config: 2.3.1::gentoo dev-lang/perl:5.30.3-r1::gentoo dev-lang/python: 2.7.18::gentoo, 3.6.10-r2::gentoo, 3.7.8::gentoo, 3.8.3::gentoo, 3.9.0_beta3::gentoo dev-util/ccache: 3.7.10::gentoo dev-util/cmake: 3.17.3::gentoo dev-util/pkgconfig: 0.29.2::gentoo sys-apps/baselayout: 2.7::gentoo sys-apps/sandbox: 2.20::gentoo sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r5::gentoo sys-devel/automake: 1.13.4-r2::gentoo, 1.16.2::gentoo sys-devel/binutils: 2.34-r1::gentoo sys-devel/gcc:10.1.0-r1::gentoo sys-devel/gcc-config: 2.3.1::gentoo sys-devel/libtool:2.4.6-r6::gentoo sys-devel/make: 4.3::gentoo sys-kernel/linux-headers: 5.7::gentoo (virtual/os-headers) sys-libs/glibc: 2.31-r5::gentoo Repositories: gentoo location: /var/cache/portage/gentoo sync-type: rsync sync-uri: rsync://rsync.de.gentoo.org/gentoo-portage priority: -1000 sync-rsync-extra-opts: --new-compress sync-rsync-verify-jobs: 1 sync-rsync-verify-max-age: 24 sync-rsync-verify-metamanifest: yes flatpak-overlay location: /var/db/repos/flatpak-overlay sync-type: git sync-uri: https://github.com/fosero/flatpak-overlay.git masters: gentoo crossdev location: /var/cache/portage/crossdev masters: gentoo priority: 100 local location: /var/cache/portage/local sync-type: git sync-uri: https://github.com/devurandom/gentoo-overlay.git masters: gentoo priority: 1000 ACCEPT_KEYWORDS="amd64 ~amd64" ACCEPT_LICENSE="@FREE" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-pipe -O2 -march=znver1" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /etc/grs/systems.conf
[kmail2] [Bug 420390] New: KMail crashed on startup in Wayland
https://bugs.kde.org/show_bug.cgi?id=420390 Bug ID: 420390 Summary: KMail crashed on startup in Wayland Product: kmail2 Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: kmail (5.13.3 (19.12.3)) Qt Version: 5.14.2 Frameworks Version: 5.69.0 Operating System: Linux 5.6.5 x86_64 Windowing system: Wayland Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed:Shortly after start KMail crashed when running it on Wayland / Sway WM 1.4 -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa4462e9dc0 (LWP 214569))] Thread 47 (Thread 0x7fa34e7cf700 (LWP 217106)): #0 0x7fa45b6d277f in poll () at /usr/lib64/libc.so.6 #1 0x7fa45841f43e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa45841f55f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa45bd07f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fa34b60, flags=...) at /tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa45bcb06eb in QEventLoop::exec(QFlags) (this=this@entry=0x7fa34e7ce7e0, flags=..., flags@entry=...) at /tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7fa45bafadfe in QThread::exec() (this=) at /tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7fa45bafbe5f in QThreadPrivate::start(void*) (arg=0x5634810ecc70) at /tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/src/corelib/thread/qthread_unix.cpp:342 #7 0x7fa458e5b02a in start_thread () at /usr/lib64/libpthread.so.0 #8 0x7fa45b6dd26f in clone () at /usr/lib64/libc.so.6 Thread 46 (Thread 0x7fa34700 (LWP 216730)): #0 0x7fa458e61957 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fa45298a51c in base::ConditionVariable::Wait() () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x in () Thread 45 (Thread 0x7fa365b0a700 (LWP 216657)): #0 0x7fa458e61957 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fa444c8b63b in cnd_wait (mtx=0x56347d7ea8e8, cond=0x56347d7ea910) at ../mesa-20.0.4/include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x56347d7045b0) at ../mesa-20.0.4/src/util/u_queue.c:275 #3 0x7fa444c8b247 in impl_thrd_routine (p=) at ../mesa-20.0.4/include/c11/threads_posix.h:87 #4 0x7fa458e5b02a in start_thread () at /usr/lib64/libpthread.so.0 #5 0x7fa45b6dd26f in clone () at /usr/lib64/libc.so.6 Thread 44 (Thread 0x7fa36630b700 (LWP 216655)): #0 0x7fa458e61957 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7fa444c8b63b in cnd_wait (mtx=0x56347d755698, cond=0x56347d7556c0) at ../mesa-20.0.4/include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x56347d702fb0) at ../mesa-20.0.4/src/util/u_queue.c:275 #3 0x7fa444c8b247 in impl_thrd_routine (p=) at ../mesa-20.0.4/include/c11/threads_posix.h:87 #4 0x7fa458e5b02a in start_thread () at /usr/lib64/libpthread.so.0 #5 0x7fa45b6dd26f in clone () at /usr/lib64/libc.so.6 Thread 43 (Thread 0x7fa367fff700 (LWP 216637)): #0 0x7fa45b6d7d59 in syscall () at /usr/lib64/libc.so.6 #1 0x7fa45bafdf88 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long long, int*, int) (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at /tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/src/corelib/thread/qfutex_p.h:133 #2 QtLinuxFutex::futexWait >(QBasicAtomicInteger&, QBasicAtomicInteger::Type) (expectedValue=, futex=...) at /tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/src/corelib/thread/qfutex_p.h:135 #3 futexSemaphoreTryAcquire_loop(QBasicAtomicInteger&, unsigned long long, unsigned long long, int) (timeout=-1, nn=8589934593, curValue=, u=...) at /tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/src/corelib/thread/qsemaphore.cpp:219 #4 futexSemaphoreTryAcquire(QBasicAtomicInteger&, int, int) (u=..., n=n@entry=1, timeout=timeout@entry=-1) at /tmp/portage/dev-qt/qtcore-5.14.2/work/qtbase-everywhere-src-5.14.2/src/corelib/thread/qsemaphore.cpp:262 #5 0x7fa45bafddea in QSemaphore::acquire(int) (this=this@entry=0x7fa459543660 <(anonymous namespace)::Q_QGS_libProxyWrapper::innerFunction()::holder+32>, n=n@entry=1) at
[Akonadi] [Bug 418912] Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 --- Comment #3 from Dennis Schridde --- Created attachment 126951 --> https://bugs.kde.org/attachment.cgi?id=126951=edit New crash information added by DrKonqi akonadi_imap_resource (5.13.2 (19.12.2)) using Qt 5.13.2 - What I was doing when the application crashed: The issue persists in Fedora 32: Akonadi IMAP resource for this account is still in a crash loop. -- Backtrace (Reduced): #6 0x7f55cc0216f0 in () [...] #8 0x7f5609aa18a6 in Akonadi::ResourceScheduler::executeNext() () at /lib64/libKF5AkonadiAgentBase.so.5 #9 0x7f5608211456 in QSingleShotTimer::timerEvent(QTimerEvent*) () at /lib64/libQt5Core.so.5 #10 0x7f56082062cf in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #11 0x7f5608c6de66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418912] Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418593] Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0
https://bugs.kde.org/show_bug.cgi?id=418593 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418593] Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0
https://bugs.kde.org/show_bug.cgi?id=418593 --- Comment #1 from Dennis Schridde --- Created attachment 126948 --> https://bugs.kde.org/attachment.cgi?id=126948=edit New crash information added by DrKonqi akonadi_imap_resource (5.13.2 (19.12.2)) using Qt 5.13.2 - What I was doing when the application crashed: The issue persists in Fedora 32. [..] -- Backtrace (Reduced): #6 0x7f212c0232e0 in () [...] #8 0x7f21678ed8a6 in Akonadi::ResourceScheduler::executeNext() () at /lib64/libKF5AkonadiAgentBase.so.5 #9 0x7f216605d456 in QSingleShotTimer::timerEvent(QTimerEvent*) () at /lib64/libQt5Core.so.5 #10 0x7f21660522cf in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #11 0x7f2166ab9e66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418914] New: org.kde.pim.davresource: Error when uploading item: 400 "There was a problem with the request. The item has not been created on the server.\nThe file or folder dav.mailbox.
https://bugs.kde.org/show_bug.cgi?id=418914 Bug ID: 418914 Summary: org.kde.pim.davresource: Error when uploading item: 400 "There was a problem with the request. The item has not been created on the server.\nThe file or folder dav.mailbox.org does not exist. (0)." Product: Akonadi Version: 5.11.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- SUMMARY CalDAV event synchronisation appears to be impaired. It seems as if Akonadi DAV resource puts the hostname in odd locations in the CalDAV query. STEPS TO REPRODUCE 1. Setup DAV groupware / CalDAV synchronisation with your mailbox.org account 2. Create events on your computer OBSERVED RESULT `akonadictl restart` outputs: org.kde.pim.davresource: Error when uploading item: 400 "There was a problem with the request. The item has not been created on the server.\nThe file or folder dav.mailbox.org does not exist. (0)." Some events in my calendar do not appear to be synchronised with the CalDAV server. EXPECTED RESULT Events are synchronised and there is no output from `akonadictl restart`. SOFTWARE/OS VERSIONS Linux: 5.5.8, via Fedora 31 KDE Plasma Version: 5.17.5 KDE Applications Version: 19.04.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418912] Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 --- Comment #2 from Dennis Schridde --- Notable output from `akonadictl restart`: org.kde.pim.akonadicontrol: ProcessControl: Application '/usr/bin/akonadi_imap_resource' returned with exit code 253 (Unknown error) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fcea00aa130) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fcea00aa130) identified as "AgentBaseChangeRecorder - 94682505928208" org.kde.pim.akonadiserver: Error while handling command FetchCollections on connection akonadi_imap_resource_0 (0x55948b647ce0) It is not easy to figure out, but I believe that akonadi_imap_resource_0 is the resource for the 2nd IMAP server, the same one that is segfaulting constantly. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418912] Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 --- Comment #1 from Dennis Schridde --- Created attachment 126824 --> https://bugs.kde.org/attachment.cgi?id=126824=edit akonadi_imap_resource-20200316-102944.kcrash.txt -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 396663] Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 --- Comment #9 from Dennis Schridde --- (In reply to Dennis Schridde from comment #8) > Bug #418593, bug #418595, bug #418599 might be related, as they appeared in > a similar context bug #418912 might also be roughly related. Note that all my crashes are segfaults, while this crash here (bug #396663) is an abort. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418599] Crash when moving emails from one IMAP server to another
https://bugs.kde.org/show_bug.cgi?id=418599 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418912 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418595] Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418912 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418912] Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418599 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418593] Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0
https://bugs.kde.org/show_bug.cgi?id=418593 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418912 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418912] Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418595 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418912] Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418593 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418912] New: Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 Bug ID: 418912 Summary: Akonadi IMAP resource in crash loop after moving and deleting folder Product: Akonadi Version: 5.11.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- SUMMARY Akonadi IMAP resource constantly crashes, is being restarted, crashes, etc. `akonadictl restart` does not help. STEPS TO REPRODUCE 1. Move a mail folder from one IMAP server to another 2. See in KMail (expand the progress bar in the bottom right corner) that the Akonadi IMAP resource for the 2nd server got stuck in "Creating folder" 3. Sync the first server again 4. Notice that the folder reappeared there 5. Move all content from the 2nd server's folder back to the 1st 6. Delete now-empty folder on the 2nd server OBSERVED RESULT * Akonadi IMAP resource for the 2nd server got stuck in "Creating folder" after moving folder * Akonadi IMAP resource goes into crash loop after deleting folder EXPECTED RESULT Akonadi is rock stable and handles the moving and deletion of folders and content gracefully SOFTWARE/OS VERSIONS Linux: 5.5.8, via Fedora 31 KDE Plasma Version: 5.17.5 KDE Applications Version: 19.04.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 396663] Imap resource crashes when large amounts of emails is moved/deleted
https://bugs.kde.org/show_bug.cgi?id=396663 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net --- Comment #8 from Dennis Schridde --- Bug #418593, bug #418595, bug #418599 might be related, as they appeared in a similar context -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418595] Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418599 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418599] Crash when moving emails from one IMAP server to another
https://bugs.kde.org/show_bug.cgi?id=418599 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418595 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418593] Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0
https://bugs.kde.org/show_bug.cgi?id=418593 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418599 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418599] Crash when moving emails from one IMAP server to another
https://bugs.kde.org/show_bug.cgi?id=418599 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418593 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]
https://bugs.kde.org/show_bug.cgi?id=339214 --- Comment #26 from Dennis Schridde --- Just ran into this again using: * KMail 5.13.3 (19.12.3) * KDE Frameworks 5.67.0 * Qt 5.14.1 (built against 5.14.1) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418599] New: Crash when moving emails from one IMAP server to another
https://bugs.kde.org/show_bug.cgi?id=418599 Bug ID: 418599 Summary: Crash when moving emails from one IMAP server to another Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadi_imap_resource (5.13.3 (19.12.3)) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.8 x86_64 Windowing system: X11 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: I moved 34 (contents of folder "a") and then another 40 (contents of folder "b") emails from one IMAP server to another. - Unusual behavior I noticed: First my Akonadi IMAP resource stopped syncing (bug #418593), then I deleted and recreated it, but it stopped connecting to the server after a while (bug #418595), then I recreated it again and am now running into this problem here. -- Backtrace: Application: Kynes (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8125eefd80 (LWP 275208))] Thread 24 (Thread 0x7f80c9dec700 (LWP 331976)): #0 0x7f8137e13d7d in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7f8138cb2205 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (this=0x7f80b80109a0, deadline=...) at thread/qwaitcondition_unix.cpp:136 #2 QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x7f80b80109a0) at thread/qwaitcondition_unix.cpp:144 #3 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x7f80b8010b88, deadline=...) at thread/qwaitcondition_unix.cpp:225 #4 0x7f8138cb2307 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x7f80b8011a80, mutex=mutex@entry=0x7f80b8010b88, time=) at thread/qwaitcondition_unix.cpp:209 #5 0x7f8138cb015b in QThreadPoolThread::run() (this=0x7f80b8011a70) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:270 #6 0x7f8138caccef in QThreadPrivate::start(void*) (arg=0x7f80b8011a70) at thread/qthread_unix.cpp:342 #7 0x7f8137e0c42a in start_thread () at /usr/lib64/libpthread.so.0 #8 0x7f813886c42f in clone () at /usr/lib64/libc.so.6 Thread 23 (Thread 0x7f80ca5ed700 (LWP 331975)): #0 0x7f8136fb6b04 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f8136f6807b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8136f68a53 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8136f68c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8138eb889b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f80b006d480, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f8138e6101b in QEventLoop::exec(QFlags) (this=this@entry=0x7f80ca5ec820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f8138cabc8e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f8138caccef in QThreadPrivate::start(void*) (arg=0x55fd085546d0) at thread/qthread_unix.cpp:342 #8 0x7f8137e0c42a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7f813886c42f in clone () at /usr/lib64/libc.so.6 Thread 22 (Thread 0x7f80cadee700 (LWP 275243)): #0 0x7f81388600db in poll () at /usr/lib64/libc.so.6 #1 0x7f8136f68b2e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8136f68c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8138eb889b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f80b8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8138e6101b in QEventLoop::exec(QFlags) (this=this@entry=0x7f80caded820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f8138cabc8e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f8138caccef in QThreadPrivate::start(void*) (arg=0x55fd07c250d0) at thread/qthread_unix.cpp:342 #7 0x7f8137e0c42a in start_thread () at /usr/lib64/libpthread.so.0 #8 0x7f813886c42f in clone () at /usr/lib64/libc.so.6 Thread 21 (Thread 0x7f80cb5ef700 (LWP 275242)): #0 0x7f81388600db in poll () at /usr/lib64/libc.so.6 #1 0x7f8136f68b2e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8136f68c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8138eb889b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f80cb60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8138e6101b in QEventLoop::exec(QFlags) (this=this@entry=0x7f80cb5ee820, flags=..., flags@entry=...) at
[Akonadi] [Bug 418595] Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595
--- Comment #2 from Dennis Schridde ---
I ran `akonadictl restart`, but that was a bumpy ride:
org.kde.pim.akonadicontrol: ProcessControl: Application
"/usr/bin/akonadiserver" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' crashed. No
restart!
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
❯ akonadictl restart
Akonadi is not running.
❯ akonadictl start
org.kde.pim.akonadicontrol: Service org.freedesktop.Akonadi.Control.lock
already registered, terminating now.
Error: akonadi_control was started but didn't register at D-Bus session bus.
Make sure your system is set up correctly!
❯ ps aux | rg akonadi
dschrid+ 246610 10.6 1.5 851584 225956 ? Sl 21:04 4:17
/usr/sbin/mysqld
--defaults-file=/home/dschridde/.local/share/akonadi/mysql.conf
--datadir=/home/dschridde/.local/share/akonadi/db_data/
--socket=/run/user/1000/akonadi/mysql.socket
--pid-file=/run/user/1000/akonadi/mysql.pid
dschrid+ 249132 0.3 1.0 3450644 153252 ? Sl 21:08 0:08
/usr/bin/akonadiconsole
dschrid+ 265348 0.0 0.0 10568 5860 ?S21:44 0:00
/usr/bin/mysqladmin
--defaults-file=/home/dschridde/.local/share/akonadi/mysql.conf
--socket=/run/user/1000/akonadi/mysql.socket shutdown
dschrid+ 265363 0.2 0.3 431516 43944 ?Sl 21:44 0:00
/usr/bin/akonadi_control
dschrid+ 265394 0.1 0.1 167704 24844 ?Sl 21:44 0:00
/usr/bin/akonadiserver
dschrid+ 265399 0.3 0.1 67932 19096 ?Sl 21:44 0:00
/usr/sbin/mysqld
--defaults-file=/home/dschridde/.local/share/akonadi/mysql.conf
--datadir=/home/dschridde/.local/share/akonadi/db_data/
--socket=/run/user/1000/akonadi/mysql.socket
--pid-file=/run/user/1000/akonadi/mysql.pid
dschrid+ 265735 0.0 0.0 5384 8 pts/6D+ 21:44 0:00 rg akonadi
❯ akonadictl status
Akonadi Control: stopped
Akonadi Server: stopped
Akonadi Server Search Support: available (Remote Search, Akonadi Search Plugin)
Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent,
akonadi_birthdays_resource, akonadi_contacts_resource,
akonadi_davgroupware_resource, akonadi_ews_resource, akonadi_ewsmta_resource,
akonadi_followupreminder_agent, akonadi_googlecalendar_resource,
akonadi_googlecontacts_resource, akonadi_ical_resource,
akonadi_icaldir_resource, akonadi
_imap_resource, akonadi_indexing_agent, akonadi_kalarm_dir_resource,
akonadi_kalarm_resource, akonadi_knut_resource, akonadi_maildir_resource,
akonadi_maildispatcher_agent, akonadi_mailfilter_agent, akonadi_mbox_resource,
akonadi_migration_agent, akonadi_mixedmaildir_resource,
akonadi_newmailnotifier_agent, akonadi_notes_agent, akonadi_notes_resource,
akonadi_op
enxchange_resource, akonadi_pop3_resource, akonadi_sendlater_agent,
akonadi_tomboynotes_resource, akonadi_unifiedmailbox_agent,
akonadi_vcard_resource, akonadi_vcarddir_resource
After I while I saw output from `akonadictl restart` (I presume):
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial
connection!
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld"
org.kde.pim.akonadiserver: arguments:
("--defaults-file=/home/dschridde/.local/share/akonadi/mysql.conf",
"--datadir=/home/dschridde/.local/share/akonadi/db_data/",
"--socket=/run/user/1000/akonadi/mysql.socket",
"--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2020-03-07 21:44:20 0 [Note]
/usr/sbin/mysqld (mysqld 10.4.12-MariaDB) starting as process 265399 ...\n"
org.kde.pim.akonadiserver: exit code: 1
[Akonadi] [Bug 418593] Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0
https://bugs.kde.org/show_bug.cgi?id=418593 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418595 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418595] New: Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595 Bug ID: 418595 Summary: Akonadi IMAP resource crashed after it lost connection and I tried to restart it Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadi_imap_resource (5.13.3 (19.12.3)) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.8 x86_64 Windowing system: X11 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: I set up a new Akonadi IMAP resource (for a server that I had previously set up, but I had to delete the Akonadi IMAP resource for it, because it stopped synchronising), after synchronising a few folders the resource put out a lot of messages of not being able to create connections to the server and then stopped doing anything. I tried to restart it, after which it still said "Unable to connect to the IMAP server". I tried to restart it again, and it crashed. -- Backtrace: Application: Kynes (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f83d0b28d80 (LWP 266490))] Thread 24 (Thread 0x7f8363f7d700 (LWP 273498)): #0 0x7f83e2a4cd7d in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib64/libpthread.so.0 #1 0x7f83e38eb205 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (this=0x7f83640109a0, deadline=...) at thread/qwaitcondition_unix.cpp:136 #2 QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x7f83640109a0) at thread/qwaitcondition_unix.cpp:144 #3 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x7f8364010b88, deadline=...) at thread/qwaitcondition_unix.cpp:225 #4 0x7f83e38eb307 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x7f8364011a80, mutex=mutex@entry=0x7f8364010b88, time=) at thread/qwaitcondition_unix.cpp:209 #5 0x7f83e38e915b in QThreadPoolThread::run() (this=0x7f8364011a70) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:270 #6 0x7f83e38e5cef in QThreadPrivate::start(void*) (arg=0x7f8364011a70) at thread/qthread_unix.cpp:342 #7 0x7f83e2a4542a in start_thread () at /usr/lib64/libpthread.so.0 #8 0x7f83e34a542f in clone () at /usr/lib64/libc.so.6 Thread 23 (Thread 0x7f83c0ed6700 (LWP 273497)): #0 0x7f83e1befb04 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f83e1ba107b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f83e1ba1a53 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f83e1ba1c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f83e3af189b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f836406e810, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f83e3a9a01b in QEventLoop::exec(QFlags) (this=this@entry=0x7f83c0ed5820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f83e38e4c8e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f83e38e5cef in QThreadPrivate::start(void*) (arg=0x564e8a81a920) at thread/qthread_unix.cpp:342 #8 0x7f83e2a4542a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7f83e34a542f in clone () at /usr/lib64/libc.so.6 Thread 22 (Thread 0x7f83a97fa700 (LWP 267813)): #0 0x7f83e1befad9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f83e1ba1095 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f83e1ba1a53 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f83e1ba1c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f83e3af189b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f8368002e90, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f83e3a9a01b in QEventLoop::exec(QFlags) (this=this@entry=0x7f83a97f9820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f83e38e4c8e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f83e38e5cef in QThreadPrivate::start(void*) (arg=0x564e8abd57d0) at thread/qthread_unix.cpp:342 #8 0x7f83e2a4542a in start_thread () at /usr/lib64/libpthread.so.0 #9 0x7f83e34a542f in clone () at /usr/lib64/libc.so.6 Thread 21 (Thread 0x7f83c16f4700 (LWP 266819)): #0 0x7f83e34990db in poll () at /usr/lib64/libc.so.6 #1 0x7f83e1ba1b2e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f83e1ba1c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f83e3af189b in QEventDispatcherGlib::processEvents(QFlags)
[Akonadi] [Bug 418595] Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595 --- Comment #1 from Dennis Schridde --- > because it stopped synchronising That issue is described in bug #418593. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418595] Akonadi IMAP resource crashed after it lost connection and I tried to restart it
https://bugs.kde.org/show_bug.cgi?id=418595 Dennis Schridde changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418593 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 418593] New: Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0
https://bugs.kde.org/show_bug.cgi?id=418593 Bug ID: 418593 Summary: Akonadi IMAP crashed while moving mails after: Error while handling command FetchCollections on connection akonadi_imap_resource_0 Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadi_imap_resource (5.13.3 (19.12.3)) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.8 x86_64 Windowing system: X11 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: 1. I moved a bunch of emails from "one" IMAP server to "another" using KMail 2. (I tried to move two folders "a" and "b" with the new emails from "another" into a "third" \NoSelect folder (as a new child) on the "one" server, which KMail does not allow me to do, I cannot even drop the folder there) 3. (That is IIRC an issue in KMail related to \NoSelect, so I ran `create "third"`, which succeeded.) 4. (After clicking "Check Mail" in KMail or "Synchronise All" in Akonadi Console, KMail still displays the "third" folder as greyed-out and does not allow me to move folders into it.) 5. I moved both folders "a" and "b" to the top level of the "one" IMAP server 6. Using another IMAP client (`gnutls-cli`) I ran `rename "a" "third/a"` on the "one" IMAP server 7. Also using that other IMAP client, I tried to rename "b" to "third/b", but the "one" IMAP server replied "NO [NONEXISTENT]" 8. Also using that other IMAP client, I ran `create "third/b"`, which succeeded 9. Coming back to KMail, it still displays "a" and "b" at the root level of the "one" IMAP server, "third/a" also exists, but "third/b" does not 10. "Check Mail" in KMail or "Synchronise All" in Akonadi Console do not fix this 11. KMail displayed "a" on "another" IMAP server as empty, so I deleted it 12. KMail displayed "b" on "another" IMAP server as non-empty, so I kept it 13. Using KMail I moved the emails from "b" in the top level of the "one" IMAP server back to the folder on "another" IMAP server 14. Also using KMail I moved the folder "a" from the "one" IMAP server back to "another" IMAP server 15. I also used KMail to move the emails from "third/a" on "one" IMAP server back into folder "a" on "another" IMAP server - Unusual behavior I noticed: When running `akonadictl restart` or restarting the Akonadi IMAP Account, I see the following in the output: > Error while handling command FetchCollections on connection > akonadi_imap_resource_0 - Status afterwards / the problem: The Akonadi IMAP account for the "one" IMAP server does not synchronise at all anymore. When clicking "Check Mail > one IMAP server" in KMail nothing happens. The agent status as displayed by Akonadi Console does not change either. Additionally I can "sometimes" make the Akonadi IMAP resource crash. I am not yet sure what exactly I need to do to make it crash. I am a bit afraid of the state of my emails and what would happen if I was to delete the "one" IMAP server account in Akonadi and would recreate it. - Wild guess: Akonadi IMAP does not handle it very well when other IMAP clients are fiddling with the mailboxes (create, delete, rename) while it itself is moving mailboxes around. The crash can be reproduced sometimes. -- Backtrace: Application: Kynes (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f62b4cf7d80 (LWP 250421))] Thread 23 (Thread 0x7f6260a09700 (LWP 250488)): #0 0x7f62c76636f8 in read () at /usr/lib64/libc.so.6 #1 0x7f62c5dba51f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f62c5d70657 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f62c5d70ad3 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f62c5d70c4f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f62c7cc089b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f624b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f62c7c6901b in QEventLoop::exec(QFlags) (this=this@entry=0x7f6260a08820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #7 0x7f62c7ab3c8e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #8 0x7f62c7ab4cef in QThreadPrivate::start(void*) (arg=0x5646bf81cda0) at thread/qthread_unix.cpp:342 #9 0x7f62c6c1442a in start_thread () at /usr/lib64/libpthread.so.0 #10 0x7f62c767442f in clone () at /usr/lib64/libc.so.6 Thread 22 (Thread 0x7f62615eb700 (LWP 250444)): #0 0x7f62c6c1bd7d in
[kresources] [Bug 126191] Kontact displays Open-Xchange URLs with password in them
https://bugs.kde.org/show_bug.cgi?id=126191 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net --- Comment #3 from Dennis Schridde --- The resource is currently entirely broken for many users, see bug #353286. Could you please confirm that this issue still exists for you? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 381530] Akonadi OpenXchange Resource seems to be broken
https://bugs.kde.org/show_bug.cgi?id=381530 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net --- Comment #1 from Dennis Schridde --- Persists with KDE Frameworks 5.66.0, KDE Plasma 5.17.5, KDE Applications 19.04.3, Akonadi 1.13.0 on Fedora 31. Could be a duplicate of bug #353286. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 353286] Openxchange calender not showing up in KOrganizer
https://bugs.kde.org/show_bug.cgi?id=353286 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net --- Comment #9 from Dennis Schridde --- Persists with KDE Frameworks 5.66.0, KDE Plasma 5.17.5, KDE Applications 19.04.3, Akonadi 1.13.0 on Fedora 31. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415403] kmail2 5.13.1 (19.12.1) with QtWebEngine 5.14.1 - segfault in KMReaderWin::KMReaderWin on startup
https://bugs.kde.org/show_bug.cgi?id=415403 --- Comment #5 from Dennis Schridde --- (In reply to Dennis Schridde from comment #3) > Created attachment 125528 [details] > gdb full backtrace, kmail 5.13.1 (19.12.1), qtwebengine 5.14.1 > > Persists with QtWebEngine 5.14.1, too. I am still using the same versions, but can now start KMail again. Maybe some dependency had a bug? Denis Lisov, is the issue resolved on your side, too? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415403] kmail2 5.13.0 (19.12.0) with QtWebEngine 5.14.0 - segfault in KMReaderWin::KMReaderWin on startup
https://bugs.kde.org/show_bug.cgi?id=415403 Dennis Schridde changed: What|Removed |Added Attachment #125528|application/octet-stream|text/plain mime type|| -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415403] kmail2 5.13.1 (19.12.1) with QtWebEngine 5.14.1 - segfault in KMReaderWin::KMReaderWin on startup
https://bugs.kde.org/show_bug.cgi?id=415403 Dennis Schridde changed: What|Removed |Added Version|5.13.0 |5.13.1 Summary|kmail2 5.13.0 (19.12.0) |kmail2 5.13.1 (19.12.1) |with QtWebEngine 5.14.0 - |with QtWebEngine 5.14.1 - |segfault in |segfault in |KMReaderWin::KMReaderWin on |KMReaderWin::KMReaderWin on |startup |startup -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415403] kmail2 5.13.0 (19.12.0) with QtWebEngine 5.14.0 - segfault in KMReaderWin::KMReaderWin on startup
https://bugs.kde.org/show_bug.cgi?id=415403 --- Comment #3 from Dennis Schridde --- Created attachment 125528 --> https://bugs.kde.org/attachment.cgi?id=125528=edit gdb full backtrace, kmail 5.13.1 (19.12.1), qtwebengine 5.14.1 Persists with QtWebEngine 5.14.1, too. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415403] kmail2 5.13.0 (19.12.0) with QtWebEngine 5.14.0 - segfault in KMReaderWin::KMReaderWin on startup
https://bugs.kde.org/show_bug.cgi?id=415403 --- Comment #2 from Dennis Schridde --- The issue persists with KDE Applications 19.12.1. Here is a backtrace from 2020-01-25: Process 6729 (kmail) of user 1000 dumped core. Stack trace of thread 6918: #0 0x7f2672f28461 raise (libc.so.6 + 0x3a461) #1 0x7f267468c361 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5361) #2 0x7f2672f28520 __restore_rt (libc.so.6 + 0x3a520) #3 0x7f2672f28461 raise (libc.so.6 + 0x3a461) #4 0x7f2672f1055b abort (libc.so.6 + 0x2255b) #5 0x7f26622bf545 log_assert_failed_realm (libudev.so.1 + 0x6545) #6 0x7f26622d0521 safe_close (libudev.so.1 + 0x17521) #7 0x7f26622c5181 device_monitor_disconnect (libudev.so.1 + 0xc181) #8 0x7f26622c5224 sd_device_monitor_stop (libudev.so.1 + 0xc224) #9 0x7f26622c526e sd_device_monitor_detach_event (libudev.so.1 + 0xc26e) #10 0x7f26622c52e4 device_monitor_free (libudev.so.1 + 0xc2e4) #11 0x7f26622c2090 udev_monitor_free (libudev.so.1 + 0x9090) #12 0x7f2668a054b4 _ZN6device11UdevWatcher13StartWatchingEPNS0_8ObserverERKSt6vectorINS0_6FilterESaIS4_EE (libQt5WebEngineCore.so.5 + 0x11104b4) #13 0x7f2668b44dde _ZN5media18DeviceMonitorLinux24BlockingTaskRunnerHelper10InitializeEv (libQt5WebEngineCore.so.5 + 0x124fdde) #14 0x7f266a94445e _ZN4base13TaskAnnotator7RunTaskEPKcPNS_11PendingTaskE (libQt5WebEngineCore.so.5 + 0x304f45e) #15 0x7f266a9b0582 _ZN4base8internal11TaskTracker21RunContinueOnShutdownEPNS0_4TaskE (libQt5WebEngineCore.so.5 + 0x30bb582) #16 0x7f266a9b08ce _ZN4base8internal11TaskTracker13RunOrSkipTaskENS0_4TaskEPNS0_10TaskSourceERKNS_10TaskTraitsEb (libQt5WebEngineCore.so.5 + 0x30bb8ce) #17 0x7f266a99619d _ZN4base8internal16TaskTrackerPosix13RunOrSkipTaskENS0_4TaskEPNS0_10TaskSourceERKNS_10TaskTraitsEb (libQt5WebEngineCore.so.5 + 0x30a119d) #18 0x7f266a9b01a9 _ZN4base8internal11TaskTracker17RunAndPopNextTaskENS0_23DecoratorWithTaskSourceINS0_10TaskSource9RunIntentENS0_20RegisteredTaskSourceEEE (libQt5WebEngineCore.so.5 + 0x30bb1a9) #19 0x7f266a9b5ce5 _ZN4base8internal12WorkerThread9RunWorkerEv (libQt5WebEngineCore.so.5 + 0x30c0ce5) #20 0x7f266a9b6134 _ZN4base8internal12WorkerThread15RunPooledWorkerEv (libQt5WebEngineCore.so.5 + 0x30c1134) #21 0x7f266a996505 _ZN4base12_GLOBAL__N_110ThreadFuncEPv (libQt5WebEngineCore.so.5 + 0x30a1505) #22 0x7f267077142a start_thread (libpthread.so.0 + 0x842a) #23 0x7f2672ffa3cf __clone (libc.so.6 + 0x10c3cf) Stack trace of thread 6741: #0 0x7f2670778a47 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfa47) #1 0x7f265779872b cnd_wait (radeonsi_dri.so + 0x5f672b) #2 0x7f2657798337 impl_thrd_routine (radeonsi_dri.so + 0x5f6337) #3 0x7f267077142a start_thread (libpthread.so.0 + 0x842a) #4 0x7f2672ffa3cf __clone (libc.so.6 + 0x10c3cf) Stack trace of thread 6737: #0 0x7f2670778a47 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfa47) #1 0x7f265779872b cnd_wait (radeonsi_dri.so + 0x5f672b) #2 0x7f2657798337 impl_thrd_routine (radeonsi_dri.so + 0x5f6337) #3 0x7f267077142a start_thread (libpthread.so.0 + 0x842a) #4 0x7f2672ffa3cf __clone (libc.so.6 + 0x10c3cf) Stack trace of thread 6740: #0 0x7f2670778a47 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfa47) #1 0x7f265779872b cnd_wait (radeonsi_dri.so + 0x5f672b) #2 0x7f2657798337 impl_thrd_routine (radeonsi_dri.so + 0x5f6337) #3 0x7f267077142a start_thread (libpthread.so.0 + 0x842a) #4 0x7f2672ffa3cf __clone (libc.so.6 + 0x10c3cf) Stack trace of thread 6743: #0 0x7f2670778a47 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfa47) #1 0x7f265779872b cnd_wait (radeonsi_dri.so + 0x5f672b) #2 0x7f2657798337 impl_thrd_routine (radeonsi_dri.so + 0x5f6337) #3 0x7f267077142a start_thread (libpthread.so.0 + 0x842a) #4 0x7f2672ffa3cf __clone (libc.so.6 + 0x10c3cf) Stack trace of thread 6912: #0 0x7f2670778d7d pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfd7d) #1 0x7f266a993a36 _ZN4base17ConditionVariable9TimedWaitERKNS_9TimeDeltaE (libQt5WebEngineCore.so.5 + 0x309ea36) #2 0x7f266a9944cb _ZN4base13WaitableEvent14TimedWaitUntilERKNS_9TimeTicksE (libQt5WebEngineCore.so.5 + 0x309f4cb) #3 0x7f266a994631 _ZN4base13WaitableEvent9TimedWaitERKNS_9TimeDeltaE (libQt5WebEngineCore.so.5 + 0x309f631) #4 0x7f266a9b5762 _ZN4base8internal12WorkerThread8Delegate11WaitForWorkEPNS_13WaitableEventE (libQt5WebEngineCore.so.5 + 0x30c0762) #5 0x7f266a9b5e19 _ZN4base8internal12WorkerThread9RunWorkerEv (libQt5WebEngineCore.so.5 + 0x30c0e19) #6 0x7f266a9b6134 _ZN4base8internal12WorkerThread15RunPooledWorkerEv (libQt5WebEngineCore.so.5 + 0x30c1134) #7 0x7f266a996505 _ZN4base12_GLOBAL__N_110ThreadFuncEPv (libQt5WebEngineCore.so.5 + 0x30a1505) #8 0x7f267077142a start_thread (libpthread.so.0 + 0x842a) #9 0x7f2672ffa3cf __clone (libc.so.6 + 0x10c3cf) Stack trace of thread
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #107 from Dennis Schridde --- In case you want to know more of the background, there is an article in German magazine iX and Heise Online. In the last paragraph, the KDE PIM issue is being mentioned. https://www.heise.de/ix/meldung/Mailbox-org-Google-sperrt-unsichere-Dritte-von-Kalender-aus-4640540.html -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #106 from Dennis Schridde --- I confirm: On Fedora 31 Google Contacts, Calendars and Tasks work again in Akonadi (as expected from Adriaan's reply), while GMail does not (which is also as expected). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #104 from Dennis Schridde --- I received a response from Adriaan de Groot : > Please see https://euroquis.nl/kde/2020/01/13/google.html .. there is progress, although Google's review of KMail's use of access to GMail is still pending. tl;dr: The contacts and calendar issues should be fixed by the upcoming February 2020 update of KDE Apps, but the email problem is still work in progress. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415403] kmail2 5.13.0 (19.12.0) with QtWebEngine 5.14.0 - segfault in KMReaderWin::KMReaderWin on startup
https://bugs.kde.org/show_bug.cgi?id=415403 --- Comment #1 from Dennis Schridde --- Created attachment 124620 --> https://bugs.kde.org/attachment.cgi?id=124620=edit console log (stdout / stderr) -- You are receiving this mail because: You are the assignee for the bug.
