Bug 299466 - Kmail crash after sent mail.
Summary: Kmail crash after sent mail.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-05 20:10 UTC by Henrik
Modified: 2017-01-07 21:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henrik 2012-05-05 20:10:26 UTC
Application: kmail (4.8.2)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-23-generic x86_64
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
Send a mail from Kmail and when i want to return to the main screen in Kmail it crash and the main screen is empty. Newly installed kubuntu 12.04. Using IMAP.

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

Thread 4 (Thread 0x7f34dac98700 (LWP 6254)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f34f3fdadec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f34f3fdaf19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f34fcb0ce9a in start_thread (arg=0x7f34dac98700) at pthread_create.c:308
#4  0x00007f34ff03d4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f34da497700 (LWP 6255)):
#0  0x00007f34f78e689b in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f34f78e6f6a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f34f78e7124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f34ff9c8426 in QEventDispatcherGlib::processEvents (this=0x7f34d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f34ff997c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f34ff997ed7 in QEventLoop::exec (this=0x7f34da496dc0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f34ff896fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f34ff899fcb in QThreadPrivate::start (arg=0x157f290) at thread/qthread_unix.cpp:298
#8  0x00007f34fcb0ce9a in start_thread (arg=0x7f34da497700) at pthread_create.c:308
#9  0x00007f34ff03d4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f3492292700 (LWP 6314)):
#0  0x00007f34ff031b03 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f34f78e6ff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f34f78e7124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f34ff9c8426 in QEventDispatcherGlib::processEvents (this=0x7f34880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f34ff997c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f34ff997ed7 in QEventLoop::exec (this=0x7f3492291d90, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f34ff896fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f34ff9779ff in QInotifyFileSystemWatcherEngine::run (this=0x1ac54b0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f34ff899fcb in QThreadPrivate::start (arg=0x1ac54b0) at thread/qthread_unix.cpp:298
#9  0x00007f34fcb0ce9a in start_thread (arg=0x7f3492292700) at pthread_create.c:308
#10 0x00007f34ff03d4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f3501cf17c0 (LWP 6217)):
[KCrash Handler]
#6  0x00007f34fef81445 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f34fef84bab in __GI_abort () at abort.c:91
#8  0x00007f34ff88f50b in qt_message_output (msgType=<optimized out>, buf=0x298cf68 "kmail2(6217): Attempted to remove the last identity! ") at global/qglobal.cpp:2276
#9  0x00007f3500b3930b in ~QDebug (this=0x7fff1d8ff180, __in_chrg=<optimized out>) at /usr/include/qt4/QtCore/qdebug.h:85
#10 KMail::IdentityPage::slotRemoveIdentity (this=0x217f310) at ../../kmail/identitypage.cpp:217
#11 0x00007f34ff9ad281 in QMetaObject::activate (sender=0x217e0e0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff1d8ff450) at kernel/qobject.cpp:3547
#12 0x00007f350054bc72 in QAbstractButton::clicked (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:220
#13 0x00007f3500289a4e in QAbstractButtonPrivate::emitClicked (this=<optimized out>) at widgets/qabstractbutton.cpp:548
#14 0x00007f350028ad8b in QAbstractButtonPrivate::click (this=0x218a0b0) at widgets/qabstractbutton.cpp:541
#15 0x00007f350028affc in QAbstractButton::mouseReleaseEvent (this=0x217e0e0, e=0x7fff1d8ffd20) at widgets/qabstractbutton.cpp:1123
#16 0x00007f34fff0c144 in QWidget::event (this=0x217e0e0, event=0x7fff1d8ffd20) at kernel/qwidget.cpp:8362
#17 0x00007f34ffebb894 in notify_helper (e=0x7fff1d8ffd20, receiver=0x217e0e0, this=0x108e3f0) at kernel/qapplication.cpp:4559
#18 QApplicationPrivate::notify_helper (this=0x108e3f0, receiver=0x217e0e0, e=0x7fff1d8ffd20) at kernel/qapplication.cpp:4531
#19 0x00007f34ffec10bf in QApplication::notify (this=<optimized out>, receiver=0x217e0e0, e=0x7fff1d8ffd20) at kernel/qapplication.cpp:4102
#20 0x00007f35016f4b46 in KApplication::notify (this=0x7fff1d900ab0, receiver=0x217e0e0, event=0x7fff1d8ffd20) at ../../kdeui/kernel/kapplication.cpp:311
#21 0x00007f34ff998e9c in QCoreApplication::notifyInternal (this=0x7fff1d900ab0, receiver=0x217e0e0, event=0x7fff1d8ffd20) at kernel/qcoreapplication.cpp:876
#22 0x00007f34ffebc862 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#23 QApplicationPrivate::sendMouseEvent (receiver=0x217e0e0, event=0x7fff1d8ffd20, alienWidget=0x217e0e0, nativeWidget=0x1ac4d30, buttonDown=0x217e0e0, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3170
#24 0x00007f34fff3bbf5 in QETWidget::translateMouseEvent (this=0x1ac4d30, event=<optimized out>) at kernel/qapplication_x11.cpp:4617
#25 0x00007f34fff3abae in QApplication::x11ProcessEvent (this=0x7fff1d900ab0, event=0x7fff1d9005f0) at kernel/qapplication_x11.cpp:3732
#26 0x00007f34fff640d2 in x11EventSourceDispatch (s=0x1090560, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#27 0x00007f34f78e6c9a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f34f78e7060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007f34f78e7124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007f34ff9c83bf in QEventDispatcherGlib::processEvents (this=0x1040b00, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#31 0x00007f34fff63d5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#32 0x00007f34ff997c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#33 0x00007f34ff997ed7 in QEventLoop::exec (this=0x7fff1d900990, flags=...) at kernel/qeventloop.cpp:204
#34 0x00007f34ff99cf67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#35 0x0000000000402bd3 in main (argc=<optimized out>, argv=<optimized out>) at ../../kmail/main.cpp:145

Possible duplicates by query: bug 283935, bug 270442, bug 264758, bug 255169, bug 253675.

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 18:03:31 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:26:13 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.