Bug 167889 - Kontact crashes for no obvious reason
Summary: Kontact crashes for no obvious reason
Status: RESOLVED DUPLICATE of bug 165540
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-31 20:23 UTC by hyper_ch
Modified: 2008-07-31 23:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hyper_ch 2008-07-31 20:23:36 UTC
Version:            (using KDE 4.1.0)
Installed from:    Ubuntu Packages
OS:                Linux

well, the new kontact kdepim for kde 4.1 (Kontact Version 1.3) works fine but after a while it keeps crashing - for no obvious reason.
Here's the traceback:

Application: Kontact (kontact), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb4daf720 (LWP 11375)]
[New Thread 0xb105db90 (LWP 11400)]
[KCrash handler]
#6  0xb77593a9 in QUrl (this=0xbfb74aa4, other=@0x60) at io/qurl.cpp:3769
#7  0xb797dcd9 in KUrl (this=0xbfb74aa4, _u=@0x60)
    at /build/buildd/kde4libs-4.1.0/kdecore/io/kurl.cpp:436
#8  0xb69e0dc5 in KIO::SchedulerPrivate::slotScheduleCoSlave (this=0x87b41e8)
    at /build/buildd/kde4libs-4.1.0/kio/kio/scheduler.cpp:883
#9  0xb69e3ff3 in KIO::Scheduler::qt_metacall (this=0x87cc580, 
    _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfb74b98)
    at /build/buildd/kde4libs-4.1.0/obj-i486-linux-gnu/kio/scheduler.moc:105
#10 0xb77bc4f9 in QMetaObject::activate (sender=0x87b4204, 
    from_signal_index=4, to_signal_index=4, argv=0x0)
    at kernel/qobject.cpp:3010
#11 0xb77bcbc2 in QMetaObject::activate (sender=0x87b4204, m=0xb789d004, 
    local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080
#12 0xb77f9e07 in QTimer::timeout (this=0x87b4204)
    at .moc/release-shared/moc_qtimer.cpp:126
#13 0xb77c367e in QTimer::timerEvent (this=0x87b4204, e=0xbfb75078)
    at kernel/qtimer.cpp:263
#14 0xb77b7c9a in QObject::event (this=0x87b4204, e=0xbfb75078)
    at kernel/qobject.cpp:1105
#15 0xb6e77c0c in QApplicationPrivate::notify_helper (this=0x8064600, 
    receiver=0x87b4204, e=0xbfb75078) at kernel/qapplication.cpp:3772
#16 0xb6e7c799 in QApplication::notify (this=0xbfb752e8, receiver=0x87b4204, 
    e=0xbfb75078) at kernel/qapplication.cpp:3366
#17 0xb7c37ef3 in KApplication::notify (this=0xbfb752e8, receiver=0x87b4204, 
    event=0xbfb75078)
    at /build/buildd/kde4libs-4.1.0/kdeui/kernel/kapplication.cpp:311
#18 0xb77a76a9 in QCoreApplication::notifyInternal (this=0xbfb752e8, 
    receiver=0x87b4204, event=0xbfb75078) at kernel/qcoreapplication.cpp:587
#19 0xb77d51a1 in QTimerInfoList::activateTimers (this=0x8067344)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#20 0xb77d2a40 in timerSourceDispatch (source=0x8067310)
    at kernel/qeventdispatcher_glib.cpp:166
#21 0xb5661dd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb5665193 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb566574e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb77d2f98 in QEventDispatcherGlib::processEvents (this=0x805c908, 
    flags=@0xbfb751d8) at kernel/qeventdispatcher_glib.cpp:325
#25 0xb6f0b195 in QGuiEventDispatcherGlib::processEvents (this=0x805c908, 
    flags=@0xbfb75208) at kernel/qguieventdispatcher_glib.cpp:204
#26 0xb77a692d in QEventLoop::processEvents (this=0xbfb75280, 
    flags=@0xbfb75244) at kernel/qeventloop.cpp:149
#27 0xb77a6abd in QEventLoop::exec (this=0xbfb75280, flags=@0xbfb75288)
    at kernel/qeventloop.cpp:200
#28 0xb77a8d3d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#29 0xb6e77567 in QApplication::exec () at kernel/qapplication.cpp:3304
#30 0x0804b326 in _start ()
#0  0xb7eeb410 in __kernel_vsyscall ()
Comment 1 Thomas McGuire 2008-07-31 23:27:28 UTC

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