Bug 489956

Summary:	Crashes when marking a folder as read after marking a large number of folders as read - crashing presists afterwards
Product:	[Applications] kmail2	Reporter:	arran <arran4>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	kdedev
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description arran 2024-07-09 03:01:48 UTC

Application: kmail (5.24.5 (23.08.5))
 (Compiled from sources)
Qt Version: 5.15.14
Frameworks Version: 5.116.0
Operating System: Linux 6.6.30-gentoo-x86_64 x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
Moving around a lot of mail I have encountered a large number of bugs, especially between imap servers. In this case I had moved the failing to sync mail locally and was marking it all as read, there are a lot of folders, I was systematically marking them as read. There is a propagation delay, if you mark the same folder as read before it completes, especially if there are 1,000+ messages in it, kmail will crash. 

It will get into a state where it will crash every time you mark it as read even just after opening it. I haven't tried logging out / logging in again but I suspect based on the other errors that will "resolve" it.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  0x00007feec5b583ed in Akonadi::ItemModifyJobPrivate::fullCommand() const () at /usr/lib64/libKPim5AkonadiCore.so.5
#5  0x00007feec5b59663 in Akonadi::ItemModifyJob::doStart() () at /usr/lib64/libKPim5AkonadiCore.so.5
#6  0x00007feec5b6063c in ??? () at /usr/lib64/libKPim5AkonadiCore.so.5
#7  0x00007feec7ca7278 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#8  0x00007feec8702da2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#9  0x00007feec7c7c0e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#10 0x00007feec7c7f584 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#11 0x00007feec7cce407 in ??? () at /usr/lib64/libQt5Core.so.5
#12 0x00007feec39e2824 in ??? () at /usr/lib64/libglib-2.0.so.0
#13 0x00007feec39e5977 in ??? () at /usr/lib64/libglib-2.0.so.0
#14 0x00007feec39e5fa0 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#15 0x00007feec7ccdefa in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#16 0x00007feec7c7aadb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#17 0x00007feec7c82d91 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#18 0x000056419c91d084 in ??? ()
#19 0x00007feec7445390 in ??? () at /usr/lib64/libc.so.6
#20 0x00007feec7445449 in __libc_start_main () at /usr/lib64/libc.so.6
#21 0x000056419c91d745 in ??? ()
[Inferior 1 (process 18283) detached]

Reported using DrKonqi

Comment 1 TraceyC 2024-07-15 16:27:24 UTC

Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong:

#6  0x00007feec5b6063c in ??? () at /usr/lib64/libKPim5AkonadiCore.so.5
#11 0x00007feec7cce407 in ??? () at /usr/lib64/libQt5Core.so.5

Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See [https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl](https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl) for details about how to do this. Thanks again!

Comment 2 Bug Janitor Service 2024-07-30 03:46:10 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Bug Janitor Service 2024-08-14 03:46:58 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.