Summary: | Korganizer crash when I save in egroupware ressource (delete, QObjectPrivate::derefSender, disconnect, KIO::SchedulerPrivate::jobFinished) | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | niko <nk> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | andresbajotierra, le.petit.fou, smartins |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
niko
2009-08-24 08:26:24 UTC
- Can you always reproduce the crash ? Thanks (In reply to comment #1) > - Can you always reproduce the crash ? > Thanks I don't understand question, you ask me to crash again ? or if the crash appear each time ? I'm not sure that append every time I save, I try now. I'm not familiar woth bucktracking, if Korganizer crash I do bug and marke as duplicate or just paste the report here ? I can run tests if you want, and, I can test beta version if it's usefull thanks I crash again, I have modified some task, when I clic on "enregistrer", tadammm :) Crash Bug report : Application: KOrganizer (korganizer), signal: Segmentation fault [KCrash Handler] #6 0xb5d04896 in memcpy () from /lib/tls/i686/cmov/libc.so.6 #7 0x087705d4 in ?? () #8 0xb6fd8647 in QList<KIO::Task>::detach_helper (this=0x87705d4) at /usr/include/qt4/QtCore/qlist.h:524 #9 0xb6fd6d56 in KIO::ConnectionPrivate::commandReceived (this=0x87705d0, task=@0xbff3791c) at /usr/include/qt4/QtCore/qlist.h:119 #10 0xb6fd6f10 in KIO::Connection::qt_metacall (this=0x87705e0, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbff378dc) at /build/buildd/kde4libs-4.3.0/obj-i486-linux-gnu/kio/connection.moc:74 #11 0xb606c1b8 in QMetaObject::activate (sender=0x948bb70, from_signal_index=5, to_signal_index=5, argv=0xbff378dc) at kernel/qobject.cpp:3113 #12 0xb606ce42 in QMetaObject::activate (sender=0x948bb70, m=0xb71b6860, local_signal_index=1, argv=0xbff378dc) at kernel/qobject.cpp:3187 #13 0xb6fd5263 in KIO::AbstractConnectionBackend::commandReceived (this=0x948bb70, _t1=@0xbff3791c) at /build/buildd/kde4libs-4.3.0/obj-i486-linux-gnu/kio/connection_p.moc:90 #14 0xb6fd619b in KIO::SocketConnectionBackend::socketReadyRead (this=0x948bb70) at /build/buildd/kde4libs-4.3.0/kio/kio/connection.cpp:369 #15 0xb6fd640b in KIO::SocketConnectionBackend::qt_metacall (this=0x948bb70, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbff379c8) at /build/buildd/kde4libs-4.3.0/obj-i486-linux-gnu/kio/connection_p.moc:146 #16 0xb606c1b8 in QMetaObject::activate (sender=0x8771ba8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #17 0xb606ce42 in QMetaObject::activate (sender=0x8771ba8, m=0xb6149028, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #18 0xb60a6727 in QIODevice::readyRead (this=0x8771ba8) at .moc/release-shared/moc_qiodevice.cpp:85 #19 0xb6e7c1c2 in QAbstractSocketPrivate::canReadNotification (this=0x95416b8) at socket/qabstractsocket.cpp:604 #20 0xb6e6914b in QAbstractSocketEngine::readNotification (this=0x8748088) at socket/qabstractsocketengine.cpp:154 #21 0xb6e6a4a6 in QReadNotifier::event (this=0x9482ee0, e=0xbff37dc0) at socket/qnativesocketengine.cpp:1036 #22 0xb6517d3c in QApplicationPrivate::notify_helper (this=0x84559e8, receiver=0x9482ee0, e=0xbff37dc0) at kernel/qapplication.cpp:4056 #23 0xb652003e in QApplication::notify (this=0xbff3800c, receiver=0x9482ee0, e=0xbff37dc0) at kernel/qapplication.cpp:3603 #24 0xb7d3e5cd in KApplication::notify (this=0xbff3800c, receiver=0x9482ee0, event=0xbff37dc0) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302 #25 0xb6056bcb in QCoreApplication::notifyInternal (this=0xbff3800c, receiver=0x9482ee0, event=0xbff37dc0) at kernel/qcoreapplication.cpp:610 #26 0xb608258a in socketNotifierSourceDispatch (source=0x8452b60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #27 0xb514cb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #28 0xb51500eb in ?? () from /usr/lib/libglib-2.0.so.0 #29 0xb5150268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #30 0xb60822f8 in QEventDispatcherGlib::processEvents (this=0x8430db0, flags={i = -1074561256}) at kernel/qeventdispatcher_glib.cpp:327 #31 0xb65b9a75 in QGuiEventDispatcherGlib::processEvents (this=0x8430db0, flags={i = -1074561208}) at kernel/qguieventdispatcher_glib.cpp:202 #32 0xb60551fa in QEventLoop::processEvents (this=0xbff37fc0, flags={i = -1074561144}) at kernel/qeventloop.cpp:149 #33 0xb6055642 in QEventLoop::exec (this=0xbff37fc0, flags={i = -1074561080}) at kernel/qeventloop.cpp:201 #34 0xb6057ae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #35 0xb6517bb7 in QApplication::exec () at kernel/qapplication.cpp:3525 #36 0x0804ec64 in main (argc=0, argv=0x0) at /build/buildd/kdepim-4.3.0/korganizer/main.cpp:61 With my question I was referring to: if you reproduce the steps that caused the application to crash the first time, does the application crashes again ? - The new backtrace seems a bit different, but it is also related to KIO. Thanks If you need something tell me :) My c/c++ level is little and old, so I can't do big job, but testing I can For this crash, I have erase some task, all of them, And try to save. egroupware is done through an akonadi resource now, rewritten from scratch. |