Bug 396720 - Kmail crashes after startup
Summary: Kmail crashes after startup
Status: RESOLVED DUPLICATE of bug 396694
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 5.8.2
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-07-21 11:15 UTC by MarkusM
Modified: 2018-07-21 12:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (1.95 KB, text/plain)
2018-07-21 11:50 UTC, Bojan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description MarkusM 2018-07-21 11:15:52 UTC
Application: kmail (5.8.2)

Qt Version: 5.11.1
Frameworks Version: 5.48.0
Operating System: Linux 4.15.0-29-generic x86_64
Distribution: KDE neon User Edition 5.13

-- Information about the crash:
- What I was doing when the application crashed:

I've started Kmail after an system reboot. Before the reboot I've installed system updates.

After the update Kmail have shown some strange behaviour. If I tried to open an mail
it took a couple of seconds to show the window and if I hit reply, it took up to a minute until
the reply window came up. Not sure if this is related but it's why I did the restart at this point.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcbf80bc980 (LWP 2361))]

Thread 2 (Thread 0x7fcbc1f73700 (LWP 2363)):
#0  0x00007fcbf51cf27d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007fcbe8fc86f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fcbe8f84e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fcbe8f85330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fcbe8f8549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fcbf5aeb0bb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fcbf5a925ba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fcbf58c75e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fcbf4128f35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x00007fcbf58d2727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fcbeaa896ba in start_thread (arg=0x7fcbc1f73700) at pthread_create.c:333
#11 0x00007fcbf51df41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fcbf80bc980 (LWP 2361)):
[KCrash Handler]
#6  0x0000000000000001 in ?? ()
#7  0x00007fcbf7dccd3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135
#8  0x00000000004035fc in main (argc=1, argv=0x7ffd3f4ffec8) at /workspace/build/src/main.cpp:128

The reporter indicates this bug may be a duplicate of or related to bug 396694.

Possible duplicates by query: bug 396686.

Reported using DrKonqi
Comment 1 Bojan 2018-07-21 11:50:25 UTC
Created attachment 114045 [details]
New crash information added by DrKonqi

kmail (5.8.2) using Qt 5.11.1

- What I was doing when the application crashed:
Just started it by clicking on its icon in a start meny...

-- Backtrace (Reduced):
#7  0x00007f872d481d3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135
#8  0x00000000004035fc in main (argc=1, argv=0x7ffdb1af9ae8) at /workspace/build/src/main.cpp:128
Comment 2 Christoph Feck 2018-07-21 12:27:09 UTC

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