[Akonadi] [Bug 486627] New: Akonadi crashes a while after a restart
https://bugs.kde.org/show_bug.cgi?id=486627 Bug ID: 486627 Summary: Akonadi crashes a while after a restart Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.24.5 (23.08.5)) (Compiled from sources) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.6.21-gentoo-g x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: I had restarted akonadi because one (IMAP) resource was stuk and usually, restarting fixes that. This time, I restarted and went to do something else on my computer. Then, a while later (10 minutes?) it crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted [KCrash Handler] #4 0x7be7e2ec481c in ?? () from /usr/lib64/libc.so.6 #5 0x7be7e2e74142 in raise () from /usr/lib64/libc.so.6 #6 0x7be7e2e5c4ef in abort () from /usr/lib64/libc.so.6 #7 0x7be7e309bca9 in ?? () from /usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6 #8 0x7be7e30ae338 in ?? () from /usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6 #9 0x7be7e30ae3a3 in std::terminate() () from /usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6 #10 0x7be7e347a18e in qTerminate () at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/global/qglobal.cpp:3383 #11 0x7be7e347c10b in (anonymous namespace)::terminate_on_exception > (t=...) at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qthread_unix.cpp:297 #12 QThreadPrivate::start (arg=0x557797794000) at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qthread_unix.cpp:310 #13 0x7be7e2ec2ac9 in ?? () from /usr/lib64/libc.so.6 #14 0x7be7e2f36ec8 in ?? () from /usr/lib64/libc.so.6 Thread 7 (Thread 0x7be7dca776c0 (LWP 702492) "IntervalCheck-T"): #1 0x7be7e1b2160c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #2 0x7be7e36cf1be in QEventDispatcherGlib::processEvents (this=0x7be7b8000b70, flags=...) at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #3 0x7be7e367c00b in QEventLoop::exec (this=this@entry=0x7be7dca76d10, flags=..., flags@entry=...) at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/include/QtCore/../../src/corelib/global/qflags.h:69 #4 0x7be7e34c0aea in QThread::exec (this=) at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/include/QtCore/../../src/corelib/global/qflags.h:121 #5 0x7be7e34c1e17 in operator() (__closure=) at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qthread_unix.cpp:350 #6 (anonymous namespace)::terminate_on_exception > (t=...) at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qthread_unix.cpp:287 #7 QThreadPrivate::start (arg=0x557797770460) at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qthread_unix.cpp:310 #8 0x7be7e2ec2ac9 in ?? () from /usr/lib64/libc.so.6 #9 0x7be7e2f36ec8 in ?? () from /usr/lib64/libc.so.6 Thread 6 (Thread 0x7be7dd2786c0 (LWP 702491) "SearchTaskManag"): #1 0x7be7e2ec1de2 in pthread_cond_wait () from /usr/lib64/libc.so.6 #2 0x7be7e34c776b in QWaitConditionPrivate::wait (deadline=..., this=0x5577977d7e60) at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qwaitcondition_unix.cpp:146 #3 QWaitCondition::wait (this=this@entry=0x557797792a98, mutex=mutex@entry=0x557797792aa0, deadline=...) at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/thread/qwaitcondition_unix.cpp:225 #4 0x557796cabcc6 in Akonadi::Server::SearchTaskManager::searchLoop (this=0x557797792a70) at /var/tmp/portage/kde-apps/akonadi-23.08.5/work/akonadi-23.08.5/src/server/search/searchtaskmanager.cpp:195 #5 0x7be7e36a86b7 in QObject::event (this=0x557797792a70, e=0x557797792ef0) at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/kernel/qobject.cpp:1347 #6 0x7be7e367d5b5 in doNotify (event=0x557797792ef0, receiver=0x557797792a70) at /var/tmp/portage/dev-qt/qtcore-5.15.13/work/qtbase-everywhere-src-5.15.13/src/corelib/kernel/qcoreapplication.cpp:1154 #7 QCoreApplication::notify (event=, receiver=, this=) at
[Reminder Daemon] [Bug 485863] New: log flooded with messages when EWS cannot reach outlook server
https://bugs.kde.org/show_bug.cgi?id=485863 Bug ID: 485863 Summary: log flooded with messages when EWS cannot reach outlook server Classification: Frameworks and Libraries Product: Reminder Daemon Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- My log is filled with innumerable repetitions of lines of the following kind: ``` kalendarac[1883]: org.kde.pim.ews.client: Failed to process EWS request: Unknown host outlook.office365.com: Host not found ``` This suggests to me that whatever process is trying to create a connection is trying again and again even if there is no internet connection. Would it be possible to make this process act a bit smarter, as it would avoid having relevant messages in logs being drowned out by these? *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 451620] akonadictl; sqlite: Error moving orphan items to collection 242 : Expression tree is too large (maximum depth 1000)
https://bugs.kde.org/show_bug.cgi?id=451620 --- Comment #4 from Erik Quaeghebeur --- (In reply to Christophe Marin from comment #3) > (In reply to Erik Quaeghebeur from comment #2) > > This is still an issue in latest KDE 5 versions. (I again had to apply my > > manual SQL fix.) > > If you mean akonadi < 24.02, it won't get the fix. This branch is closed, > you need to backport the change manually. Ah, nice, it seems the great commit https://invent.kde.org/pim/akonadi/-/commit/fcc37ce297df718430f83f7feb669573c9b135f2?page=3#995e689d409482037d49b6b0893848ff42e9f64f likely fixed the issue. (The function is now at https://invent.kde.org/pim/akonadi/-/blob/master/src/server/storagejanitor.cpp#L301.) AFAIU, It does seem though that the fix still passes through a C++ data structure and uses a two-step approach. Namely, first a list of orphans is queried, it is copied to a QList (https://invent.kde.org/pim/akonadi/-/blob/master/src/server/storagejanitor.cpp#L325), which is fed back into a second query that sets the orphaned items' collectionId to the lost+found one. This might be done more efficiently by directly selecting anything that qualifies as an orphan item using SQL directly in the WHERE of the UPDATE statement (cf. https://www.sqlite.org/lang_update.html, like in the DELETE statement in my Comment #1). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 451620] akonadictl; sqlite: Error moving orphan items to collection 242 : Expression tree is too large (maximum depth 1000)
https://bugs.kde.org/show_bug.cgi?id=451620 Erik Quaeghebeur changed: What|Removed |Added Version|5.18.3 |5.24.5 --- Comment #2 from Erik Quaeghebeur --- This is still an issue in latest KDE 5 versions. (I again had to apply my manual SQL fix.) I believe this issue should be taken seriously. It points to a a sometimes very inefficient approach to using SQL in Akonadi's code. Namely, that things which are easy/efficient to do in SQL are instead done inefficiently in C++. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 480543] Akonadis sqlite backend does not honor sql limits
https://bugs.kde.org/show_bug.cgi?id=480543 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu --- Comment #5 from Erik Quaeghebeur --- Related: Bug #451620 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483365] akonadiconsole wants QSQLITE3, while only QSQLITE is available
https://bugs.kde.org/show_bug.cgi?id=483365 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483365] akonadiconsole wants QSQLITE3, while only QSQLITE is available
https://bugs.kde.org/show_bug.cgi?id=483365 --- Comment #3 from Erik Quaeghebeur --- (In reply to Nick from comment #2) > Hi. Thanks for raising this. Can you please provide a full list of commands > you are issuing to cause this, plus any associated apps which need to be > installed? I will then try to duplicate this. Thanks, Nick Install akonadiconsole. Stop akonadi. Replace your akonadiserverrc file with the first one of Comment 1. Restart akonadi. My feeling is that the behavior with those settings are not interesting. It would rather be interesting to know whether those settings can occur without user interaction. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483364] akonadiconsole crashes after trying to restart server
https://bugs.kde.org/show_bug.cgi?id=483364 Erik Quaeghebeur changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Erik Quaeghebeur --- (In reply to Nick from comment #1) > Hi - thanks for raising this. Can you please provide a full list of commands > you issued to cause this, plus any apps installed relating to this? I will > then try to duplicate it. Thanks, Nick. I cannot provide more info than what is in the original report. If the backtrace doesn't point to a specific code path, I guess this report cannot be followed up. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483365] akonadiconsole wants QSQLITE3, while only QSQLITE is available
https://bugs.kde.org/show_bug.cgi?id=483365 --- Comment #1 from Erik Quaeghebeur --- I investigated a bit further. My akonadiserverrc file looked as follows: --- [Debug] Tracer=null [%General] Driver=QSQLITE3 [QSQLITE] Name=/home/USERNAME/.local/share/akonadi/akonadi.db [QSQLITE3] Name=/home/USERNAME/.local/share/akonadi/akonadi.db --- I am very sure I did not add the multiple [QSQLITE.?] lines, but only had one in the past. (Can't remember which.) When stopping the server, changing to the config below and restarting the server and akonadiconsole, I do not get an error message anymore and DB-Browser in akonadiconsole is working again, so that seemed to have been the problem. So the bugreport now only still pertains to the configuration issue. --- [Debug] Tracer=null [%General] Driver=QSQLITE [QSQLITE] Name=/home/USERNAME/.local/share/akonadi/akonadi.db --- -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483365] New: akonadiconsole wants QSQLITE3, while only QSQLITE is available
https://bugs.kde.org/show_bug.cgi?id=483365 Bug ID: 483365 Summary: akonadiconsole wants QSQLITE3, while only QSQLITE is available Classification: Frameworks and Libraries Product: Akonadi Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: akonadiconsole Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu CC: c...@carlschwan.eu Target Milestone: --- SUMMARY When starting akonadi, I twice get the message that the database driver is not loaded. When looking at the startup log in akonadiconsole when restarting the server, it becomes clear that akonadiconsole wants QSQLITE3, while only QSQLITE is available. I assume it is akonadiconsole and not akonadi, because the latter functions, but the former's DB-Browser tab doesn't work. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION I think this may be related to “Remove the QSQLITE3 driver” https://invent.kde.org/pim/akonadi/-/commit/e70a7a5521b4d8fe0bb36a5b3392c547851507b0 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 483364] New: akonadiconsole crashes after trying to restart server
https://bugs.kde.org/show_bug.cgi?id=483364 Bug ID: 483364 Summary: akonadiconsole crashes after trying to restart server Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: akonadiconsole Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiconsole (5.24.5 (23.08.5)) (Compiled from sources) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.6.21-gentoo-a x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: I tried to restart the akonadi server from within akonadiconsole, but then it crashed. Perhaps related: I had run akonadictl fsck before this. The crash does not seem to be reproducible. -- Backtrace: Application: Akonadi-console (akonadiconsole), signal: Segmentation fault [KCrash Handler] #4 0x72871414c181 in AgentConfigModel::~AgentConfigModel (this=0x7286f4007c20, this=) at /var/tmp/portage/kde-apps/akonadiconsole-23.08.5/work/akonadiconsole-23.08.5/src/agentconfigmodel.cpp:20 #5 0x72871414c259 in AgentConfigModel::~AgentConfigModel (this=0x7286f4007c20, this=) at /var/tmp/portage/kde-apps/akonadiconsole-23.08.5/work/akonadiconsole-23.08.5/src/agentconfigmodel.cpp:21 #6 0x728712ebe682 in QObjectPrivate::deleteChildren (this=this@entry=0x5fec46907340) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r2/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qobject.cpp:2137 #7 0x7287139a27d6 in QWidget::~QWidget (this=this@entry=0x5fec468f6ed0, __in_chrg=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidget.cpp:1524 #8 0x728713b7878a in QDialog::~QDialog (this=this@entry=0x5fec468f6ed0, __in_chrg=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/widgets/dialogs/qdialog.cpp:426 #9 0x72871413e1ea in AgentConfigDialog::~AgentConfigDialog (this=0x5fec468f6ed0, this=) at /var/tmp/portage/kde-apps/akonadiconsole-23.08.5/work/akonadiconsole-23.08.5_build/src/libakonadiconsole_autogen/EWIEGA46WW/../../../../akonadiconsole-23.08.5/src/agentconfigdialog.h:15 #10 AgentConfigDialog::~AgentConfigDialog (this=0x5fec468f6ed0, this=) at /var/tmp/portage/kde-apps/akonadiconsole-23.08.5/work/akonadiconsole-23.08.5_build/src/libakonadiconsole_autogen/EWIEGA46WW/../../../../akonadiconsole-23.08.5/src/agentconfigdialog.h:15 #11 0x728714141076 in AgentWidget::configureAgentRemote (this=) at /var/tmp/portage/kde-apps/akonadiconsole-23.08.5/work/akonadiconsole-23.08.5/src/agentwidget.cpp:230 #12 0x728712ec6b64 in QtPrivate::QSlotObjectBase::call (a=0x7ffc74b11270, r=0x5fec45c7b4f0, this=0x5fec46039cb0) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r2/work/qtbase-everywhere-src-5.15.12/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x5fec46039980, signal_index=4, argv=0x7ffc74b11270) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r2/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qobject.cpp:3925 #14 0x728712ec0897 in QMetaObject::activate (sender=sender@entry=0x5fec46039980, m=m@entry=0x728713e90c80 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc74b11270) at /var/tmp/portage/dev-qt/qtcore-5.15.12-r2/work/qtbase-everywhere-src-5.15.12/src/corelib/kernel/qobject.cpp:3985 #15 0x72871395c642 in QAction::triggered (this=this@entry=0x5fec46039980, _t1=) at .moc/moc_qaction.cpp:376 #16 0x72871395f41f in QAction::activate (this=0x5fec46039980, event=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qaction.cpp:1161 #17 0x728713aee8aa in QMenuPrivate::activateCausedStack (this=this@entry=0x5fec46066b70, causedStack=..., action=action@entry=0x5fec46039980, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/widgets/widgets/qmenu.cpp:1384 #18 0x728713af68d0 in QMenuPrivate::activateAction (this=0x5fec46066b70, action=0x5fec46039980, action_e=, self=true) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/widgets/widgets/qmenu.cpp:1461 #19 0x7287139a6fa8 in QWidget::event (this=0x5fec45ec6e20, event=0x7ffc74b11880) at /var/tmp/portage/dev-qt/qtwidgets-5.15.12-r1/work/qtbase-everywhere-src-5.15.12/src/widgets/kernel/qwidget.cpp:9045 #20 0x7287139631ee in QApplicationPrivate::notify_helper (this=this@entry=0x5fec4584bfe0, receiver=receiver@entry=0x5fec45ec6e20, e=e@entry=0x7ffc74b11880) at
[Akonadi] [Bug 477637] New: Synchronization of EWS resource blocks other resources
https://bugs.kde.org/show_bug.cgi?id=477637 Bug ID: 477637 Summary: Synchronization of EWS resource blocks other resources Classification: Frameworks and Libraries Product: Akonadi Version: 5.24.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: EWS Resource Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu CC: c...@carlschwan.eu, kri...@op.pl Target Milestone: --- I've noticed that whenever the EWS resource is syncing, other resources are blocked. This is especially problematic when for example trying to compose a response to an email in another (e.g., IMAP) resource. It ‘hangs’ with a dialog saying that it is retrieving the message. Can the EWS resource's activity be split off into some separate process? (I do not understand why it could be necessary to block composing a response to a message in another resource.) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 471834] New: KMail crashes after being stuck sending an email
https://bugs.kde.org/show_bug.cgi?id=471834 Bug ID: 471834 Summary: KMail crashes after being stuck sending an email Classification: Applications Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: kmail (5.22.3 (22.12.3)) (Compiled from sources) Qt Version: 5.15.9 Frameworks Version: 5.106.0 Operating System: Linux 6.1.31-gentoo-b x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: I was trying to send an email. Because it didn't go (grayed out) and nothing happened, I closed and restarting KMail, which then crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x72d99e56f297 in std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/atomic_base.h:488 #5 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed() const (this=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #7 QtPrivate::RefCount::isShared() const (this=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/tools/qrefcount.h:101 #8 QList::append(QWidget* const&) (this=0x586361e94e60, t=@0x7ffddce91470: 0x5863616e8cb0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/tools/qlist.h:622 #9 0x72d99e59d4b0 in QWidget::insertAction(QAction*, QAction*) (this=this@entry=0x5863616e8cb0, before=, before@entry=0x0, action=0x5863618acb60) at /var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/src/widgets/kernel/qwidget.cpp:3138 #10 0x72d99d3bad92 in KXMLGUI::ActionList::plug(QWidget*, int) const (this=this@entry=0x586361ac2030, container=0x5863616e8cb0, index=) at /var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguifactory_p.cpp:33 #11 0x72d99d3bf4d3 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&, QTypedArrayData::iterator const&) (this=this@entry=0x5863619f18d0, state=..., mergingIdxIt=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguifactory_p.cpp:209 #12 0x72d99d3bf712 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=0x5863619f18d0, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguifactory_p.cpp:181 #13 0x72d99d3bf745 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguifactory_p.cpp:185 #14 0x72d99d3bf745 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguifactory_p.cpp:185 #15 0x72d99d3b8437 in KXMLGUIFactory::plugActionList(KXMLGUIClient*, QString const&, QList const&) (this=0x586361a21200, client=client@entry=0x586368a0d4f0, name=..., actionList=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguifactory.cpp:564 #16 0x72d99d3af01d in KXMLGUIClient::plugActionList(QString const&, QList const&) (this=this@entry=0x586368a0d4f0, name=..., actionList=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.106.0/work/kxmlgui-5.106.0/src/kxmlguiclient.cpp:697 #17 0x72d99c58051b in PimCommon::PluginInterface::initializePluginActions(QString const&, KXMLGUIClient*) (this=, prefix=..., guiClient=0x586368a0d4f0) at /var/tmp/portage/kde-apps/pimcommon-22.12.3/work/pimcommon-22.12.3/src/pimcommonakonadi/genericplugins/plugininterface.cpp:154 #18 0x72d9a6e0dc8e in KMMainWidget::initializePluginActions() (this=this@entry=0x5863718fc130) at /var/tmp/portage/kde-apps/kmail-22.12.3/work/kmail-22.12.3/src/kmmainwidget.cpp:4190 #19 0x72d9a6e18a73 in KMMainWidget::slotShowStartupFolder() (this=0x5863718fc130) at /var/tmp/portage/kde-apps/kmail-22.12.3/work/kmail-22.12.3/src/kmmainwidget.cpp:4096 #20 0x72d99daaf8c4 in QObject::event(QEvent*) (this=0x5863718fc130, e=0x58636492d000) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:1347 #21 0x72d99e56344e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x5863718fc130,
[Akonadi] [Bug 469789] New: Akonadi crashes when akonadiserver is restarted
https://bugs.kde.org/show_bug.cgi?id=469789
Bug ID: 469789
Summary: Akonadi crashes when akonadiserver is restarted
Classification: Frameworks and Libraries
Product: Akonadi
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: server
Assignee: kdepim-bugs@kde.org
Reporter: bugs.kde@e3q.eu
CC: c...@carlschwan.eu
Target Milestone: ---
Application: akonadiserver (5.22.3 (22.12.3))
(Compiled from sources)
Qt Version: 5.15.9
Frameworks Version: 5.104.0
Operating System: Linux 6.1.27-gentoo-r1-a x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.4 [KCrashBackend]
-- Information about the crash:
Akonadi resources often get stuck synchronizing. One way of working around that
is to restart akonadiserver. Sometimes akonadi then crashes, as with this
crash.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
[KCrash Handler]
#4 std::default_delete::operator() (__ptr=0x211,
this=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/unique_ptr.h:89
#5 std::unique_ptr >::~unique_ptr
(this=, __in_chrg=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/unique_ptr.h:396
#6 std::__new_allocator >
>::destroy > > (__p=,
this=0x7ffd41125ae8) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/new_allocator.h:181
#7
std::allocator_traits > >
>::destroy > > (__p=,
__a=...) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/alloc_traits.h:535
#8 std::vector >,
std::allocator > > >::_M_erase
(__position=std::unique_ptr = {...},
this=0x7ffd41125ae8) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/vector.tcc:181
#9 std::vector >,
std::allocator > > >::erase
(__position=std::unique_ptr = {...},
this=0x7ffd41125ae8) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/stl_vector.h:1530
#10 Akonadi::Server::AkonadiServer::connectionDisconnected
(this=0x7ffd41125a60) at
/var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/server/akonadi.cpp:234
#11 0x787ce9aaf8d4 in QObject::event (this=0x7ffd41125a60,
e=0x787c3c02dfe0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:1347
#12 0x787ce9a83f25 in doNotify (event=0x787c3c02dfe0,
receiver=0x7ffd41125a60) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1154
#13 QCoreApplication::notify (event=, receiver=,
this=) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1140
#14 QCoreApplication::notifyInternal2 (receiver=0x7ffd41125a60,
event=0x787c3c02dfe0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1064
#15 0x787ce9a8414e in QCoreApplication::sendEvent (receiver=, event=) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1462
#16 0x787ce9a87493 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x65001f79d9c0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1821
#17 0x787ce9a87738 in QCoreApplication::sendPostedEvents
(receiver=, event_type=) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1680
#18 0x787ce9ad66f3 in postEventSourceDispatch (s=0x65001f7a0550) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qeventdispatcher_glib.cpp:277
#19 0x787ce858f51c in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#20 0x787ce858f7c8 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x787ce858f85c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#22 0x787ce9ad61f6 in QEventDispatcherGlib::processEvents
(this=0x65001f7a02e0, flags=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qeventdispatcher_glib.cpp:423
#23 0x787ce9a8297b in QEventLoop::exec (this=this@entry=0x7ffd41125940,
flags=..., flags@entry=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/global/qflags.h:69
#24 0x787ce9a8ac56 in QCoreApplication::exec () at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/global/qflags.h:121
#25 0x65001dee2d45 in AkApplicationBase::exec
(this=this@entry=0x7ffd41125a30) at
/var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/shared/akapplication.cpp:109
#26 0x65001dd6e8a0 in main (argc=, argv=) at
[kmail2] [Bug 469694] New: KMail crash when akonadiserver is restarted
https://bugs.kde.org/show_bug.cgi?id=469694 Bug ID: 469694 Summary: KMail crash when akonadiserver is restarted Classification: Applications Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: kmail (5.22.3 (22.12.3)) (Compiled from sources) Qt Version: 5.15.9 Frameworks Version: 5.104.0 Operating System: Linux 6.1.27-gentoo-r1-a x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: As often happens, an akonadi resource was stuck synchronizing, blocking the whole of akonadi. My solution for this is to restart akonadiserver in akonadiconsole. This crash occurred when I restarted akonadiserver in such a way. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::operator--() (this=0x630031) at /usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/atomic_base.h:392 #5 QAtomicOps::deref(std::atomic&) (_q_value=) at /usr/include/qt5/QtCore/qatomic_cxx11.h:289 #6 QBasicAtomicInteger::deref() (this=0x630031) at /usr/include/qt5/QtCore/qbasicatomic.h:119 #7 QSharedDataPointer::~QSharedDataPointer() (this=0x5984d1702d50, __in_chrg=) at /usr/include/qt5/QtCore/qshareddata.h:93 #8 Akonadi::Item::~Item() (this=0x5984d1702d50, __in_chrg=) at /var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/core/item.cpp:56 #9 0x7e4023707e1c in QHashData::free_helper(void (*)(QHashData::Node*)) (this=0x7e401409d9a0, node_delete=0x7e4021797cc0 ::RefCountedValue >::deleteNode2(QHashData::Node*)>) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/tools/qhash.cpp:572 #10 0x7e402178f38f in QHash::RefCountedValue >::freeData(QHashData*) (x=, this=) at /usr/include/qt5/QtCore/qhash.h:617 #11 QHash::RefCountedValue >::~QHash() (this=, __in_chrg=) at /usr/include/qt5/QtCore/qhash.h:250 #12 QHash::RefCountedValue >::~QHash() (this=, __in_chrg=) at /usr/include/qt5/QtCore/qhash.h:250 #13 QHash::RefCountedValue >::operator=(QHash::RefCountedValue >&&) (other=, this=0x5984d1bac5b8) at /usr/include/qt5/QtCore/qhash.h:255 #14 QHash::RefCountedValue >::clear() (this=0x5984d1bac5b8) at /usr/include/qt5/QtCore/qhash.h:625 #15 RefCountedHash::clear() (this=0x5984d1bac5b0) at /var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/core/models/entitytreemodel_p.h:109 #16 Akonadi::EntityTreeModelPrivate::endResetModel() (this=0x5984d1bac5a0) at /var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/core/models/entitytreemodel_p.cpp:1722 #17 0x7e40238b7b4c in doActivate(QObject*, int, void**) (sender=0x5984d0418c60, signal_index=3, argv=0x7ffdd7c568c0) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:3935 #18 0x7e40238b1767 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7e402182a500 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:3983 #19 0x7e4021711e80 in Akonadi::ServerManager::started() (this=) at /var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3_build/src/core/KF5AkonadiCore_autogen/include/moc_servermanager.cpp:167 #20 0x7e4021715659 in Akonadi::ServerManagerPrivate::setState(Akonadi::ServerManager::State) (this=0x7e4021832560 <(anonymous namespace)::Q_QGS_sInstance::innerFunction()::holder>, state=Akonadi::ServerManager::Running) at /var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/core/servermanager.cpp:75 #21 0x7e40238af8d4 in QObject::event(QEvent*) (this=0x5984d0418c60, e=0x5984d84960e0) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:1347 #22 0x7e402436344e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x5984d0418c60, e=0x5984d84960e0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/src/widgets/kernel/qapplication.cpp:3640 #23 0x7e4023883f58 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5984d0418c60, event=0x5984d84960e0) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1064 #24 0x7e402388414e in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1462 #25 0x7e4023887493 in
[kmail2] [Bug 468801] New: org.kde.pim.mimetreeparser: unknown mimetype "text/x-moz-deleted"
https://bugs.kde.org/show_bug.cgi?id=468801 Bug ID: 468801 Summary: org.kde.pim.mimetreeparser: unknown mimetype "text/x-moz-deleted" Classification: Applications Product: kmail2 Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- In my log, I find multiple repetitions of the following warning: --- kmail[6994]: org.kde.pim.mimetreeparser: unknown mimetype "text/x-moz-deleted" --- Given that kmail itself produces attached with such a mimetype when an attachment is deleted, I think it would be a good idea to support this type in some way, so as to at least not trigger a warning. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 454257] Crash on save of attachment
https://bugs.kde.org/show_bug.cgi?id=454257 Erik Quaeghebeur changed: What|Removed |Added Summary|Crash on save of attachment |Crash on save of attachment |(tar.gz)| --- Comment #3 from Erik Quaeghebeur --- (In reply to Erik Quaeghebeur from comment #2) > *** Bug 467266 has been marked as a duplicate of this bug. *** My encounter shows it is not limited to tar.gz, but can also occur, e.g., with pdfs. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 454257] Crash on save of attachment (tar.gz)
https://bugs.kde.org/show_bug.cgi?id=454257 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu --- Comment #2 from Erik Quaeghebeur --- *** Bug 467266 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467266] KMail crashes when saving a pdf attachment
https://bugs.kde.org/show_bug.cgi?id=467266 Erik Quaeghebeur changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Erik Quaeghebeur --- *** This bug has been marked as a duplicate of bug 454257 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 467266] New: KMail crashes when saving a pdf attachment
https://bugs.kde.org/show_bug.cgi?id=467266 Bug ID: 467266 Summary: KMail crashes when saving a pdf attachment Classification: Applications Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: kmail (5.21.3 (22.08.3)) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 6.1.12-gentoo-d x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: KMail crashed when saving a pdf attachment. The crash happens after the save file dialog has been opened and the moment the button to Save is pressed. (The file is not saved.) This has happened before a few times now. But it also happens that saving does work. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x70dc6574049e in QVector::begin(QTypedArrayData::const_iterator) const (this=) at /usr/include/qt5/QtCore/qvector.h:220 #5 KMime::Content::headerByType(char const*) const (this=this@entry=0x630ae9dec5b0, type=0x70dc6575ca0c "Content-Transfer-Encoding") at /var/tmp/portage/kde-apps/kmime-22.08.3/work/kmime-22.08.3/src/kmime_content.cpp:617 #6 0x70dc65741a19 in KMime::Content::header(bool) (create=true, this=0x630ae9dec5b0) at /var/tmp/portage/kde-apps/kmime-22.08.3/work/kmime-22.08.3/src/kmime_content.h:681 #7 KMime::Content::contentTransferEncoding(bool) (this=0x630ae9dec5b0, create=) at /var/tmp/portage/kde-apps/kmime-22.08.3/work/kmime-22.08.3/src/kmime_content.cpp:874 #8 0x70dc65741aa3 in KMime::Content::decodedContent() (this=0x630ae9dec5b0) at /var/tmp/portage/kde-apps/kmime-22.08.3/work/kmime-22.08.3/src/kmime_content.cpp:316 #9 0x70dc6631627e in MessageViewer::Util::saveContent(QWidget*, KMime::Content*, QUrl const&) (parent=0x630ae4cae770, content=, url=...) at /var/tmp/portage/kde-apps/messagelib-22.08.3/work/messagelib-22.08.3/messageviewer/src/utils/messageviewerutil.cpp:421 #10 0x70dc66317f1e in MessageViewer::Util::saveContents(QWidget*, QVector const&, QList&) (parent=0x630ae4cae770, contents=..., urlList=...) at /var/tmp/portage/kde-apps/messagelib-22.08.3/work/messagelib-22.08.3/messageviewer/src/utils/messageviewerutil.cpp:324 #11 0x70dc662d3a61 in MessageViewer::ViewerPrivate::slotHandleAttachment(int) (this=0x630ae4d71460, choice=) at /var/tmp/portage/kde-apps/messagelib-22.08.3/work/messagelib-22.08.3/messageviewer/src/viewer/viewer_p.cpp:2611 #12 0x70dc672b79c4 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffcd657e5b0, r=0x630ae4d71460, this=0x630ae83e2890) at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate(QObject*, int, void**) (sender=0x630ae6cd8d80, signal_index=4, argv=0x7ffcd657e5b0) at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:3923 #14 0x70dc672b1707 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x630ae6cd8d80, m=m@entry=0x70dc6828fd00 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffcd657e5b0) at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:3983 #15 0x70dc67d5c8b2 in QAction::triggered(bool) (this=this@entry=0x630ae6cd8d80, _t1=) at .moc/moc_qaction.cpp:376 #16 0x70dc67d5f64b in QAction::activate(QAction::ActionEvent) (this=0x630ae6cd8d80, event=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qaction.cpp:1161 #17 0x70dc67eeea8a in QMenuPrivate::activateCausedStack(QVector > const&, QAction*, QAction::ActionEvent, bool) (this=this@entry=0x630aee197cc0, causedStack=..., action=action@entry=0x630ae6cd8d80, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/widgets/qmenu.cpp:1384 #18 0x70dc67ef6aec in QMenuPrivate::activateAction(QAction*, QAction::ActionEvent, bool) (this=0x630aee197cc0, action=0x630ae6cd8d80, action_e=QAction::Trigger, self=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/widgets/qmenu.cpp:1461 #19 0x70dc67da7028 in QWidget::event(QEvent*) (this=0x7ffcd657f3c0, event=0x7ffcd657ebc0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:9045 #20 0x70dc67d6344e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x630ae48451e0,
[Akonadi] [Bug 466913] New: Feature request: select only some calendars in collection
https://bugs.kde.org/show_bug.cgi?id=466913 Bug ID: 466913 Summary: Feature request: select only some calendars in collection Classification: Frameworks and Libraries Product: Akonadi Version: 5.21.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Caldav collections can have multiple calendars. Sometimes one does not wish to synchronize all of them. (I have one which very often causes the resource to get stuck…) It would be convenient to have the possibility to only synchronize a selected subset of the available calendars. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 466233] New: KMail crashes after restart after akonadi-restart when mail was not being sent
https://bugs.kde.org/show_bug.cgi?id=466233 Bug ID: 466233 Summary: KMail crashes after restart after akonadi-restart when mail was not being sent Classification: Applications Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: kmail (5.21.3 (22.08.3)) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 6.1.12-gentoo-c x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: I tried to send a mail using KMail, but it did not do that. So I restarted akonadi (the go-to solution for most issues…). Then KMail's folder list became empty. So I quit it and restarted. Then KMail crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Aborted [KCrash Handler] #4 0x770ecf6b0f9c in () at /usr/lib64/libc.so.6 #5 0x770ecf663b62 in raise () at /usr/lib64/libc.so.6 #6 0x770ecf64e471 in abort () at /usr/lib64/libc.so.6 #7 0x770ecf49e99f in () at /usr/lib/gcc/x86_64-pc-linux-gnu/12/libstdc++.so.6 #8 0x770ecf4aa5d6 in () at /usr/lib/gcc/x86_64-pc-linux-gnu/12/libstdc++.so.6 #9 0x770ecf4aa641 in () at /usr/lib/gcc/x86_64-pc-linux-gnu/12/libstdc++.so.6 #10 0x770ecf4aa8a2 in () at /usr/lib/gcc/x86_64-pc-linux-gnu/12/libstdc++.so.6 #11 0x770ecf890f96 in qBadAlloc() () at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/global/qglobal.cpp:3371 #12 0x770ecf89397e in QListData::detach_grow(int*, int) (this=this@entry=0x5d4cd94a8110, idx=idx@entry=0x7ffd8a8d799c, num=num@entry=1) at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/tools/qlist.cpp:97 #13 0x770ed056f1ac in QList::detach_helper_grow(int, int) (this=0x5d4cd94a8110, i=, i@entry=2147483647, c=c@entry=1) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/tools/qlist.h:803 #14 0x770ed056f2ad in QList::append(QWidget* const&) (this=, t=@0x7ffd8a8d79f0: 0x5d4ce23f5e40) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/tools/qlist.h:623 #15 0x770ed059d4b0 in QWidget::insertAction(QAction*, QAction*) (this=this@entry=0x5d4ce23f5e40, before=, before@entry=0x0, action=0x5d4cd94bdbd0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:3138 #16 0x770ecf3ba982 in KXMLGUI::ActionList::plug(QWidget*, int) const (this=this@entry=0x5d4ce547c9e0, container=0x5d4ce23f5e40, index=) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguifactory_p.cpp:33 #17 0x770ecf3bf0c3 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&, QTypedArrayData::iterator const&) (this=this@entry=0x5d4cdd7b2050, state=..., mergingIdxIt=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguifactory_p.cpp:209 #18 0x770ecf3bf302 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=0x5d4cdd7b2050, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguifactory_p.cpp:181 #19 0x770ecf3bf335 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguifactory_p.cpp:185 #20 0x770ecf3bf335 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguifactory_p.cpp:185 #21 0x770ecf3b8027 in KXMLGUIFactory::plugActionList(KXMLGUIClient*, QString const&, QList const&) (this=0x5d4ce91e9a90, client=client@entry=0x5d4ce4e1d100, name=..., actionList=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguifactory.cpp:564 #22 0x770ecf3aec0d in KXMLGUIClient::plugActionList(QString const&, QList const&) (this=this@entry=0x5d4ce4e1d100, name=..., actionList=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguiclient.cpp:697 #23 0x770ece49d28b in PimCommon::PluginInterface::initializePluginActions(QString const&, KXMLGUIClient*) (this=, prefix=..., guiClient=0x5d4ce4e1d100) at /var/tmp/portage/kde-apps/pimcommon-22.08.3/work/pimcommon-22.08.3/src/pimcommonakonadi/genericplugins/plugininterface.cpp:152 #24 0x770ed8a0beae in KMMainWidget::initializePluginActions() (this=) at
[kmail2] [Bug 464440] New: KMail crashes on startup after being stuck
https://bugs.kde.org/show_bug.cgi?id=464440 Bug ID: 464440 Summary: KMail crashes on startup after being stuck Classification: Applications Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: kmail (5.21.3 (22.08.3)) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.99.0 Operating System: Linux 5.15.88-gentoo-a x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: KMail was stuck loading folder contents. This can often be resolved by restarting it and/or Akonadi. Like now, this often results in a crash when restarting. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=Python Exception : Cannot access memory at address 0x65006d0061016e #5 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=Python Exception : Cannot access memory at address 0x65006d0061016e #6 QBasicAtomicInteger::loadRelaxed() const (this=Python Exception : Cannot access memory at address 0x65006d0061016e #7 QtPrivate::RefCount::isShared() const (this=Python Exception : Cannot access memory at address 0x65006d0061016e #8 QList::append(QWidget* const&) (this=0x65006d0061016e, t=@0x7ffec9e6b1b0: 0x5bf37c295430) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8/work/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/tools/qlist.h:622 #9 0x762a0c12f5d9 in QWidget::insertAction(QAction*, QAction*) (this=this@entry=0x5bf37c295430, before=, before@entry=0x0, action=0x5bf37c482260) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:3138 #10 0x762a0afea8c2 in KXMLGUI::ActionList::plug(QWidget*, int) const (this=this@entry=0x5bf37c235bf0, container=0x5bf37c295430, index=) at /var/tmp/portage/kde-frameworks/kxmlgui-5.99.0/work/kxmlgui-5.99.0/src/kxmlguifactory_p.cpp:33 #11 0x762a0afeefe4 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&, QTypedArrayData::iterator const&) (this=this@entry=0x5bf37c43add0, state=..., mergingIdxIt=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.99.0/work/kxmlgui-5.99.0/src/kxmlguifactory_p.cpp:209 #12 0x762a0afef21e in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=0x5bf37c43add0, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.99.0/work/kxmlgui-5.99.0/src/kxmlguifactory_p.cpp:181 #13 0x762a0afef259 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.99.0/work/kxmlgui-5.99.0/src/kxmlguifactory_p.cpp:185 #14 0x762a0afef259 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.99.0/work/kxmlgui-5.99.0/src/kxmlguifactory_p.cpp:185 #15 0x762a0afe7ed7 in KXMLGUIFactory::plugActionList(KXMLGUIClient*, QString const&, QList const&) (this=0x5bf37c213560, client=client@entry=0x5bf37d0bb3a0, name=..., actionList=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.99.0/work/kxmlgui-5.99.0/src/kxmlguifactory.cpp:564 #16 0x762a0afdeaa9 in KXMLGUIClient::plugActionList(QString const&, QList const&) (this=this@entry=0x5bf37d0bb3a0, name=..., actionList=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.99.0/work/kxmlgui-5.99.0/src/kxmlguiclient.cpp:697 #17 0x762a0a00828b in PimCommon::PluginInterface::initializePluginActions(QString const&, KXMLGUIClient*) (this=, prefix=..., guiClient=0x5bf37d0bb3a0) at /var/tmp/portage/kde-apps/pimcommon-22.08.3/work/pimcommon-22.08.3/src/pimcommonakonadi/genericplugins/plugininterface.cpp:152 #18 0x762a14664550 in KMMainWidget::initializePluginActions() (this=0x762948117c70) at /var/tmp/portage/kde-apps/kmail-22.08.3-r1/work/kmail-22.08.3/src/kmmainwidget.cpp:4182 #19 0x762a1466f734 in KMMainWidget::slotShowStartupFolder() (this=0x762948117c70) at /var/tmp/portage/kde-apps/kmail-22.08.3-r1/work/kmail-22.08.3/src/kmmainwidget.cpp:4088 #20 0x762a0b748f46 in QObject::event(QEvent*) (this=0x762948117c70, e=0x5bf37c480580) at /var/tmp/portage/dev-qt/qtcore-5.15.8-r1/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:1347 #21 0x762a0c0f5a6f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x762948117c70, e=0x5bf37c480580) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qapplication.cpp:3640 #22 0x762a0b71d318 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x762948117c70,
[kmail2] [Bug 422095] Bad printout quality of kmail
https://bugs.kde.org/show_bug.cgi?id=422095 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu --- Comment #7 from Erik Quaeghebeur --- The default print quality is so bad, that it would be better to only offer export/print to pdf (allowing for margin setting) and drop the current print result. Perhaps there is some opendesktop standard for opening files with their default application and open the print dialog? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 400565] Correctly deal with multiple multipart/alternative parts in a single message
https://bugs.kde.org/show_bug.cgi?id=400565 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Erik Quaeghebeur --- Still not supported and still fails ungracefully. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 459299] Kmail composer does not offer contact suggestions for auto-completion.
https://bugs.kde.org/show_bug.cgi?id=459299 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu --- Comment #3 from Erik Quaeghebeur --- (In reply to Laurent Montel from comment #1) > Fixed in 5.21.1 Is there a patch I can use for 5.20.3? Perhaps cherry-picking a certain commit? My distribution will not change to 5.21 soon and this is very annoying. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 364876] System log: kontact: Cannot open "/usr/share/zoneinfo/Eastern Standard Time"
https://bugs.kde.org/show_bug.cgi?id=364876 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #9 from Erik Quaeghebeur --- Cannot reproduce anymore. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 383853] IMAP flag changes should not create a new message
https://bugs.kde.org/show_bug.cgi?id=383853 Erik Quaeghebeur changed: What|Removed |Added Version|5.5.3 |5.20.3 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Erik Quaeghebeur --- Still present. -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 364178] contact completion gives addressbook suggestions last
https://bugs.kde.org/show_bug.cgi?id=364178 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Erik Quaeghebeur --- I can't test LDAP completion anymore, but the other parts of this report seem to be mostly fixed. As the linked bug covers LDAP, I'll close this one. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 384098] request: better support for address list group syntax
https://bugs.kde.org/show_bug.cgi?id=384098 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Erik Quaeghebeur --- Still problematic. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372066] kmail mangles the mime structure of some IMAP messages
https://bugs.kde.org/show_bug.cgi?id=372066 Erik Quaeghebeur changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Erik Quaeghebeur --- Yes, I checked the same message and the problem is still there. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 452444] KMail crashed on quit
https://bugs.kde.org/show_bug.cgi?id=452444 --- Comment #5 from Erik Quaeghebeur --- Created attachment 153212 --> https://bugs.kde.org/attachment.cgi?id=153212=edit New crash information added by DrKonqi kmail (5.20.3 (22.04.3)) using Qt 5.15.5 KMail was not responsive (gear icon shown for a mailbox but nothing happening), so I closed it upon restarting, it crashed. -- Backtrace (Reduced): #4 0x7772fca428a8 in QScopedPointer >::operator->() const (this=0x8) at /var/tmp/portage/dev-qt/qtwidgets-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 [...] #7 QAction::setText(QString const&) (this=this@entry=0x0, text=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/widgets/kernel/qaction.cpp:714 #8 0x777304f5b0c2 in KMMainWidget::updateFolderMenu() (this=0x5d0267b605b0) at /var/tmp/portage/kde-apps/kmail-22.04.3/work/kmail-22.04.3/src/kmmainwidget.cpp:4037 #9 0x777304f65ccd in KMMainWidget::setupActions() (this=0x5d0267b605b0) at /var/tmp/portage/kde-apps/kmail-22.04.3/work/kmail-22.04.3/src/kmmainwidget.cpp:3399 #10 0x777304f6b789 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) (this=this@entry=0x5d0267b605b0, parent=parent@entry=0x5d0253428bc0, aGUIClient=aGUIClient@entry=0x5d0253428c38, actionCollection=actionCollection@entry=0x5d0254402670, config=...) at /var/tmp/portage/kde-apps/kmail-22.04.3/work/kmail-22.04.3/src/kmmainwidget.cpp:242 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 366398] add "Delete Attachments" menu entry (complementary to "Save Attachments")
https://bugs.kde.org/show_bug.cgi?id=366398 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Version|5.1.3 |5.21.2 Severity|minor |wishlist --- Comment #4 from Erik Quaeghebeur --- Functionality not yet implemented. -- You are receiving this mail because: You are the assignee for the bug.
[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 Erik Quaeghebeur changed: What|Removed |Added Platform|Neon|unspecified OS|Linux |All Summary|Kmail doesn't sync message |Store Kmail (Akonadi) tags |tags over different devices |in IMAP flags to enable ||syncing between mail ||clients -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 418784] kmail crashes is unresponsive after startup, then crashes when restarting
https://bugs.kde.org/show_bug.cgi?id=418784 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 414588] KMail crashes when restarting after closing when syncing is stuck at 99%
https://bugs.kde.org/show_bug.cgi?id=414588 Erik Quaeghebeur changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Erik Quaeghebeur --- I haven't had a crash like this for a while, so I'll mark it WORKSFORME. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 414922] crash of akonadictl
https://bugs.kde.org/show_bug.cgi?id=414922 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Erik Quaeghebeur --- I haven't had this crash for a while, so marking as WORKSFORME. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 415576] kmail crashes after restarting because no new mail was being fetched
https://bugs.kde.org/show_bug.cgi?id=415576 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Erik Quaeghebeur --- KMail crashes are hard to reproduce even if they are not resolved. In any case, I haven't come across something like this crash for a while, so I'll mark it as WORKSFORME. -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453676] Meeting reminder flood and sometimes kalendarac crashes after login
https://bugs.kde.org/show_bug.cgi?id=453676 --- Comment #2 from Erik Quaeghebeur --- Created attachment 152330 --> https://bugs.kde.org/attachment.cgi?id=152330=edit New crash information added by DrKonqi kalendarac (5.20.3) using Qt 5.15.5 - What I was doing when the application crashed: I was restaring the akonadi server via akonadiconsole -- Backtrace (Reduced): #7 0x795014e07cd7 in qt_message_fatal (message=..., context=...) at /var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/global/qlogging.cpp:1914 #8 QMessageLogger::fatal (this=this@entry=0x7fffb4012a00, msg=msg@entry=0x795013ef8198 "QWidget: Cannot create a QWidget without QApplication") at /var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/global/qlogging.cpp:893 #9 0x795013b21d42 in QWidgetPrivate::init (this=, parentWidget=, f=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/widgets/kernel/qwidget.cpp:981 #10 0x795013d413bf in QDialog::QDialog (this=0x639898de1050, parent=0x0, f=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/widgets/dialogs/qdialog.cpp:400 #11 0x7950141c0ece in KMessageBox::sorry(QWidget*, QString const&, QString const&, QFlags) () from /usr/lib64/libKF5WidgetsAddons.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[Reminder Daemon] [Bug 453676] Meeting reminder flood and sometimes kalendarac crashes after login
https://bugs.kde.org/show_bug.cgi?id=453676 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 458160] New: kmail renders calendar invites with a large delay
https://bugs.kde.org/show_bug.cgi?id=458160 Bug ID: 458160 Summary: kmail renders calendar invites with a large delay Product: kmail2 Version: 5.20.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- SUMMARY When opening mails containing a calendar invite (multipart/alternative with parts text/plain, text/html, and text/calendar), kmail nicely formats them, with buttons for invitation response actions. However, it takes a long time for these messages to be rendered, i.e., the time between opening them and seeing anything but white is long (23 seconds on a very fast laptop), which makes the feature inconvenient. STEPS TO REPRODUCE 1. Open calendar invite mail OBSERVED RESULT See blank space for a long time EXPECTED RESULT See rendered invite almost immediately SOFTWARE/OS VERSIONS KDE Plasma Version: 5.96.0 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION In my logs, I see the following right after opening the calendar invite mail. I assume that this activity is related to the fact that a list of nearby events are shown at the bottom of the invite mail. I assume that something going wrong here is what causes the large delay. akonadiserver[1617]: org.kde.pim.akonadiserver.search: Executing search "kmail2-3636980645-SearchSession" akonadiserver[1617]: org.kde.pim.akonadiserver.search: Search "kmail2-3636980645-SearchSession" done (without remote search) akonadiserver[1617]: org.kde.pim.akonadiserver: ItemRetrievalJob for request 511 finished akonadiserver[1617]: org.kde.pim.akonadiserver: ItemRetrievalJob for request 512 finished kmail[2754]: parse error from icalcomponent_new_from_string. string= "" kmail[2754]: org.kde.pim.calendar_serializer: Failed to parse incidence! Item id = 323784 Storage collection id 209 parentCollectionId = -4134 kmail[2754]: org.kde.pim.calendar_serializer: "" kmail[2754]: org.kde.pim.akonadicore: Unable to deserialize payload part: "RFC822" in item 323784 collection -4134 kmail[2754]: org.kde.pim.akonadicore: payload data was: "" [LAST 5 LINES REPEATED 9 TIMES FOR DIFFERENT ‘items’ AND TWO DIFFERENT ‘collections’] akonadiserver[1617]: org.kde.pim.akonadiserver: ItemRetrievalJob for request 515 finished akonadiserver[1617]: org.kde.pim.akonadiserver: ItemRetrievalJob for request 514 finished kmail[2754]: org.kde.pim.akonadicalendar: Discarding event with invalid DTSTART. identifier= "bcf67360-f30a-47c5-b40c-7ea81db35e6a_KABC_Birthday" ; summary= "Verjaardag van " kmail[2754]: org.kde.pim.akonadicalendar: Discarding event with invalid DTSTART. identifier= "15f9ece3-7d43-4705-b29d-7ae65ce45c60_KABC_Birthday" ; summary= "Verjaardag van " kmail[2754]: kf.calendarcore: hierarchy loop between "5a0b7b9c-81ad-456f-bfdc-6b8c285c356e" and "9884a435-85fd-435d-b300-367cfb2968bb" [LAST LINE REPEATED 10 TIMES FOR DIFFERENT PAIRS OF UUIDS] kmail[2754]: org.kde.pim.akonadicalendar: Unable to fetch incidences: "Invalid item or payload: 308122" [LAST LINE REPEATED 236 TIMES FOR DIFFERENT ‘items’] kmail[2754]: org.kde.pim.text_calendar: Unable to fetch incidences: "Invalid item or payload: 313658" kmail[2754]: kf.xmlgui: Index 86 is not within range (0 - 20 ) -- 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 #18 from Erik Quaeghebeur --- Created attachment 151247 --> https://bugs.kde.org/attachment.cgi?id=151247=edit New crash information added by DrKonqi akonadi_imap_resource (5.20.3 (22.04.3)) using Qt 5.15.5 - What I was doing when the application crashed: Trying to restart an IMAP instance that had not visible state (empty instead of ‘Ready’ or something like that) -- Backtrace (Reduced): #4 0x7322192f4c99 in QScopedPointer >::operator->() const (this=) at /var/tmp/portage/dev-qt/qtcore-5.15.5-r2/work/qtbase-everywhere-src-5.15.5/include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 [...] #7 QSettings::setValue(QString const&, QVariant const&) (this=this@entry=0x0, key=..., value=...) at /var/tmp/portage/dev-qt/qtcore-5.15.5-r2/work/qtbase-everywhere-src-5.15.5/src/corelib/io/qsettings.cpp:3271 #8 0x73221ac3f4dd in Akonadi::AgentBase::setOnline(bool) (this=0x7ffc706bf100, state=true) at /var/tmp/portage/kde-apps/akonadi-22.04.3/work/akonadi-22.04.3/src/agentbase/agentbase.cpp:1000 #9 0x5e0fec677404 in ImapResourceBase::onConnectDone(int, QString const&) (this=0x7ffc706bf100, errorCode=, errorString=) at /var/tmp/portage/kde-apps/kdepim-runtime-22.04.3/work/kdepim-runtime-22.04.3/resources/imap/imapresourcebase.cpp:271 #10 0x732219394e86 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc706be990, r=0x7ffc706bf100, this=0x5e0fed94c350) at /var/tmp/portage/dev-qt/qtcore-5.15.5-r2/work/qtbase-everywhere-src-5.15.5/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 453297] KMail + Akonadi crash
https://bugs.kde.org/show_bug.cgi?id=453297 --- Comment #1 from Erik Quaeghebeur --- Created attachment 150333 --> https://bugs.kde.org/attachment.cgi?id=150333=edit New crash information added by DrKonqi kmail (5.19.3 (21.12.3)) using Qt 5.15.4 - What I was doing when the application crashed: I was restarting kmail for a second time after I had closed it down because it was stuck loading folder contents (likely because akonadi was stuck…). The first time also kmail crashed, but in a different way, but for that no crash report could be sent, for some reason. -- Backtrace (Reduced): #4 0x7964fe145417 in std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/g++-v11/bits/atomic_base.h:481 #5 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.4-r2/work/qtbase-everywhere-src-5.15.4/include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed() const (this=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.4-r2/work/qtbase-everywhere-src-5.15.4/include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #7 QtPrivate::RefCount::isShared() const (this=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.4-r2/work/qtbase-everywhere-src-5.15.4/include/QtCore/../../src/corelib/tools/qrefcount.h:101 #8 QList::append(QWidget* const&) (this=0x598b1af40100, t=@0x7ffce7a3af00: 0x598b1b13ae70) at /var/tmp/portage/dev-qt/qtwidgets-5.15.4-r2/work/qtbase-everywhere-src-5.15.4/include/QtCore/../../src/corelib/tools/qlist.h:622 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 453297] KMail + Akonadi crash
https://bugs.kde.org/show_bug.cgi?id=453297 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 454182] New: message (part) size display: please follow BinaryUnitDialect everywhere
https://bugs.kde.org/show_bug.cgi?id=454182 Bug ID: 454182 Summary: message (part) size display: please follow BinaryUnitDialect everywhere Product: kmail2 Version: 5.19.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Depends on: 57240 Target Milestone: --- SUMMARY KMail does not seem to follow the BinaryUnitDialect config option everywhere. Likely it is just a matter of replacing some function with some higher-level ones, as in a few places, KMail does do the right thing. STEPS TO REPRODUCE 1. Set BinaryUnitDialect=2 in [Locale] section of $KDEHOME/.config/kdeglobals (setting to metric/SI instead of IEC) 2. Start KMail 3. Look at message sizes is message list, part sizes in part list and attachment list OBSERVED RESULT IEC formatting is used instead of metric for part sizes in part list and attachment list (metric is used in the message list) EXPECTED RESULT Metric formatting is used everywhere SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION The BinaryUnitDialect config option is described in Bug 57240. This option is for now still without a GUI, but Bug 364321 makes it clear this is about to change. So apps like KMail should be made ready to follow BinaryUnitDialect. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=57240 [Bug 57240] Display file size in kibibyte, mebibyte... ? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 452444] KMail crashed on quit
https://bugs.kde.org/show_bug.cgi?id=452444 --- Comment #2 from Erik Quaeghebeur --- Created attachment 149017 --> https://bugs.kde.org/attachment.cgi?id=149017=edit New crash information added by DrKonqi kmail (5.19.3 (21.12.3)) using Qt 5.15.3 - What I was doing when the application crashed: Closing/Restarting KMail after restarting akonadi. The trace seems to be more complete. -- Backtrace (Reduced): #4 0x7131ac3ef7d8 in QScopedPointer >::operator->() const (this=0x8) at /var/tmp/portage/dev-qt/qtwidgets-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 [...] #7 QAction::setText(QString const&) (this=this@entry=0x0, text=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.3/work/qtbase-everywhere-src-5.15.3/src/widgets/kernel/qaction.cpp:714 #8 0x7131b49193f2 in KMMainWidget::updateFolderMenu() (this=0x71311c623240) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwidget.cpp:4043 #9 0x7131b4923ef1 in KMMainWidget::setupActions() (this=0x71311c623240) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwidget.cpp:3405 #10 0x7131b4929819 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) (this=this@entry=0x71311c623240, parent=parent@entry=0x5dfd13c5b600, aGUIClient=aGUIClient@entry=0x5dfd13c5b678, actionCollection=actionCollection@entry=0x5dfd13a4e070, config=...) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwidget.cpp:251 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 453990] New: Crash when restarting the akonadi server
https://bugs.kde.org/show_bug.cgi?id=453990
Bug ID: 453990
Summary: Crash when restarting the akonadi server
Product: Akonadi
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: server
Assignee: kdepim-bugs@kde.org
Reporter: bugs.kde@e3q.eu
Target Milestone: ---
Application: akonadiserver (5.19.3 (21.12.3))
(Compiled from sources)
Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.32-gentoo-r1-a x86_64
Windowing System: X11
Distribution: Gentoo/Linux
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Akonadi seemed stalled (KMail did not refresh when requesting one). So I
restarted it using akonadiconsole. That caused this crash.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
[KCrash Handler]
#4 std::default_delete::operator() (__ptr=0x110,
this=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/bits/unique_ptr.h:79
#5 std::unique_ptr >::~unique_ptr
(this=, __in_chrg=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/bits/unique_ptr.h:361
#6 __gnu_cxx::new_allocator >
>::destroy > > (__p=,
this=0x7fffdec49b18) at
/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/ext/new_allocator.h:168
#7
std::allocator_traits > >
>::destroy > > (__p=,
__a=...) at
/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/bits/alloc_traits.h:535
#8 std::vector >,
std::allocator > > >::_M_erase
(__position=std::unique_ptr = {get() =
0x5ec11bfabce0}, this=0x7fffdec49b18) at
/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/bits/vector.tcc:177
#9 std::vector >,
std::allocator > > >::erase
(__position=std::unique_ptr = {get() =
0x5ec11bfabce0}, this=0x7fffdec49b18) at
/usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/bits/stl_vector.h:1431
#10 Akonadi::Server::AkonadiServer::connectionDisconnected
(this=0x7fffdec49a90) at
/var/tmp/portage/kde-apps/akonadi-21.12.3/work/akonadi-21.12.3/src/server/akonadi.cpp:234
#11 0x729492fdfa16 in QObject::event (this=0x7fffdec49a90,
e=0x5ec11bfb20d0) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:1314
#12 0x729492fb4105 in doNotify (event=0x5ec11bfb20d0,
receiver=0x7fffdec49a90) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qcoreapplication.cpp:1154
#13 QCoreApplication::notify (event=, receiver=,
this=) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qcoreapplication.cpp:1140
#14 QCoreApplication::notifyInternal2 (receiver=0x7fffdec49a90,
event=0x5ec11bfb20d0) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qcoreapplication.cpp:1064
#15 0x729492fb77a5 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x5ec11bfa5da0) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qcoreapplication.cpp:1821
#16 0x729493006853 in postEventSourceDispatch (s=0x5ec11bfab2a0) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qeventdispatcher_glib.cpp:277
#17 0x72949157616b in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#18 0x729491576428 in ?? () from /usr/lib64/libglib-2.0.so.0
#19 0x7294915764df in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#20 0x7294930062e4 in QEventDispatcherGlib::processEvents
(this=0x5ec11bfa8710, flags=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qeventdispatcher_glib.cpp:423
#21 0x729492fb2b2b in QEventLoop::exec (this=this@entry=0x7fffdec49970,
flags=..., flags@entry=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/global/qflags.h:69
#22 0x729492fbb15d in QCoreApplication::exec () at
/var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/global/qflags.h:121
#23 0x5ec11affbf85 in AkApplicationBase::exec
(this=this@entry=0x7fffdec49a60) at
/var/tmp/portage/kde-apps/akonadi-21.12.3/work/akonadi-21.12.3/src/shared/akapplication.cpp:109
#24 0x5ec11ae8696e in main (argc=, argv=) at
/var/tmp/portage/kde-apps/akonadi-21.12.3/work/akonadi-21.12.3/src/server/main.cpp:65
[Inferior 1 (process 12435) detached]
Possible duplicates by query: bug 453753, bug 453457, bug 453442, bug 453371,
bug 453237.
Reported using DrKonqi
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 421432] Kmail crashed on start after seeming stuck on syncing my mailbox
https://bugs.kde.org/show_bug.cgi?id=421432 --- Comment #2 from Erik Quaeghebeur --- Created attachment 148238 --> https://bugs.kde.org/attachment.cgi?id=148238=edit New crash information added by DrKonqi kmail (5.19.3 (21.12.3)) using Qt 5.15.3 - What I was doing when the application crashed: Trying to restart kmail after it had crashed on quitting after it was stuck loading the contents of a folder. This crash report's backtrace contains more details and is for a recent version of kmail/qt. -- Backtrace (Reduced): #8 QList::append(QWidget* const&) (this=0x60101, t=@0x7fff63999230: 0x5b36679e1ed0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/tools/qlist.h:622 #9 0x7f56ed6b6149 in QWidget::insertAction(QAction*, QAction*) (this=this@entry=0x5b36679e1ed0, before=, before@entry=0x0, action=0x5b36679d0750) at /var/tmp/portage/dev-qt/qtwidgets-5.15.3/work/qtbase-everywhere-src-5.15.3/src/widgets/kernel/qwidget.cpp:3129 #10 0x7f56ec56acc2 in KXMLGUI::ActionList::plug(QWidget*, int) const (this=this@entry=0x5b36679b1fc0, container=0x5b36679e1ed0, index=) at /var/tmp/portage/kde-frameworks/kxmlgui-5.90.0/work/kxmlgui-5.90.0/src/kxmlguifactory_p.cpp:33 #11 0x7f56ec56f104 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&, QTypedArrayData::iterator const&) (this=this@entry=0x5b3667c6e130, state=..., mergingIdxIt=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.90.0/work/kxmlgui-5.90.0/src/kxmlguifactory_p.cpp:230 #12 0x7f56ec56f33e in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=0x5b3667c6e130, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.90.0/work/kxmlgui-5.90.0/src/kxmlguifactory_p.cpp:202 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 452444] KMail crashed on quit
https://bugs.kde.org/show_bug.cgi?id=452444 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 452444] KMail crashed on quit
https://bugs.kde.org/show_bug.cgi?id=452444 --- Comment #1 from Erik Quaeghebeur --- Created attachment 148237 --> https://bugs.kde.org/attachment.cgi?id=148237=edit New crash information added by DrKonqi kmail (5.19.3 (21.12.3)) using Qt 5.15.3 - What I was doing when the application crashed: Loading of content of a mailbox stalled, so I wanted to restart kmail. It crashed on quitting (Ctrl-Q). As compared to the previous bugreport, this one shows it is still present in the more recent version 21.12.3 of kmail. -- Backtrace (Reduced): #4 0x7218c32707d8 in QScopedPointer >::operator->() const (this=0x8) at /var/tmp/portage/dev-qt/qtwidgets-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 [...] #7 QAction::setText(QString const&) (this=this@entry=0x0, text=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.3/work/qtbase-everywhere-src-5.15.3/src/widgets/kernel/qaction.cpp:714 #8 0x7218cb7953f2 in KMMainWidget::updateFolderMenu() (this=0x6279476bff20) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwidget.cpp:4043 #9 0x7218cb79fef1 in KMMainWidget::setupActions() (this=0x6279476bff20) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwidget.cpp:3405 #10 0x7218cb7a5819 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) (this=this@entry=0x6279476bff20, parent=parent@entry=0x62793c5f5da0, aGUIClient=aGUIClient@entry=0x62793c5f5e18, actionCollection=actionCollection@entry=0x62793cac7fd0, config=...) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwidget.cpp:251 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 451730] akonadi server crashes upon restart
https://bugs.kde.org/show_bug.cgi?id=451730 Erik Quaeghebeur changed: What|Removed |Added Version|5.18.3 |5.19.3 --- Comment #1 from Erik Quaeghebeur --- Still happens with 5.19.3: Application: akonadi_control (akonadi_control), signal: Aborted [KCrash Handler] #4 0x7ddf74554d0c in () at /lib64/libc.so.6 #5 0x7ddf74507a62 in raise () at /lib64/libc.so.6 #6 0x7ddf744f2449 in abort () at /lib64/libc.so.6 #7 0x7ddf74980cc3 in qt_message_fatal (message=..., context=...) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/global/qlogging.cpp:1914 #8 QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffcf0029000, msg=msg@entry=0x6098a6352980 "Cannot rename log file '%s' to '%s': %s") at /var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/global/qlogging.cpp:893 #9 0x6098a63210da in akInit(QString const&) (appName=...) at /var/tmp/portage/kde-apps/akonadi-21.12.3/work/akonadi-21.12.3/src/shared/akdebug.cpp:230 #10 0x6098a6345483 in AkApplicationBase::init() (this=this@entry=0x7ffcf00291b0) at /var/tmp/portage/kde-apps/akonadi-21.12.3/work/akonadi-21.12.3/src/shared/akapplication.cpp:47 #11 0x6098a6321542 in AkUniqueApplicationImpl::AkUniqueApplicationImpl(int&, char**, QString const&, QLoggingCategory const&) (loggingCategory=..., serviceName=..., argv=, argc=@0x7ffcf002912c: 1, this=0x7ffcf00291b0) at /var/tmp/portage/kde-apps/akonadi-21.12.3/work/akonadi-21.12.3/src/shared/akapplication.h:81 #12 main(int, char**) (argc=, argv=) at /var/tmp/portage/kde-apps/akonadi-21.12.3/work/akonadi-21.12.3/src/akonadicontrol/main.cpp:47 [Inferior 1 (process 598667) detached] -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 452444] New: KMail crashed on quit
https://bugs.kde.org/show_bug.cgi?id=452444 Bug ID: 452444 Summary: KMail crashed on quit Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: kmail (5.19.3 (21.12.3)) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.15.32-gentoo-r1-a x86_64 Windowing System: X11 Distribution: Gentoo/Linux DrKonqi: 5.23.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was opening a mail, but it did not load. Therefore, I quit the application, which triggered this crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x734216b897d8 in QScopedPointer >::operator->() const (this=0x8) at ../../include/QtCore/../../../qtbase-7c6c0030cf80ef7b9ace42996b0e0c3a72f76860/src/corelib/tools/qscopedpointer.h:118 #5 qGetPtrHelper > >(QScopedPointer >&) (ptr=...) at ../../include/QtCore/../../../qtbase-7c6c0030cf80ef7b9ace42996b0e0c3a72f76860/src/corelib/global/qglobal.h:1143 #6 QAction::d_func() (this=this@entry=0x0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.2-r12/work/qtbase-7c6c0030cf80ef7b9ace42996b0e0c3a72f76860/src/widgets/kernel/qaction.h:63 #7 QAction::setText(QString const&) (this=this@entry=0x0, text=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.2-r12/work/qtbase-7c6c0030cf80ef7b9ace42996b0e0c3a72f76860/src/widgets/kernel/qaction.cpp:714 #8 0x73421f0953f2 in KMMainWidget::updateFolderMenu() (this=0x734118106e60) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwidget.cpp:4043 #9 0x73421f09fef1 in KMMainWidget::setupActions() (this=0x734118106e60) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwidget.cpp:3405 #10 0x73421f0a5819 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) (this=this@entry=0x734118106e60, parent=parent@entry=0x652703b06800, aGUIClient=aGUIClient@entry=0x652703b06878, actionCollection=actionCollection@entry=0x652702bf35b0, config=...) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwidget.cpp:251 #11 0x73421f04e5aa in KMMainWin::KMMainWin(QWidget*) (this=this@entry=0x652703b06800, __in_chrg=, __vtt_parm=) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmmainwin.cpp:49 #12 0x73421f060607 in KMKernel::openReader(bool, bool) (this=, onlyCheck=, startInTray=) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmkernel.cpp:565 #13 0x73421f06597f 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&) (this=0x7ffe4e06dbe0, mailto=, check=, startInTray=, to=..., cc=..., bcc=..., subj=..., body=..., messageFile=..., attachURLs=..., customHeaders=..., replyTo=..., inReplyTo=..., identity=...) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmkernel.cpp:1276 #14 0x73421f06729b in KMKernel::handleCommandLine(bool, QStringList const&, QString const&) (this=, noArgsOpensReader=noArgsOpensReader@entry=true, args=..., workingDir=...) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/kmkernel.cpp:476 #15 0x652701705842 in KMailApplication::activate(QStringList const&, QString const&) (this=, args=..., workingDir=...) at /var/tmp/portage/kde-apps/kmail-21.12.3/work/kmail-21.12.3/src/main.cpp:100 #16 0x73421f1ae123 in KontactInterface::PimUniqueApplication::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7ffe4e06d0e0, _o=) at /var/tmp/portage/kde-apps/kontactinterface-21.12.3/work/kontactinterface-21.12.3_build/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:87 #17 KontactInterface::PimUniqueApplication::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=0x7ffe4e06d0e0) at /var/tmp/portage/kde-apps/kontactinterface-21.12.3/work/kontactinterface-21.12.3_build/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:79 #18 0x73421f1ae3d3 in KontactInterface::PimUniqueApplication::qt_metacall(QMetaObject::Call, int, void**) (this=0x7ffe4e06dbc0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7ffe4e06d0e0) at /var/tmp/portage/kde-apps/kontactinterface-21.12.3/work/kontactinterface-21.12.3_build/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:124 #19 0x734215895d1b in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&,
[kmail2] [Bug 283020] Store Kmail Tags in IMAP flags, like Thunderbird
https://bugs.kde.org/show_bug.cgi?id=283020 --- Comment #30 from Erik Quaeghebeur --- I've been looking at this issue again. The KMail/Akonadi codebase is still to scary for me in most places, so I tried to circumvent it and add this functionality using SQL triggers directly in Akonadi's database. I'm using the SQLite backend, but this should be similar for MySQL and Postgresql. *TLDR: Using only SQL triggers, a flag added by another client can be synced via IMAP to an Akonadi tag, but deleting it from another client does not work. Adding and deleting from KMail does not sync to the IMAP server.* For my experiments, I used DB browser for SQLite <https://sqlitebrowser.org/> to add triggers and look at the database; it is a bit more convenient than the functionality in Akonadiconsole. To test, I created two tags in Akonadi (via KMail's config) and these have ids 3 and 5 in the TagTable. I used one flag, with id 57 in the FlagTable. Flag 57 should be synced to tag 3. Tag 5 was used for deeper investigations. (Obviously, the trigger would need to be made flag/tag-agnostic, but this would require adding a FlagTagRelation table, which would go to far for an initial test. It would also have been a waste of time.) Then, I created the following triggers: 1. Adding tag 3 when flag 57 arrives in the database: --- create trigger "insert_tag_from_flag" after insert on "PimItemFlagRelation" when NEW.Flag_Id is 57 begin insert or ignore into "PimItemTagRelation" values (NEW.PimItem_id, 3); end --- This works. The tag is added to the mail in KMail if in another client (Trojita, Thunderbird) the tag is added to the mail. 2. Adding flag 57 when tag 3 arrives in the database: --- create trigger "insert_flag_from_tag" after insert on "PimItemTagRelation" when NEW.Tag_Id is 3 begin insert or ignore into "PimItemFlagRelation" values (NEW.PimItem_id, 57); end --- This does not sync. The flag is added to the database, alright, but Akonadi isn't aware of it and does not propagate it to the server. ⇒ This needs to be coded in Akonadi/KMail. 3. Deleting tag 3 when flag 57 is removed in the database: --- create trigger "delete_tag_from_flag" after delete on "PimItemFlagRelation" when OLD.Flag_Id is 57 begin delete from "PimItemTagRelation" where "PimItem_id" == "OLD.PimItem_id" and "Tag_id" == 3; insert into "PimItemTagRelation" values (OLD.PimItem_id, 5); end --- This does not persist. For a moment, the tag is removed, but then it is added again, likely from another in-memory data structure. (I was keeping the mail folder containing the mail with removed flag open in KMail.) To verify that indeed the database commit works, the additional insert was added, which confirms it does. ⇒ This needs to be coded in Akonadi/KMail. 4. Removing flag 57 when tag 3 is deleted in the database: --- create trigger "delete_flag_from_tag" after delete on "PimItemTagRelation" when OLD.Tag_Id is 3 begin delete from "PimItemFlagRelation" where "PimItem_id" == "OLD.PimItem_id" and "Flag_id" == 57; end --- This does not sync. The flag is removed from the database, alright, but Akonadi isn't aware of it and does not propagate it to the server. ⇒ This needs to be coded in Akonadi/KMail. So, while insightful to me, this idea doesn't really bring us closer. Into the code we must go. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 451730] New: akonadi server crashes upon restart
https://bugs.kde.org/show_bug.cgi?id=451730 Bug ID: 451730 Summary: akonadi server crashes upon restart Product: Akonadi Version: 5.18.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: akonadiserver (akonadiserver), signal: Aborted [KCrash Handler] #4 0x747c426a952e in raise () from /lib64/libc.so.6 #5 0x747c42693546 in abort () from /lib64/libc.so.6 #6 0x747c42afccc3 in qt_message_fatal (message=..., context=...) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffcacec3d80, msg=msg@entry=0x5a759e78a5d0 "Cannot rename log file '%s' to '%s': %s") at /var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/global/qlogging.cpp:893 #8 0x5a759e5e2242 in akInit (appName=...) at /var/tmp/portage/kde-apps/akonadi-21.08.3/work/akonadi-21.08.3/src/shared/akdebug.cpp:230 #9 0x5a759e75a383 in AkApplicationBase::init (this=this@entry=0x7ffcacec3f00) at /var/tmp/portage/kde-apps/akonadi-21.08.3/work/akonadi-21.08.3/src/shared/akapplication.cpp:47 #10 0x5a759e5e25cf in AkApplicationImpl::AkApplicationImpl (loggingCategory=..., argv=, argc=@0x7ffcacec3e9c: 1, this=0x7ffcacec3f00) at /var/tmp/portage/kde-apps/akonadi-21.08.3/work/akonadi-21.08.3/src/shared/akapplication.h:70 #11 main (argc=, argv=) at /var/tmp/portage/kde-apps/akonadi-21.08.3/work/akonadi-21.08.3/src/server/main.cpp:31 [Inferior 1 (process 736685) detached] SUMMARY Akonadi was acting up again, with kmail showing te dreaded eternal loading message screen. So I restarted it, leading to the crash with backtrace above. I can't reliably reproduce it. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 (with KDE patches) -- 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 #17 from Erik Quaeghebeur --- Created attachment 147620 --> https://bugs.kde.org/attachment.cgi?id=147620=edit New crash information added by DrKonqi akonadi_imap_resource (5.18.3 (21.08.3)) using Qt 5.15.2 - What I was doing when the application crashed: Trying to toggle online/offline from unclear online/offline state (empty info in akonadiconsole) -- Backtrace (Reduced): #4 0x7b0237569399 in QScopedPointer >::operator->() const (this=) at ../../include/QtCore/../../../qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/tools/qscopedpointer.h:118 [...] #7 QSettings::setValue(QString const&, QVariant const&) (this=this@entry=0x0, key=..., value=...) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/io/qsettings.cpp:3271 #8 0x7b0238ff955d in Akonadi::AgentBase::setOnline(bool) (this=0x7ffef3c29750, state=false) at /var/tmp/portage/kde-apps/akonadi-21.08.3/work/akonadi-21.08.3/src/agentbase/agentbase.cpp:1003 #9 0x7b023902598d in Akonadi__StatusAdaptor::setOnline(bool) (state=, this=) at /var/tmp/portage/kde-apps/akonadi-21.08.3/work/akonadi-21.08.3_build/src/agentbase/statusadaptor.cpp:51 #10 0x7b0239025c43 in Akonadi__StatusAdaptor::qt_metacall(QMetaObject::Call, int, void**) (this=0x5f49ac78b510, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7ffef3c29110) at /var/tmp/portage/kde-apps/akonadi-21.08.3/work/akonadi-21.08.3_build/src/agentbase/statusadaptor.moc:238 -- 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 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 451620] akonadictl; sqlite: Error moving orphan items to collection 242 : Expression tree is too large (maximum depth 1000)
https://bugs.kde.org/show_bug.cgi?id=451620 --- Comment #1 from Erik Quaeghebeur --- I have investigated a bit further. Using a GUI for sqlite (sqlitebrowser), I familiarized myself a bit with the database and then looked into what was going on here: --- select distinct "collectionId" as "id" from "PimItemTable" except select distinct "id" from "CollectionTable" order by "id"; --- This returned 52 collections that where referenced by items, but apparently do not exist anymore. --- select "id" as "itemId", "collectionId" from "PimItemTable" where "collectionId" not in (select distinct "id" from "CollectionTable") order by "collectionId"; --- This returned 110689 items, the same as reported by akonadictl, so indeed these were the orphans mentioned. --- delete from "PimItemTable" where "collectionId" not in (select distinct "id" from "CollectionTable"); --- To fix the issue, I just removed them rather than creating a lost+found(?) collection (with id 242?) and updating the collectionId of the items to 242. After vacuuming (‘compress database’ under ‘Extra’ menu in sqlitebrowser), my database shrunk to less than half the size it had before (600+ to ~250 MB). So what seems to go wrong is that in the code *the list of orphans* resulting from a first query is used to build a second query to change their collectionId. Because this list is absurdly long, sqlite bails out. A possible fix would be to first find out if there are orphan collections (my first query listed) and if so, create as needed the lost+found collection and update the corresponding items in the way done by my last query above. Next, I dived into the code. I think the function in question can be found at https://invent.kde.org/pim/akonadi/-/blob/master/src/server/storagejanitor.cpp#L277. There, one can indeed see that a list of orphans is created on the C++ side (in the variable imapIds) and subsequently used to create the query to clean up the orphans. While the Qt functions for creating queries are mostly gibberish to me, what I can deduce, is that this is done in a roundabout, inefficient way, as compared to what my queries above do. Is there a reason for this? Finally, a point that must be addressed is why such orphans can even exist, as in the database schema for the creation of PimItemTable, I see: … collectionId BIGINT … CONSTRAINT PimItemTablecollectionId_Collectionid_fk FOREIGN KEY (collectionId) REFERENCES CollectionTable(id) ON UPDATE CASCADE ON DELETE CASCADE DEFERRABLE INITIALLY DEFERRED … which should in principle cascade the deletion of the collection to the deletion of items within that collection. I do not know what could have gone wrong, but it is worrying. N.B.: The above column definition+constraint can more compactly be done as collectionId BIGINT REFERENCES CollectionTable(id) ON UPDATE CASCADE ON DELETE CASCADE DEFERRABLE INITIALLY DEFERRED using the concept of column constraint: https://www.sqlite.org/syntax/column-constraint.html. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 451620] New: akonadictl; sqlite: Error moving orphan items to collection 242 : Expression tree is too large (maximum depth 1000)
https://bugs.kde.org/show_bug.cgi?id=451620
Bug ID: 451620
Summary: akonadictl; sqlite: Error moving orphan items to
collection 242 : Expression tree is too large (maximum
depth 1000)
Product: Akonadi
Version: 5.18.3
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: bugs.kde@e3q.eu
Target Milestone: ---
SUMMARY
I use akonadi with the sqlite backend. Running akonadictl results in an error
that seems to result from akonadi giving sqlite a query that is too long:
---
$ akonadictl fsck
[…]
Checking collection tree consistency...
Looking for items not belonging to a valid collection...
Found 110689 orphan items.
Error moving orphan items to collection 242 : Expression tree is too large
(maximum depth 1000) Kon statement niet uitvoeren
[…]
---
("Kon statement niet uitvoeren" means "Could not execute statement")
STEPS TO REPRODUCE
1. run akonadictl fsck again
OBSERVED RESULT
Error moving orphan items to collection 242 : Expression tree is too large
(maximum depth 1000) Kon statement niet uitvoeren
EXPECTED RESULT
orphans are cleaned up
SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2 (with https://community.kde.org/Qt5PatchCollection)
ADDITIONAL INFORMATION
I think this is sqlite-specific, given some search results on the web
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 451518] New: Use no or UTF-8 as default when non-ASCII characters are encountered in header
https://bugs.kde.org/show_bug.cgi?id=451518 Bug ID: 451518 Summary: Use no or UTF-8 as default when non-ASCII characters are encountered in header Product: kmail2 Version: 5.16.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Created attachment 147503 --> https://bugs.kde.org/attachment.cgi?id=147503=edit mail with UTF-8 character in ASCII header SUMMARY When a mail with some non-ASCII characters is encountered with the encoding of the header being (effectively) ASCII, KMail tries to decode it assuming ISO-8859-1. Because currently such occurrences tend to actually be UTF-8, this results in failed decodings in general. (I assume it was different in the past, when ISO-8859-1 was the most common ASCII-extension encoding used.) Obviously, the mail is malformed, because of the missing encoding information. So the strict thing to do is to show explicitly that the character(s) cannot be decoded, e.g., using the replacement character �. The lenient thing to do, nowadays, is to assume UTF-8. STEPS TO REPRODUCE 1. List folder with mail with non-encoded non-ISO-8895-1-character in header OBSERVED RESULT Observe that character is decoded as if it were ISO-8859-1 EXPECTED RESULT Observe that character is decoded as replacement character � or as if it were UTF-8. SOFTWARE/OS VERSIONS KMail: 5.18.3 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 (with https://community.kde.org/Qt5PatchCollection) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 451040] New: Akonadi EWS: Restrict what is synchronized (server-side subscription not working?)
https://bugs.kde.org/show_bug.cgi?id=451040 Bug ID: 451040 Summary: Akonadi EWS: Restrict what is synchronized (server-side subscription not working?) Product: Akonadi Version: 5.18.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: EWS Resource Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu CC: kri...@op.pl Target Milestone: --- In the configuration of an Akonadi EWS resource, there is a tab for selecting what to synchronize (server-side synchronization). For example, I'm only interested in a couple of mail folders currently and have selected those (this need not be a server-side subscription; local is fine). However, that does not impact what is actually synchronized, namely, everything. I would expect this setting to reduce the amount of things that are synchronized. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 448183] New: Messageviewer is confused by strange RFC2047-encoded header
https://bugs.kde.org/show_bug.cgi?id=448183 Bug ID: 448183 Summary: Messageviewer is confused by strange RFC2047-encoded header Product: kdepim Version: 5.16.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messageviewer Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Created attachment 145281 --> https://bugs.kde.org/attachment.cgi?id=145281=edit Example mail with RFC2047-encoded header that confuses messageviewer SUMMARY Headers can contain RFC2047-encoded (Q-encoded) fragments. I got a mail that containts such a header that confuses messageviewer into displaying it wrong. Namely, the Cc field is --- Cc: =?UTF-8?Q?comp=2Dneuro=40neuroinformatics=2Ebe_=3Ccomp=2Dneuro=40neuroinformati?= =?UTF-8?Q?cs=2Ebe=3E=2C=2C_connectionists=40cs=2Ecmu=2Eedu_=3Cconnectionists=40cs=2Ecmu=2Eed?= =?UTF-8?Q?u=3E=2C=2C_ml=2Dnews=40googlegroups=2Ecom_=3Cml=2Dnews=40googlegroups=2Ecom=3E=2C=2C_s?= =?UTF-8?Q?ystems=2Dneuroscience=40googlegroups=2Ecom_=3Csystems=2Dneuroscience=40g?= =?UTF-8?Q?ooglegroups=2Ecom=3E=2C=2C_maths=2Dneuronet=40lists=2Enottingham=2Eac=2Euk?= , rl-l...@googlegroups.com --- Everything in front of is decoded as if it were the display name for that address, namely, as the string --- "comp-ne...@neuroinformatics.be ,, connectioni...@cs.cmu.edu ,, ml-n...@googlegroups.com ,, systems-neuroscie...@googlegroups.com ,, maths-neuro...@lists.nottingham.ac.uk " --- whereas actually it should not have the quotes added. (There are issues with this list, the double commas, but that is not the problem here, I think.) The attached mail contains this Cc header. I've added the string above without the quotes to the Bcc header and it seems that the double commas confuse the header parser into displaying each address twice, so that is a second issue. SOFTWARE/OS VERSIONS messagelib version: 21.08.3 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2-r11 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 448024] New: KMail crashes on close after playing with tags
https://bugs.kde.org/show_bug.cgi?id=448024 Bug ID: 448024 Summary: KMail crashes on close after playing with tags Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: kmail (5.18.3 (21.08.3)) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.88.0 Operating System: Linux 5.15.12-gentoo-a x86_64 Windowing System: X11 Distribution: Gentoo/Linux DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I had just configures a tag and marked one message with that tag. Then KMail started blocking. (Unending trying-to-open message view.) Then I closed KMail, which causes the crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x796bf887b7d8 in QScopedPointer >::operator->() const (this=0x8) at ../../include/QtCore/../../../qtbase-7c6c0030cf80ef7b9ace42996b0e0c3a72f76860/src/corelib/tools/qscopedpointer.h:118 #5 qGetPtrHelper > >(QScopedPointer >&) (ptr=...) at ../../include/QtCore/../../../qtbase-7c6c0030cf80ef7b9ace42996b0e0c3a72f76860/src/corelib/global/qglobal.h:1143 #6 QAction::d_func() (this=this@entry=0x0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.2-r12/work/qtbase-7c6c0030cf80ef7b9ace42996b0e0c3a72f76860/src/widgets/kernel/qaction.h:63 #7 QAction::setText(QString const&) (this=this@entry=0x0, text=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.2-r12/work/qtbase-7c6c0030cf80ef7b9ace42996b0e0c3a72f76860/src/widgets/kernel/qaction.cpp:714 #8 0x796c00d7c082 in KMMainWidget::updateFolderMenu() (this=0x796b70008070) at /var/tmp/portage/kde-apps/kmail-21.08.3/work/kmail-21.08.3/src/kmmainwidget.cpp:3996 #9 0x796c00d8698e in KMMainWidget::setupActions() (this=0x796b70008070) at /var/tmp/portage/kde-apps/kmail-21.08.3/work/kmail-21.08.3/src/kmmainwidget.cpp:3384 #10 0x796c00d8bedd in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) (this=this@entry=0x796b70008070, parent=parent@entry=0x62c3586d5c90, aGUIClient=aGUIClient@entry=0x62c3586d5d08, actionCollection=actionCollection@entry=0x62c354e621f0, config=...) at /var/tmp/portage/kde-apps/kmail-21.08.3/work/kmail-21.08.3/src/kmmainwidget.cpp:249 #11 0x796c00d3508a in KMMainWin::KMMainWin(QWidget*) (this=this@entry=0x62c3586d5c90, __in_chrg=, __vtt_parm=) at /var/tmp/portage/kde-apps/kmail-21.08.3/work/kmail-21.08.3/src/kmmainwin.cpp:50 #12 0x796c00d47107 in KMKernel::openReader(bool, bool) (this=, onlyCheck=, startInTray=) at /var/tmp/portage/kde-apps/kmail-21.08.3/work/kmail-21.08.3/src/kmkernel.cpp:560 #13 0x796c00d4c47f 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&) (this=0x7ffcd3b1df80, mailto=, check=, startInTray=, to=..., cc=..., bcc=..., subj=..., body=..., messageFile=..., attachURLs=..., customHeaders=..., replyTo=..., inReplyTo=..., identity=...) at /var/tmp/portage/kde-apps/kmail-21.08.3/work/kmail-21.08.3/src/kmkernel.cpp:1269 #14 0x796c00d4dd0e in KMKernel::handleCommandLine(bool, QStringList const&, QString const&) (this=, noArgsOpensReader=noArgsOpensReader@entry=true, args=..., workingDir=...) at /var/tmp/portage/kde-apps/kmail-21.08.3/work/kmail-21.08.3/src/kmkernel.cpp:471 #15 0x62c34640d842 in KMailApplication::activate(QStringList const&, QString const&) (this=, args=..., workingDir=...) at /var/tmp/portage/kde-apps/kmail-21.08.3/work/kmail-21.08.3/src/main.cpp:100 #16 0x796c00e8f0f3 in KontactInterface::PimUniqueApplication::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7ffcd3b1d480, _o=) at /var/tmp/portage/kde-apps/kontactinterface-21.08.3/work/kontactinterface-21.08.3_build/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:87 #17 KontactInterface::PimUniqueApplication::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=0x7ffcd3b1d480) at /var/tmp/portage/kde-apps/kontactinterface-21.08.3/work/kontactinterface-21.08.3_build/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:79 #18 0x796c00e8f3a3 in KontactInterface::PimUniqueApplication::qt_metacall(QMetaObject::Call, int, void**) (this=0x7ffcd3b1df60, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7ffcd3b1d480) at /var/tmp/portage/kde-apps/kontactinterface-21.08.3/work/kontactinterface-21.08.3_build/src/KF5KontactInterface_autogen/EWIEGA46WW/moc_pimuniqueapplication.cpp:124 #19
[kdepim] [Bug 371656] HTML mail styles spill into message header: security risk
https://bugs.kde.org/show_bug.cgi?id=371656 --- Comment #13 from Erik Quaeghebeur --- 1. I have looked at two webmail clients (Fastmail and Web Outlook) to see how they deal with this issue. They essentially seem to include a div with the HTML email that includes the style element for that email. While this is against the html spec (style may only be introduced in the head element), it seems to work decently. 2. After reading up on the current state of HTML, a possibly spec-compliant fix might be achieved using ‘Web Components’ <https://developer.mozilla.org/en-US/docs/Web/Web_Components>, using templates and/or slots. It seems designed mostly with dynamic pages in mind, bit may be usable even for kmail's relatively simple purpose. How exactly this could be done is not clear to me yet, TBH. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 371656] HTML mail styles spill into message header: security risk
https://bugs.kde.org/show_bug.cgi?id=371656 Erik Quaeghebeur changed: What|Removed |Added Priority|NOR |HI Version|5.16.1 |GIT (master) Severity|minor |major Summary|HTML mail styles spill into |HTML mail styles spill into |message header |message header: security ||risk --- Comment #12 from Erik Quaeghebeur --- As is clear from some bug reports marked as a duplicate of this one, this issue is a security risk. Namely, the HTML's CSS may apply changes in an adversarial way, to, e.g., make phising scams more credible and more difficult to detect by the user. I've added that this is a security risk to the header and increased the importance. I've also indicated that it is still present in the current development branch. What has not yet been mentioned, I think, is that this issue can affect display of attachments. Any ideas for fixing this are welcome. The current rendering engine is far more advanced than it was five years ago, so we may have better options now. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 371656] HTML mail styles spill into message header
https://bugs.kde.org/show_bug.cgi?id=371656 Erik Quaeghebeur changed: What|Removed |Added CC||tho...@tanghus.net --- Comment #11 from Erik Quaeghebeur --- *** Bug 429393 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 429393] HTML email "leaks" styles into headers
https://bugs.kde.org/show_bug.cgi?id=429393 Erik Quaeghebeur changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugs.kde@e3q.eu Resolution|--- |DUPLICATE --- Comment #8 from Erik Quaeghebeur --- *** This bug has been marked as a duplicate of bug 371656 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 441829] Rendering of HTML can bleed over message headers
https://bugs.kde.org/show_bug.cgi?id=441829 Erik Quaeghebeur changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugs.kde@e3q.eu Status|REPORTED|RESOLVED --- Comment #6 from Erik Quaeghebeur --- *** This bug has been marked as a duplicate of bug 371656 *** -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 371656] HTML mail styles spill into message header
https://bugs.kde.org/show_bug.cgi?id=371656 Erik Quaeghebeur changed: What|Removed |Added CC||si...@technocool.net --- Comment #10 from Erik Quaeghebeur --- *** Bug 441829 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 447743] New: Make List-Id id and phrase available separately to grantlee for header themeing
https://bugs.kde.org/show_bug.cgi?id=447743 Bug ID: 447743 Summary: Make List-Id id and phrase available separately to grantlee for header themeing Product: kdepim Version: GIT (master) Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: messageviewer Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu CC: kdepim-bugs@kde.org Target Milestone: --- AFAICT, all variables available to grantlee header theme editors are listed in https://invent.kde.org/pim/messagelib/-/blob/master/messageviewer/src/header/grantleeheaderformatter.cpp There, the List-Id header is exposed as a string containing all of the List-Id header content. However, the List-Id header is structured (https://datatracker.ietf.org/doc/html/rfc2919). Namely, it contains the actual id between angle brackets and possibly also a descriptive phrase in front. Because for presentation purposes, the phrase is more useful than the id itself, it would be useful to expose these separately. The grantlee variable header.listid could be modified to have properties/fields for each, so header.listid.phrase (e.g., for display) and header.listid.id (e.g., for in title attribute of element used to display header.listid.phrase). In case the listid variable cannot be modified this way in a backwards-compatible manner, perhaps a new variable, e.g., header.structuredlistid, can be added. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[kdepim] [Bug 447742] Make URL-containg List headers available to grantlee for header themeing
https://bugs.kde.org/show_bug.cgi?id=447742 Erik Quaeghebeur changed: What|Removed |Added Depends on|447736 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=447736 [Bug 447736] Make Resent-Date, Resent-Sender, Resent-Cc, and Resent-Bcc available to grantlee for header themeing -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[kdepim] [Bug 447736] Make Resent-Date, Resent-Sender, Resent-Cc, and Resent-Bcc available to grantlee for header themeing
https://bugs.kde.org/show_bug.cgi?id=447736 Erik Quaeghebeur changed: What|Removed |Added Blocks|447742 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=447742 [Bug 447742] Make URL-containg List headers available to grantlee for header themeing -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 447742] New: Make URL-containg List headers available to grantlee for header themeing
https://bugs.kde.org/show_bug.cgi?id=447742
Bug ID: 447742
Summary: Make URL-containg List headers available to grantlee
for header themeing
Product: kdepim
Version: GIT (master)
Platform: unspecified
OS: All
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: messageviewer
Assignee: kdepim-bugs@kde.org
Reporter: bugs.kde@e3q.eu
CC: kdepim-bugs@kde.org
Depends on: 447736
Target Milestone: ---
AFAICT, all variables available to grantlee header theme editors are listed in
https://invent.kde.org/pim/messagelib/-/blob/master/messageviewer/src/header/grantleeheaderformatter.cpp
There, it seems some standard (although less common) headers are missing. Some
of these likely require some extra parsing before they can be made available.
Namely, the URL-containg List-* headers
(https://datatracker.ietf.org/doc/html/rfc2369) are not exposed to grantlee.
Would it be possible to make List-Help, List-Unsubscribe, List-Subscribe,
List-Owner, and List-Archive available to grantlee for header themeing?
As per the RFC, the information in the headers is a list of URLs (between angle
brackets <…>, other content can be ignored), possibly both http and mailto
ones. The preference is from left to right. List-Post has a special value ‘NO’
for lists that can't be posted to.
For header theme designers, it would be useful to have, e.g.,
header.listUnsubscribe be a list of items that can be iterated over using
grantlee. Each item would then contain a URL header.listUnsubscribe.k.url and
type information header.listUnsubscribe.k.protocol (http or mailto), where k is
the current list index (normal usage: {% for item in header.listUnsubscribe
%}do something with {{ item }} to create output{% endfor %}).
Referenced Bugs:
https://bugs.kde.org/show_bug.cgi?id=447736
[Bug 447736] Make Resent-Date, Resent-Sender, Resent-Cc, and Resent-Bcc
available to grantlee for header themeing
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
[kdepim] [Bug 447736] Make Resent-Date, Resent-Sender, Resent-Cc, and Resent-Bcc available to grantlee for header themeing
https://bugs.kde.org/show_bug.cgi?id=447736 Erik Quaeghebeur changed: What|Removed |Added Blocks||447742 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=447742 [Bug 447742] Make URL-containg List headers available to grantlee for header themeing -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 447736] New: Make Resent-Date, Resent-Sender, Resent-Cc, and Resent-Bcc available to grantlee for header themeing
https://bugs.kde.org/show_bug.cgi?id=447736 Bug ID: 447736 Summary: Make Resent-Date, Resent-Sender, Resent-Cc, and Resent-Bcc available to grantlee for header themeing Product: kdepim Version: GIT (master) Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: messageviewer Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- AFAICT, all variables available to grantlee header theme editors are listed in https://invent.kde.org/pim/messagelib/-/blob/master/messageviewer/src/header/grantleeheaderformatter.cpp There, it seems some standard (although less common) headers are missing. Some of these are just variations of existing headers and so variables should be easy to create. Namely, not all Resent-* headers (https://datatracker.ietf.org/doc/html/rfc5322#section-3.6.6) are exposed to grantlee. Would it be possible to make Resent-Date, Resent-Sender, Resent-Cc, and Resent-Bcc available to grantlee for header themeing? -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 371656] HTML mail styles spill into message header
https://bugs.kde.org/show_bug.cgi?id=371656 Erik Quaeghebeur changed: What|Removed |Added CC||sud...@sudhirkhanger.com --- Comment #8 from Erik Quaeghebeur --- *** Bug 340621 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 340621] HTML/CSS is not rendered properly
https://bugs.kde.org/show_bug.cgi?id=340621 Erik Quaeghebeur changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugs.kde@e3q.eu Resolution|--- |DUPLICATE --- Comment #4 from Erik Quaeghebeur --- *** This bug has been marked as a duplicate of bug 371656 *** -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 371656] HTML mail styles spill into message header
https://bugs.kde.org/show_bug.cgi?id=371656 Erik Quaeghebeur changed: What|Removed |Added CC||n...@naturalnet.de --- Comment #7 from Erik Quaeghebeur --- *** Bug 359425 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 359425] CSS from HTML mail interfers with header layout
https://bugs.kde.org/show_bug.cgi?id=359425 Erik Quaeghebeur changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||bugs.kde@e3q.eu --- Comment #7 from Erik Quaeghebeur --- *** This bug has been marked as a duplicate of bug 371656 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 447715] New: HTML/Plain text switcher bar changes width upon switch, resulting in distracting horizontal jumps of the message header
https://bugs.kde.org/show_bug.cgi?id=447715 Bug ID: 447715 Summary: HTML/Plain text switcher bar changes width upon switch, resulting in distracting horizontal jumps of the message header Product: kmail2 Version: 5.16.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- The vertical HTML/Plain text switcher bar changes width upon switch, resulting in distracting horizontal jumps of the message header. This may be language dependent, as the bar's size seems to depend on the widest letter used. This may perhaps be fixed by printing both messages on the bar, but the inactive one in a way that it is invisible, but does take up horizontal space. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 371656] HTML mail styles spill into message header
https://bugs.kde.org/show_bug.cgi?id=371656 Erik Quaeghebeur changed: What|Removed |Added Ever confirmed|0 |1 CC||bugs.kde@e3q.eu Status|REPORTED|CONFIRMED Version|5.3.1 |5.16.1 Product|kmail2 |kdepim Component|UI |messageviewer --- Comment #6 from Erik Quaeghebeur --- Still an issue in 5.18.3 (apparently this version is not available in drop down menu). This is actually an issue in messageviewer. It happens because the HTML message's header (including style) is used for the full message view, to which the header and attachment footers are added. So any HTML message style not explicitly overridden in the header theme, but different from the default KMail style can wreak havoc on the header. This cannot reasonably be fixed is the header themes. What should happen is that the HTML message is displayed in a separate box (iframe or something less intrusive) and that its header is not used for the full message view. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 447555] New: Clicking the junk mail icon cycles strangely through various junk/nonjunk states
https://bugs.kde.org/show_bug.cgi?id=447555 Bug ID: 447555 Summary: Clicking the junk mail icon cycles strangely through various junk/nonjunk states Product: kmail2 Version: 5.16.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- SUMMARY When clicking the junk mail icon cycles strangely through various junk/nonjunk states STEPS TO REPRODUCE 1. Use a message list theme like ‘smart with clickable icons’ 2. Click the junk mail icon 3. Click the junk mail icon [Repeat multiple times to cycle] OBSERVED RESULT The icon changes strangely (or not) between junk/nonjunk/neither In akonadiconsole, I can follow the flag changes associated to the clicks (>): (neither) [softened icon] > $notjunk [notjunk icon] > $notjunk,$JUNK [either icon can apparently come up] > $notjunk,$JUNK,$NOTJUNK [either icon can apparently come up] > (neither) [softened icon] (I am not sure whether this sequence is deterministic.) EXPECTED RESULT The icon changes (cycles) in some clear way SOFTWARE/OS VERSIONS KMail version: 5.08.3 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88 Qt Version: 5.15.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 291256] Wish: Select a background color for new and important messages
https://bugs.kde.org/show_bug.cgi?id=291256 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 293794] optimize change of email attributes, like "read/unread"
https://bugs.kde.org/show_bug.cgi?id=293794 Erik Quaeghebeur changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME CC||bugs.kde@e3q.eu --- Comment #1 from Erik Quaeghebeur --- There is (now) an option to set the mark-as-read needed time. If you set it to 0 seconds, it is instantaneous (for me). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 359111] Message list shows sender name instead of receiver name
https://bugs.kde.org/show_bug.cgi?id=359111 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu --- Comment #1 from Erik Quaeghebeur --- The smart theme uses a ‘sender’ field that is actually a ‘sender or receiver’ field, where the choice depends on the folder type. It is unclear to me actually how to determine the folder type. Anyway, to solve it, go to View > Message List > Theme > Configure… Then clone the smart theme; give the cloned theme a nice name; in the cloned theme definition's Appearance tab, drag the ‘Sender’ out into the list of fields above (it is actually the sender/receiver) and then drag the real ‘Sender’ in its place (right click to get the option to soften). So in some sense, this bug report is not really about a bug, but about a potentially confusing feature. You can choose to close it or leave it open, but then perhaps change the title to reflect the actual issue (confusing nature/bad discoverability). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 342756] Clicking on read/unread icon in Kmail's message list removes attachment icon/flag instead
https://bugs.kde.org/show_bug.cgi?id=342756 Erik Quaeghebeur changed: What|Removed |Added Severity|normal |major Priority|NOR |HI CC||bugs.kde@e3q.eu Version|5.5.2 |5.16.3 --- Comment #15 from Erik Quaeghebeur --- This indeed still an issue with current versions (I'm using 21.08.3/5.08.3, but this is not in the selectable list) and actually it similarly affects the important status. * (Twice?) clicking the unread/read icon removes a present attachment icon; this corresponds to removing the $ATTACHMENT flag * Marking an unread important message as read by clicking the icon removes the important status; this corresponds to removing the \FLAGGED flag I'm increasing the importance, because given that the importance status is, unlike the attachment state, purely user-assigned, this causes data loss. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 396079] Kontact leaves multiple speech-dispatcher connections open after program close
https://bugs.kde.org/show_bug.cgi?id=396079 Erik Quaeghebeur changed: What|Removed |Added CC||k...@equaeghe.nospammail.net --- Comment #1 from Erik Quaeghebeur --- I think this is a more general KDEPIM thing. I have disabled speech-dispatcher on my system, because it messes up other audio connections (videocalling apps and websites). In my logs, I see kmail, akonadiconsole, etc. all trying to open speech-dispatcher instances. This generates entries in the logs: Connection to speech-dispatcher failed at the warning level. (These should be at the notice level, because speech-dispatcher is optional no?) This part of the KDEPIM code needs some love, I think. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 394708] Kontact crashes when trying to delete ghost todo
https://bugs.kde.org/show_bug.cgi?id=394708 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 398918] Akonadi server crashes after enabling Notification Monitor
https://bugs.kde.org/show_bug.cgi?id=398918 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 Erik Quaeghebeur changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #15 from Erik Quaeghebeur --- (In reply to Erik Quaeghebeur from comment #13) > I'm hoping to get it into a later 20.08.z version. It should appear in the 20.08 branch in 20.08.2: https://invent.kde.org/pim/kdepim-runtime/-/commit/40797e87f8a772ee0bb5df301b41824b1b5007b3 I've asked the maintainers to add it to master as well, so that it'll be present in 20.12 and beyond. @kernel_panic: Do you have the opportunity to test the patch? If it solves your issue as well, we can close this bug. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 --- Comment #14 from Erik Quaeghebeur --- (In reply to Erik Quaeghebeur from comment #13) > For (current stable) Gentoo users: place it beneath > /etc/portage/kde-apps/kdepim-runtime-20.04.3/ and re-emerge kdepim-runtime. Typo alert. It should be /etc/portage/patches/kde-apps/kdepim-runtime-20.04.3/ Note the ‘patches’. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 --- Comment #13 from Erik Quaeghebeur --- Created attachment 131589 --> https://bugs.kde.org/attachment.cgi?id=131589=edit patch that makes sure internal date is used in changeitem-task This patch fixed my issue (limited testing, however). For (current stable) Gentoo users: place it beneath /etc/portage/kde-apps/kdepim-runtime-20.04.3/ and re-emerge kdepim-runtime. Restart akonadi and check whether or not this solves your issue. (It should apply as well to earlier versions and current 20.08.z versions. I'm hoping to get it into a later 20.08.z version.) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404533] akonadi crashes during startup after non-clean closing of previous X session
https://bugs.kde.org/show_bug.cgi?id=404533 Erik Quaeghebeur changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Erik Quaeghebeur --- (In reply to Ahmad Samir from comment #1) > Is this still an issue? No. I haven't had such a crash recently. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 Erik Quaeghebeur changed: What|Removed |Added Component|commands and actions|IMAP resource Product|kmail2 |Akonadi --- Comment #11 from Erik Quaeghebeur --- (In reply to kernel_panic from comment #9) > […] We should probably > update this to "kdepim" or "kdepimlibs". I suspect the latter would be more > appropriate, what do you think? Akonadi contains the IMAP resource, so that. We may need to go back to kmail2 in case it is kmail that determines the value of msg->date()->datetime(). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 --- Comment #10 from Erik Quaeghebeur --- (In reply to kernel_panic from comment #8) > For example, GMail uses the timestamp provided in the APPEND command to > store, index, and display messages in its web interface. This timestamp may > be different to the one provided in the message header. However, it appears > that this timestamp is stored separately (presumably in some indexing > database) since the original message's Date header is left intact and > showing the correct timestamp. […] I think there is a misunderstanding. The INTERNAl DATE is *not* the same as the Date header value and it should not be according to the RFC. (Usually, it will be close, but can differ significantly[*] if message delivery is delayed.) Please read https://tools.ietf.org/html/rfc3501#section-2.3.3 for a description. GMail does follow the RFC here AFAICT and uses the ‘REFS’ threading option. (As does, e.g., Fastmail.) [*] So that order of mails in a thread differs based on INTERNAL DATE or Date header. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 --- Comment #7 from Erik Quaeghebeur --- (In reply to Erik Quaeghebeur from comment #6) > I think the line where the INTERNAL DATE is set is […] I shouldn't be so quick to point to this instance only. Similar (for when ‘replacing’ a message): https://invent.kde.org/pim/kdepim-runtime/-/blob/master/resources/imap/replacemessagejob.cpp#L36 Non-similar as setInternalDate is *not* called here (for when ‘changing an item’): https://invent.kde.org/pim/kdepim-runtime/-/blob/master/resources/imap/changeitemtask.cpp#L53 In this last case, the INTERNAL DATE is probably set by the server to the current date. It may be that this is where my issue originates. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 --- Comment #6 from Erik Quaeghebeur --- I think the line where the INTERNAL DATE is set is https://invent.kde.org/pim/kdepim-runtime/-/blob/master/resources/imap/additemtask.cpp#L56 In case you agree, we should modify the product/component of this bug. So next, to find out what determines msg->date()->dateTime(). My guess is it is Akonadi's PimItemTable.datetime, which is the last modified date, which is (in general) not the internal date of the message on the (originating) server. That would be against the RFC and therefore a clear bug. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 Erik Quaeghebeur changed: What|Removed |Added Version|5.12.3 |5.14.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 --- Comment #5 from Erik Quaeghebeur --- (In reply to kernel_panic from comment #4) > […], this doesn't explain why single part plaintext emails are not affected > - at least not in the scenarios I provided. […] TBH, I cannot reproduce your issue. When I move messages between IMAP accounts on different servers, they keep their INTERNAL DATE. I've tried with related(plain,image) and alternative(plain,related(html,image,image,image)) messages. So I'm afraid we may be hitting different bugs both related to INTERNALDATE handling. The fact that copying between different servers works (in some cases) actually makes me hopeful, as that means that it is possible without having to add a database column to Akonadi. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 417206] KMail wrong date in IMAP APPEND command
https://bugs.kde.org/show_bug.cgi?id=417206 --- Comment #3 from Erik Quaeghebeur --- (In reply to kernel_panic from comment #2) > […] I was beginning to lose hope that this > would ever be picked up […] I think that if we want this to be picked up, it would help if we can at least point out in the code where the issue lies. This is filed in the product kmail2, but it could be an akonadi or kimap issue. I think kimap can be excluded, because it clearly provides functionality for setting the INTERNAL DATE: https://invent.kde.org/pim/kimap/-/blob/release/20.04/src/appendjob.cpp (This was also apparent from your initial report.) AFAICT from the Akonadi database structure, it only has a concept of * last access time * datetime, which seems to correspond to last *modification* time (I do not know which modifications count: flags, tags, …?). For sure changing the message's MIME structure counts, for the issue I encounter. So if I'm correct it has no concept that maps to INTERNAL DATE. That means that upon append to an IMAP store from an IMAP store, the code that appends must explicitly include a call to the original IMAP store to get the INTERNAL DATE and use it upon append. Further investigation is necessary. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 421432] Kmail crashed on start after seeming stuck on syncing my mailbox
https://bugs.kde.org/show_bug.cgi?id=421432 Erik Quaeghebeur changed: What|Removed |Added CC||k...@equaeghe.nospammail.net -- You are receiving this mail because: You are the assignee for the bug.
