https://bugs.kde.org/show_bug.cgi?id=357030
Bug ID: 357030
Summary: Close button crashes kmail
Product: kmail2
Version: unspecified
Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: arsiv...@gmail.com
Application: kmail (5.1)
Qt Version: 5.5.1
Operating System: Linux 4.1.15 x86_64
Distribution (Platform): Slackware Packages
-- Information about the crash:
- What I was doing when the application crashed:
I simply click the close button. Kmail crashed with "Executable: kmail PID:
3008 Signal: Segmentation fault (11) Time: 12/22/15 09:43:04"
The crash can be reproduced every time.
-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcedb48e800 (LWP 3008))]
Thread 4 (Thread 0x7fceb4cb3700 (LWP 3010)):
#0 0x00007fced402f03d in read () at /lib64/libc.so.6
#1 0x00007fcec87905d0 in () at /usr/lib64/libglib-2.0.so.0
#2 0x00007fcec874e484 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3 0x00007fcec874e8f8 in () at /usr/lib64/libglib-2.0.so.0
#4 0x00007fcec874ea5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5 0x00007fced4e59c9b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#6 0x00007fced4e03fda in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#7 0x00007fced4c3116c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8 0x00007fced4c35f6f in () at /usr/lib64/libQt5Core.so.5
#9 0x00007fced0d0d704 in start_thread () at /lib64/libpthread.so.0
#10 0x00007fced403ef8d in clone () at /lib64/libc.so.6
Thread 3 (Thread 0x7fce8f7c6700 (LWP 3028)):
#0 0x00007fcec87917e9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1 0x00007fcec874df89 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2 0x00007fcec874e883 in () at /usr/lib64/libglib-2.0.so.0
#3 0x00007fcec874ea5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4 0x00007fced4e59c9b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#5 0x00007fced4e03fda in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#6 0x00007fced4c3116c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7 0x00007fced4c35f6f in () at /usr/lib64/libQt5Core.so.5
#8 0x00007fced0d0d704 in start_thread () at /lib64/libpthread.so.0
#9 0x00007fced403ef8d in clone () at /lib64/libc.so.6
Thread 2 (Thread 0x7fce8ebc1700 (LWP 3033)):
#0 0x00007fcec874bb37 in () at /usr/lib64/libglib-2.0.so.0
#1 0x00007fcec874df1b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2 0x00007fcec874e883 in () at /usr/lib64/libglib-2.0.so.0
#3 0x00007fcec874ea5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4 0x00007fced4e59c9b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#5 0x00007fced4e03fda in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#6 0x00007fced4c3116c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7 0x00007fced4c35f6f in () at /usr/lib64/libQt5Core.so.5
#8 0x00007fced0d0d704 in start_thread () at /lib64/libpthread.so.0
#9 0x00007fced403ef8d in clone () at /lib64/libc.so.6
Thread 1 (Thread 0x7fcedb48e800 (LWP 3008)):
[KCrash Handler]
#6 0x0000000000000018 in ()
#7 0x00007fced9a3d42c in () at /usr/lib64/libKF5AkonadiCore.so.5
#8 0x00007fced4e330a7 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#9 0x00007fced4e0bbcb in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#10 0x00000000004044a8 in main ()
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
