[Bug 251836] New: kontact seg-faulted on either start or exit

Thomas Caswell tcaswell at gmail.com
Mon Sep 20 16:53:15 BST 2010


https://bugs.kde.org/show_bug.cgi?id=251836

           Summary: kontact seg-faulted on either start or exit
           Product: kontact
           Version: 4.4.2
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: tcaswell at gmail.com


Application: kontact (4.4.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
I started kontact, then exited it almost immediatly (waited for the window to
appear and used file->exit) and restarted it (this seems to be a work around
for issues I am having with the address book not reading data properly that I
think has something to do with a race condition with the backend and is a known
problem).

About 5-10 minutes later the crash window popped up, however I was not paying
attention to kontact closely and do not know if the crash was while exiting the
first time or while starting up the second time.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f9ef1bb9780 (LWP 2230))]

Thread 2 (Thread 0x7f9ec9d35710 (LWP 2332)):
#0  0x00007f9eeec8af83 in *__GI___poll (fds=<value optimized out>, nfds=<value
optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f9ee77bf4a9 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007f9ee77bf8fc in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#3  0x00007f9ef0076566 in QEventDispatcherGlib::processEvents (this=0x1dd9440,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007f9ef004b992 in QEventLoop::processEvents (this=<value optimized
out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007f9ef004bd6c in QEventLoop::exec (this=0x7f9ec9d34d90, flags=) at
kernel/qeventloop.cpp:201
#6  0x00007f9eeff55d59 in QThread::exec (this=<value optimized out>) at
thread/qthread.cpp:487
#7  0x00007f9ef002c178 in QInotifyFileSystemWatcherEngine::run (this=0x1d4ec80)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f9eeff58775 in QThreadPrivate::start (arg=0x1d4ec80) at
thread/qthread_unix.cpp:248
#9  0x00007f9ee9d369ca in start_thread (arg=<value optimized out>) at
pthread_create.c:300
#10 0x00007f9eeec976fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f9ef1bb9780 (LWP 2230)):
[KCrash Handler]
#5  0x00007f9ed7563280 in KMFolderNode::path (this=<value optimized out>) at
../../kmail/kmfoldernode.cpp:31
#6  0x00007f9ed753cc08 in FolderStorage::location (this=0x1737750, suffix=...)
at ../../kmail/folderstorage.cpp:1234
#7  0x00007f9ed7716bb9 in KMFolderSearch::indexLocation (this=0x1737750) at
../../kmail/kmfoldersearch.cpp:741
#8  0x00007f9ed7718758 in KMFolderSearch::updateIndex (this=<value optimized
out>) at ../../kmail/kmfoldersearch.cpp:747
#9  0x00007f9ed753a677 in FolderStorage::qt_metacall (this=0x1737750,
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffb5c65330)
at ./folderstorage.moc:148
#10 0x00007f9ed771acd6 in KMFolderSearch::qt_metacall (this=0x7fffb5c65200,
_c=23683432, _id=-1245294176, _a=0x1d28a56) at ./kmfoldersearch.moc:179
#11 0x00007f9ef005fe3f in QMetaObject::activate (sender=0x168cf60, m=<value
optimized out>, local_signal_index=<value optimized out>, argv=0x1d28a56) at
kernel/qobject.cpp:3293
#12 0x00007f9ef005ca63 in QObject::event (this=0x168cf60, e=0x7fffb5c65a80) at
kernel/qobject.cpp:1212
#13 0x00007f9eef40622c in QApplicationPrivate::notify_helper (this=0x10038c0,
receiver=0x168cf60, e=0x7fffb5c65a80) at kernel/qapplication.cpp:4300
#14 0x00007f9eef40c6fb in QApplication::notify (this=0x7fffb5c65de0,
receiver=0x168cf60, e=0x7fffb5c65a80) at kernel/qapplication.cpp:4183
#15 0x00007f9ef0a35526 in KApplication::notify (this=0x7fffb5c65de0,
receiver=0x168cf60, event=0x7fffb5c65a80) at
../../kdeui/kernel/kapplication.cpp:302
#16 0x00007f9ef004d06c in QCoreApplication::notifyInternal
(this=0x7fffb5c65de0, receiver=0x168cf60, event=0x7fffb5c65a80) at
kernel/qcoreapplication.cpp:704
#17 0x00007f9ef0079d42 in QCoreApplication::sendEvent (this=0x1011d00) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#18 QTimerInfoList::activateTimers (this=0x1011d00) at
kernel/qeventdispatcher_unix.cpp:603
#19 0x00007f9ef0076848 in timerSourceDispatch (source=<value optimized out>) at
kernel/qeventdispatcher_glib.cpp:184
#20 idleTimerSourceDispatch (source=<value optimized out>) at
kernel/qeventdispatcher_glib.cpp:231
#21 0x00007f9ee77bb8c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x00007f9ee77bf748 in ?? () from /lib/libglib-2.0.so.0
#23 0x00007f9ee77bf8fc in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#24 0x00007f9ef0076513 in QEventDispatcherGlib::processEvents (this=0xfd7d70,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#25 0x00007f9eef4b646e in QGuiEventDispatcherGlib::processEvents
(this=0x7fffb5c65200, flags=<value optimized out>) at
kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007f9ef004b992 in QEventLoop::processEvents (this=<value optimized
out>, flags=) at kernel/qeventloop.cpp:149
#27 0x00007f9ef004bd6c in QEventLoop::exec (this=0x7fffb5c65d20, flags=) at
kernel/qeventloop.cpp:201
#28 0x00007f9ef004faab in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:981
#29 0x0000000000403e8e in main (argc=<value optimized out>, argv=<value
optimized out>) at ../../../kontact/src/main.cpp:224

This bug may be a duplicate of or related to bug 204341.

Possible duplicates by query: bug 237245, bug 213838, bug 204341.

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list