Bug 295636 - KMail2 composer crashes when I try to type in Subject field
Summary: KMail2 composer crashes when I try to type in Subject field
Status: RESOLVED DUPLICATE of bug 295759
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-09 20:51 UTC by S.Trzmiel
Modified: 2012-03-13 15:17 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 S.Trzmiel 2012-03-09 20:51:26 UTC
User-Agent:       Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.34 (KHTML, like Gecko) rekonq Safari/534.34
Build Identifier: 

Kontact/Kmail composer crashes when I try fill Subject field.
I started after update to KDE SC 4.8.1

=============================================
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb77509c0 (LWP 13347))]

Thread 3 (Thread 0xb5455b40 (LWP 13348)):
#0  0xb7799424 in __kernel_vsyscall ()
#1  0x4a90985c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:172
#2  0x434f49a3 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x43c19fe0) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495
#3  0x434f4ac0 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x43c19fe0) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618
#4  0x4a905cd3 in start_thread (arg=0xb5455b40) at pthread_create.c:309
#5  0x4a80ea2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 2 (Thread 0xb4b2cb40 (LWP 13349)):
#0  0x4a93f001 in __GI_clock_gettime (clock_id=1, tp=0xb4b2bfb8) at ../sysdeps/unix/clock_gettime.c:116
#1  0x4a12ae06 in do_gettime (frac=0xb4b2bfb0, sec=0xb4b2bfa8) at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0x4a214bf7 in QTimerInfoList::updateCurrentTime (this=0xb4201abc) at kernel/qeventdispatcher_unix.cpp:343
#4  0x4a214f5b in QTimerInfoList::timerWait (this=0xb4201abc, tm=...) at kernel/qeventdispatcher_unix.cpp:450
#5  0x4a2137a3 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb4b2c09c) at kernel/qeventdispatcher_glib.cpp:136
#6  0x4aab3c4c in g_main_context_prepare (context=0xb42004e0, priority=0xb4b2c0f8) at gmain.c:2762
#7  0x4aab4a08 in g_main_context_iterate (context=0xb42004e0, block=1, dispatch=1, self=0xb4200d70) at gmain.c:3069
#8  0x4aab501f in g_main_context_iteration (context=0xb42004e0, may_block=1) at gmain.c:3152
#9  0x4a214317 in QEventDispatcherGlib::processEvents (this=0xb4200468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#10 0x4a1e04ee in QEventLoop::processEvents (this=0xb4b2c230, flags=...) at kernel/qeventloop.cpp:149
#11 0x4a1e0799 in QEventLoop::exec (this=0xb4b2c230, flags=...) at kernel/qeventloop.cpp:204
#12 0x4a0c8b2c in QThread::exec (this=0x9b04348) at thread/qthread.cpp:501
#13 0x4a0c8c1c in QThread::run (this=0x9b04348) at thread/qthread.cpp:568
#14 0x4a0cc0b1 in QThreadPrivate::start (arg=0x9b04348) at thread/qthread_unix.cpp:298
#15 0x4a905cd3 in start_thread (arg=0xb4b2cb40) at pthread_create.c:309
#16 0x4a80ea2e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 1 (Thread 0xb77509c0 (LWP 13347)):
[KCrash Handler]
#7  0x4c9ac4c2 in eventFilter (e=0xbf8172f4, o=0xa101378, this=0xae8b268) at /usr/src/debug/kdelibs-4.8.1/kdeui/sonnet/highlighter.cpp:355
#8  Sonnet::Highlighter::eventFilter (this=0xae8b268, o=0xa101378, e=0xbf8172f4) at /usr/src/debug/kdelibs-4.8.1/kdeui/sonnet/highlighter.cpp:337
#9  0x4a1e17a6 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x9afd198, receiver=0xa101378, event=0xbf8172f4) at kernel/qcoreapplication.cpp:986
#10 0x4bda0103 in notify_helper (e=0xbf8172f4, receiver=0xa101378, this=0x9afd198) at kernel/qapplication.cpp:4546
#11 QApplicationPrivate::notify_helper (this=0x9afd198, receiver=0xa101378, e=0xbf8172f4) at kernel/qapplication.cpp:4522
#12 0x4bda6115 in QApplication::notify (this=0xbf817194, receiver=0xa101378, e=0xbf8172f4) at kernel/qapplication.cpp:3991
#13 0x4c9430d2 in KApplication::notify (this=0xbf817cc4, receiver=0xa101378, event=0xbf8172f4) at /usr/src/debug/kdelibs-4.8.1/kdeui/kernel/kapplication.cpp:311
#14 0x4a1e15fe in QCoreApplication::notifyInternal (this=0xbf817cc4, receiver=0xa101378, event=0xbf8172f4) at kernel/qcoreapplication.cpp:876
#15 0x4bd9e1ae in sendSpontaneousEvent (event=0xbf8172f4, receiver=0xa101378) at ../../src/corelib/kernel/qcoreapplication.h:234
#16 qt_sendSpontaneousEvent (receiver=0xa101378, event=0xbf8172f4) at kernel/qapplication.cpp:5544
#17 0x4be50522 in QKeyMapper::sendKeyEvent (keyWidget=0xa101378, grab=false, type=QEvent::KeyPress, code=16777248, modifiers=..., text=..., autorepeat=false, count=-1082035468, nativeScanCode=168825720, nativeVirtualKey=168825720, nativeModifiers=168825720) at kernel/qkeymapper_x11.cpp:1866
#18 0x4be509db in QKeyMapperPrivate::translateKeyEvent (this=0x9b2c4c0, keyWidget=0xa101378, event=0xbf81791c, grab=false) at kernel/qkeymapper_x11.cpp:1836
#19 0x4be2961d in QApplication::x11ProcessEvent (this=0xbf817cc4, event=0xbf81791c) at kernel/qapplication_x11.cpp:3534
#20 0x4be54e05 in x11EventSourceDispatch (s=0x9af9e00, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#21 0x4aab462f in g_main_dispatch (context=0x9af8a80) at gmain.c:2441
#22 g_main_context_dispatch (context=0x9af8a80) at gmain.c:3011
#23 0x4aab4d70 in g_main_context_iterate (context=0x9af8a80, block=1252800528, dispatch=1, self=0x9afd2e8) at gmain.c:3089
#24 0x4aab501f in g_main_context_iteration (context=0x9af8a80, may_block=1) at gmain.c:3152
#25 0x4a2142b8 in QEventDispatcherGlib::processEvents (this=0x9acba30, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#26 0x4be54a9b in QGuiEventDispatcherGlib::processEvents (this=0x9acba30, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#27 0x4a1e04ee in QEventLoop::processEvents (this=0xbf817c24, flags=...) at kernel/qeventloop.cpp:149
#28 0x4a1e0799 in QEventLoop::exec (this=0xbf817c24, flags=...) at kernel/qeventloop.cpp:204
#29 0x4a1e593b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#30 0x4bd9df35 in QApplication::exec () at kernel/qapplication.cpp:3811
#31 0x0804ad73 in ?? ()
#32 0x4a7346b3 in __libc_start_main (main=0x804a280, argc=1, ubp_av=0xbf817ee4, init=0x804bb80 <__libc_csu_init>, fini=0x804bbf0 <__libc_csu_fini>, rtld_fini=0x4a7062c0 <_dl_fini>, stack_end=0xbf817edc) at libc-start.c:226
#33 0x0804b2a5 in _start ()
===========================
Installed packages:

kdepimlibs-4.8.1-1.fc16.i686
kdepim-4.8.1-2.fc16.i686
kdepim-libs-4.8.1-2.fc16.i686
kdepim-runtime-4.8.1-1.fc16.i686
kde-workspace-4.8.1-2.fc16.i686
qt-4.8.0-7.fc16.i686
kernel-PAE-3.2.9-2.fc16.i686




Reproducible: Always

Steps to Reproduce:
1. Create new mail
2. Click on subject/topic field and start typing or paste something

Actual Results:  
Whole Kmail/Kontact crashes

Expected Results:  
No crash, subject field can be filled by typing/pasting etc ....
Comment 1 S.Trzmiel 2012-03-13 15:17:33 UTC
Most likely update messed with identity settings - simple resaving of spellcheck/dictionary settings (as per solution in bug https://bugs.kde.org/show_bug.cgi?id=295759) solved issue.

Was there any change to the dictionaries? (naming theme opr something)?

Bug related to https://bugs.kde.org/show_bug.cgi?id=295759
Closing this one as dupe

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