Bug 402273

Summary: Kmail: Wayland session: core dumped when I try to open any mail
Product: [Applications] kmail2 Reporter: foss
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Kmail about Dialog
Kmail log file

Description foss 2018-12-18 02:00:32 UTC
Created attachment 116978 [details]
Kmail about Dialog

SUMMARY
Kmail core dumped repeatedly as soon as I open any mail. This happens while using wayland session, but only in the last 3-5 days, I think after the 18.12 update.

STEPS TO REPRODUCE
1. Start a wayland session
2. Set kmail to use classic theme for mail list; it means that mail content shows after the mail is opened. (mails are shown in a list sorted new to old)
3. Start kmail and try to open any mail...

OBSERVED RESULT
Kmail crashes as soon as I double click any mail

EXPECTED RESULT
Mail is shown

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.14.4-2
KDE Frameworks Version: 5.53.0
Qt Version: 5.12.0
Kmail version (about dialog): 5.10
Kmail version (package manager): 18.12.0
ADDITIONAL INFORMATION
Comment 1 foss 2018-12-18 02:02:20 UTC
Created attachment 116979 [details]
Kmail log file
Comment 2 Christoph Feck 2018-12-18 02:27:04 UTC
This could be bug 401419, but we need the backtrace of the crash to make sure. Please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 3 foss 2018-12-18 07:50:45 UTC
(In reply to Christoph Feck from comment #2)
> This could be bug 401419, but we need the backtrace of the crash to make
> sure. Please see
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports

Am pretty sure it is the "same" issue. 
As per https://bugs.kde.org/show_bug.cgi?id=401419#c3 : If enable preview Kmail doesn't crash.   
Somehow I missed that bug report, it didn't show up...
Closing as duplicate.

*** This bug has been marked as a duplicate of bug 401419 ***