Bug 369856

Summary:	kmail crash on start [Thread 3 "QDBusConnection" received signal SIGSEGV]
Product:	[Applications] kmail2	Reporter:	PC LX <kde>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash
Priority:	NOR
Version:	5.3.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description PC LX 2016-10-04 10:49:15 UTC

kmail crash on start.

I have just updated my system from "Mageia 5" to "Mageia 6" and kmail from "4.14.5" to "kmail2 5.3.0 (QtWebEngine)".

This is the backtrace produced by gdb:

Thread 3 "QDBusConnection" received signal SIGSEGV, Segmentation fault.
(gdb) bt
#0  0x00007ffff5e369d7 in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () at /lib64/libQt5Core.so.5
#1  0x00007ffff7f664d0 in QDBusConnectionPrivate::closeConnection() () at /lib64/libQt5DBus.so.5
#2  0x00007ffff7f546f6 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5
#3  0x00007ffff5c43fb9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#4  0x00007fffebd9e66d in start_thread () at /lib64/libpthread.so.0
#5  0x00007ffff5346ded in clone () at /lib64/libc.so.6


Reproducible: Always

Steps to Reproduce:
1. Run kmail

Actual Results:  
kmail crashed on start.

Expected Results:  
kmail starts normally.

The only way I found to work around this crash was to delete all kmail and akonady (data and config) files and reconfigure all again.

Comment 1 Andrew Crouthamel 2018-11-01 13:40:22 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

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

Comment 2 PC LX 2018-11-08 12:44:21 UTC

This bug happened when after upgrading kmail. Currently, I'm using kmail version 5.7.2 and this bug does not occur. Can't retest it since I no longer have the old version installed.

Since no one else complained (at least from what I can see here), it should be OK to close this bug.

Comment 3 Christophe Marin 2018-11-08 12:47:53 UTC

Thanks for the feedback.