Bug 229268 - crash adding calendar resource to kontact
Summary: crash adding calendar resource to kontact
Status: RESOLVED DUPLICATE of bug 220807
Alias: None
Product: kdepimlibs
Classification: Applications
Component: kcal (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-03 17:19 UTC by Gianmarco Galletto
Modified: 2011-06-18 17:35 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 Gianmarco Galletto 2010-03-03 17:19:39 UTC
Application that crashed: systemsettings
Version of the application: 1.0
KDE Version: 4.3.5 (KDE 4.3.5) "release 3"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.12-0.1-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

What I was doing when the application crashed:
Created google calendar resource, adding calendar to kontact crashed systemsettings akonadi configuration

 -- Backtrace:
Application: Impostazioni di sistema (systemsettings), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fc9c38b1f5a in KRES::Manager<KRES::Resource>::notifyResourceAdded (this=0x972d40, res=0x18bcdf0) at /usr/src/debug/kdepimlibs-4.3.5/kresources/manager.h:415
#6  0x00007fc9c38a972d in KRES::ManagerImpl::dbusKResourceAdded (this=0x12d0e70, managerId=<value optimized out>, resourceId=...) at /usr/src/debug/kdepimlibs-4.3.5/kresources/managerimpl.cpp:260
#7  0x00007fc9c38aa244 in KRES::ManagerImpl::qt_metacall (this=0x12d0e70, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd9c57190)
    at /usr/src/debug/kdepimlibs-4.3.5/build/kresources/managerimpl.moc:82
#8  0x00007fc9d10abb78 in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=<value optimized out>, 
    slotIdx=<value optimized out>) at qdbusintegrator.cpp:891
#9  0x00007fc9d10b316f in QDBusCallDeliveryEvent::placeMetaCall(QObject*) () from /usr/lib64/libQtDBus.so.4
#10 0x00007fc9d0da42d9 in QObject::event (this=0x12d0e70, e=0x1919230) at kernel/qobject.cpp:1111
#11 0x00007fc9d19142ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#12 0x00007fc9d191b57e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#13 0x00007fc9d250f016 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#14 0x00007fc9d0d94ddc in QCoreApplication::notifyInternal (this=0x7fffd9c57b30, receiver=0x12d0e70, event=0x1919230) at kernel/qcoreapplication.cpp:610
#15 0x00007fc9d0d959ea in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213
#16 QCoreApplicationPrivate::sendPostedEvents (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.cpp:1247
#17 0x00007fc9d0dbd803 in sendPostedEvents () at kernel/qcoreapplication.h:218
#18 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:276
#19 0x00007fc9cd9cddee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007fc9cd9d17b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fc9cd9d18e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fc9d0dbd3a3 in QEventDispatcherGlib::processEvents (this=0x617430, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#23 0x00007fc9d19a731e in ?? () from /usr/lib64/libQtGui.so.4
#24 0x00007fc9d0d93712 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#25 0x00007fc9d0d93ae4 in QEventLoop::exec (this=0x7fffd9c57a80, flags=) at kernel/qeventloop.cpp:201
#26 0x00007fc9d0d95c99 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#27 0x000000000040cbd9 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.3.5/systemsettings/app/main.cpp:51

Reported using DrKonqi
Comment 1 Christoph Feck 2011-06-18 17:35:31 UTC

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