Bug 192067 - Kontact crashes on opening search folder from search settings dialog
Summary: Kontact crashes on opening search folder from search settings dialog
Status: RESOLVED NOT A BUG
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 1.4.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-08 20:31 UTC by Sergey Alpaev
Modified: 2009-10-23 10:40 UTC (History)
1 user (show)

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 Sergey Alpaev 2009-05-08 20:31:40 UTC
Version:           1.4.2 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

Open Kontact, 
select Searches in the folder tree
Open Edit/Search dialog
Clear edit box "Folder for results" at the bottom of the dialog, by clicking on Clear button next to the edit box
Press Open Search Folder. 

See Crash trace below


Приложение: Kontact (kontact), сигнал SIGABRT
[Current thread is 0 (LWP 4624)]

Thread 2 (Thread 0xac466b90 (LWP 4627)):
#0  0xb7fbd430 in __kernel_vsyscall ()
#1  0xb5118412 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb5932344 in pthread_cond_timedwait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb5b1e98c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb5b13e76 in ?? () from /usr/lib/libQtCore.so.4
#5  0xb5b1d96e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb51144ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb592349e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb482e700 (LWP 4624)):
[KCrash Handler]
#6  0xb7fbd430 in __kernel_vsyscall ()
#7  0xb586a6d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb586c098 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb5b15595 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb5b15681 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb5b15775 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb1005488 in ?? () from /usr/lib/libkmailprivate.so.4
#13 0xb1008fdd in ?? () from /usr/lib/libkmailprivate.so.4
#14 0xb5c27ca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb5c280e0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb67996a1 in QAbstractButton::clicked () from /usr/lib/libQtGui.so.4
#17 0xb64c44a9 in ?? () from /usr/lib/libQtGui.so.4
#18 0xb64c6104 in ?? () from /usr/lib/libQtGui.so.4
#19 0xb64c6396 in QAbstractButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
#20 0xb6139bd3 in QWidget::event () from /usr/lib/libQtGui.so.4
#21 0xb64c434e in QAbstractButton::event () from /usr/lib/libQtGui.so.4
#22 0xb656f310 in QPushButton::event () from /usr/lib/libQtGui.so.4
#23 0xb60e2f2c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#24 0xb60ebba1 in QApplication::notify () from /usr/lib/libQtGui.so.4
#25 0xb6d0794d in KApplication::notify () from /usr/lib/libkdeui.so.5
#26 0xb5c11a3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#27 0xb60eac0e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#28 0xb615aa0e in ?? () from /usr/lib/libQtGui.so.4
#29 0xb6159d37 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#30 0xb6184cfa in ?? () from /usr/lib/libQtGui.so.4
#31 0xb4ce4b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0xb4ce80eb in ?? () from /usr/lib/libglib-2.0.so.0
#33 0xb4ce8268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0xb5c3d438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#35 0xb61843f5 in ?? () from /usr/lib/libQtGui.so.4
#36 0xb5c1006a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#37 0xb5c104aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#38 0xb5c12959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#39 0xb60e2da7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#40 0x0804c072 in _start ()
Comment 1 Dario Andres 2009-05-08 20:39:23 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here?
You need to install the "kdepim-dbg" package
Thanks
Comment 2 Dario Andres 2009-06-12 16:28:09 UTC
Marking as NEEDSINFO
Comment 3 Christophe Marin 2009-10-23 10:40:00 UTC
Closing the old crash reports which don't have a useful backtrace. Thanks.