Bug 312798

Summary: kmail ends during set up new imap aacount.
Product: [Applications] kmail2 Reporter: Jana Domorowski <Jana.Domorowski>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: crash    
Priority: NOR    
Version: 4.8.5   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jana Domorowski 2013-01-07 08:20:30 UTC
Application: kmail (4.8.5)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-35-generic-pae i686
Distribution: Ubuntu 12.04.1 LTS

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

I set up a further imap outgoing server account. 
The incoming set up was ok. 
The automatic outgoing check was ok.
The final ok button was ok.
1 second later Kmail ends.

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

Thread 4 (Thread 0xb396db40 (LWP 4356)):
#0  0x0029a416 in __kernel_vsyscall ()
#1  0x00d5296b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x0712964c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb6fc5263 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb6fc537f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0x00d4ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0x0711bd3e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 3 (Thread 0xb3044b40 (LWP 4357)):
#0  0x00d4d483 in __i686.get_pc_thunk.bx () from /lib/i386-linux-gnu/libpthread.so.0
#1  0x00d51c39 in __pthread_mutex_unlock_usercnt () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x071298a4 in pthread_mutex_unlock () from /lib/i386-linux-gnu/libc.so.6
#3  0x04c36410 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x04bf680b in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x04bf6faf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0x04bf7201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x096c48e7 in QEventDispatcherGlib::processEvents (this=0xb2700468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#8  0x0969050d in QEventLoop::processEvents (this=0xb3044270, flags=...) at kernel/qeventloop.cpp:149
#9  0x096907a9 in QEventLoop::exec (this=0xb3044270, flags=...) at kernel/qeventloop.cpp:204
#10 0x0957994c in QThread::exec (this=0xa4238b0) at thread/qthread.cpp:501
#11 0x09579a3b in QThread::run (this=0xa4238b0) at thread/qthread.cpp:568
#12 0x0957cde0 in QThreadPrivate::start (arg=0xa4238b0) at thread/qthread_unix.cpp:298
#13 0x00d4ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#14 0x0711bd3e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xb1443b40 (LWP 4372)):
#0  0x04c36931 in g_private_get () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0x04c1ac84 in g_thread_self () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0x04bf61b7 in g_main_context_acquire () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x04bf6f58 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x04bf7201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x096c48e7 in QEventDispatcherGlib::processEvents (this=0xa41b760, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x0969050d in QEventLoop::processEvents (this=0xb1443240, flags=...) at kernel/qeventloop.cpp:149
#7  0x096907a9 in QEventLoop::exec (this=0xb1443240, flags=...) at kernel/qeventloop.cpp:204
#8  0x0957994c in QThread::exec (this=0xa7c7950) at thread/qthread.cpp:501
#9  0x0966db5d in QInotifyFileSystemWatcherEngine::run (this=0xa7c7950) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x0957cde0 in QThreadPrivate::start (arg=0xa7c7950) at thread/qthread_unix.cpp:298
#11 0x00d4ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0x0711bd3e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb5d92a00 (LWP 4352)):
[KCrash Handler]
#7  size (this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qlist.h:98
#8  size (this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qlist.h:137
#9  QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0xa026b70, receiver=0xaecb140, event=0xbf950b80) at kernel/qcoreapplication.cpp:978
#10 0x00ed2ea2 in notify_helper (e=0xbf950b80, receiver=0xaecb140, this=0xa026b70) at kernel/qapplication.cpp:4555
#11 QApplicationPrivate::notify_helper (this=0xa026b70, receiver=0xaecb140, e=0xbf950b80) at kernel/qapplication.cpp:4531
#12 0x00ed83a2 in QApplication::notify (this=0xa026b70, receiver=0xaecb140, e=0xbf950b80) at kernel/qapplication.cpp:4524
#13 0x00604e01 in KApplication::notify (this=0xbf9518dc, receiver=0xaecb140, event=0xbf950b80) at ../../kdeui/kernel/kapplication.cpp:311
#14 0x0969197e in QCoreApplication::notifyInternal (this=0xbf9518dc, receiver=0xaecb140, event=0xbf950b80) at kernel/qcoreapplication.cpp:876
#15 0x00ed140a in sendEvent (event=0xbf950b80, receiver=0xaecb140) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#16 QApplicationPrivate::setFocusWidget (focus=0xa524198, reason=Qt::MouseFocusReason) at kernel/qapplication.cpp:2260
#17 0x00f1ee1b in QWidget::setFocus (this=0xa524198, reason=Qt::MouseFocusReason) at kernel/qwidget.cpp:6450
#18 0x00ed0eb0 in QApplicationPrivate::giveFocusAccordingToFocusPolicy (widget=0xa524198, focusPolicy=Qt::ClickFocus, focusReason=Qt::MouseFocusReason) at kernel/qapplication.cpp:5593
#19 0x00eda4e4 in QApplication::notify (this=0xbf9518dc, receiver=0xa524198, e=0xbf951054) at kernel/qapplication.cpp:4059
#20 0x00604e01 in KApplication::notify (this=0xbf9518dc, receiver=0xa524198, event=0xbf951054) at ../../kdeui/kernel/kapplication.cpp:311
#21 0x0969197e in QCoreApplication::notifyInternal (this=0xbf9518dc, receiver=0xa524198, event=0xbf951054) at kernel/qcoreapplication.cpp:876
#22 0x00ed3e95 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#23 QApplicationPrivate::sendMouseEvent (receiver=0xa524198, event=0xbf951054, alienWidget=0xa524198, nativeWidget=0xa9a6528, buttonDown=0x1867cf4, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3170
#24 0x00f60074 in QETWidget::translateMouseEvent (this=0xa9a6528, event=0xbf95150c) at kernel/qapplication_x11.cpp:4617
#25 0x00f5ec0d in QApplication::x11ProcessEvent (this=0xbf9518dc, event=0xbf95150c) at kernel/qapplication_x11.cpp:3732
#26 0x00f8beac in x11EventSourceDispatch (s=0xa01cc10, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#27 0x04bf6d86 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#28 0x04bf7125 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#29 0x04bf7201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#30 0x096c4887 in QEventDispatcherGlib::processEvents (this=0x9fe4ec0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#31 0x00f8baaa in QGuiEventDispatcherGlib::processEvents (this=0x9fe4ec0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#32 0x0969050d in QEventLoop::processEvents (this=0xbf951804, flags=...) at kernel/qeventloop.cpp:149
#33 0x096907a9 in QEventLoop::exec (this=0xbf951804, flags=...) at kernel/qeventloop.cpp:204
#34 0x09695eba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#35 0x00ed0a74 in QApplication::exec () at kernel/qapplication.cpp:3820
#36 0x0804a266 in ?? ()
#37 0x070464d3 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
#38 0x0804a6e9 in _start ()

Possible duplicates by query: bug 311735, bug 310701, bug 309824, bug 308099, bug 307887.

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 17:53:02 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:40:48 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.