Bug 196951 - Kontact crashed on exit
Summary: Kontact crashed on exit
Status: RESOLVED DUPLICATE of bug 165548
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-18 00:57 UTC by Javier
Modified: 2009-06-19 23:26 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 Javier 2009-06-18 00:57:14 UTC
Application that crashed: kontact
Version of the application: 4.3.0 pre
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-8-generic x86_64
Distribution: Ubuntu karmic (development branch)

What I was doing when the application crashed:
I wasn't doing anything in particular as I'm playing around a little with karmic alpha 2.
So no mail accounts configured, no contacts, no appointmens and the default feeds for akregator part.

The only "strange" thing i did was go to system settings, advanced and set up the akonadi resources. The migrations were successfull and thats it.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  QString::operator== (this=<value optimized out>, other=@0x7ffff0d560f0) at ../../include/QtCore/../../src/corelib/tools/qstring.h:104
#6  0x00007f307cb95288 in KDirWatchPrivate::inotifyEventReceived (this=0x26eb020) at ../../kio/kio/kdirwatch.cpp:298
#7  0x00007f307cb959a4 in KDirWatchPrivate::qt_metacall (this=0x26eb020, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff0d57330) at ./kdirwatch_p.moc:75
#8  0x00007f307e6e574c in QMetaObject::activate (sender=0x26ed7a0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x31004b002e0070) at kernel/qobject.cpp:3120
#9  0x00007f307e71b88e in QSocketNotifier::activated (this=0x54005000490052, _t1=17) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#10 0x00007f307e6ea0e3 in QSocketNotifier::event (this=0x26ed7a0, e=0x7ffff0d57870) at kernel/qsocketnotifier.cpp:316
#11 0x00007f307efe727c in QApplicationPrivate::notify_helper (this=0x1a6f6c0, receiver=0x26ed7a0, e=0x7ffff0d57870) at kernel/qapplication.cpp:4057
#12 0x00007f307efee54e in QApplication::notify (this=0x7ffff0d57b90, receiver=0x26ed7a0, e=0x7ffff0d57870) at kernel/qapplication.cpp:4022
#13 0x00007f307fc44c16 in KApplication::notify (this=0x7ffff0d57b90, receiver=0x26ed7a0, event=0x7ffff0d57870) at ../../kdeui/kernel/kapplication.cpp:302
#14 0x00007f307e6d020c in QCoreApplication::notifyInternal (this=0x7ffff0d57b90, receiver=0x26ed7a0, event=0x7ffff0d57870) at kernel/qcoreapplication.cpp:610
#15 0x00007f307e6f8dea in socketNotifierSourceDispatch (source=0x1a6b470) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#16 0x00007f30784e58fe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0x00007f30784e8fd8 in ?? () from /usr/lib/libglib-2.0.so.0
#18 0x00007f30784e9100 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#19 0x00007f307e6f8b66 in QEventDispatcherGlib::processEvents (this=0x1a3e850, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#20 0x00007f307f07b55e in QGuiEventDispatcherGlib::processEvents (this=0x54005000490052, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#21 0x00007f307e6ceb12 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#22 0x00007f307e6ceee4 in QEventLoop::exec (this=0x7ffff0d57ad0, flags=) at kernel/qeventloop.cpp:200
#23 0x00007f307e6d0f89 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#24 0x0000000000403f27 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Dario Andres 2009-06-19 22:56:59 UTC
Strange enough, looks related to bug 165548.
Thanks
Comment 2 Dario Andres 2009-06-19 23:26:32 UTC
Thanks

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