Version: 4.2 rc1 (using 4.2.00 (KDE 4.2.0), Kubuntu packages) Compiler: cc OS: Linux (i686) release 2.6.27-11-generic Because of a full disk korganizer left std.ics with 0 bytes. After copying the backup version back, the dates are shown, but removing appointments is ignored and korganizer crashes when new appointments are created: Anwendung: Kontact (kontact), Signal SIGSEGV Thread 1 (Thread 0xb4ad06c0 (LWP 385)): [KCrash Handler] #6 KCal::ErrorFormat::errorCode (this=0xa36a998) at /build/buildd/kdepimlibs-4.2.0/kcal/exceptions.cpp:128 #7 0xb074e5e1 in KOEventEditor::processInput (this=0xa4700c8) at /build/buildd/kdepim-4.2.0/korganizer/koeventeditor.cpp:324 #8 0xb074ceb9 in KOIncidenceEditor::slotButtonClicked (this=0xa952dc8, button=4) at /build/buildd/kdepim-4.2.0/korganizer/koincidenceeditor.cpp:98 #9 0xb6c437b4 in KDialog::qt_metacall (this=0xa952dc8, _c=QMetaObject::InvokeMetaMethod, _id=33, _a=0xbfaa18cc) at /build/buildd/kde4libs-4.2.0/obj-i486-linux-gnu/kdeui/kdialog.moc:181 #10 0xb6d0867a in KPageDialog::qt_metacall (this=0xa952dc8, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbfaa18cc) at /build/buildd/kde4libs-4.2.0/obj-i486-linux-gnu/kdeui/kpagedialog.moc:63 #11 0xb074b9ea in KOIncidenceEditor::qt_metacall (this=0xa952dc8, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbfaa18cc) at /build/buildd/kdepim-4.2.0/obj-i486-linux-gnu/korganizer/koincidenceeditor.moc:106 #12 0xb074eb5a in KOEventEditor::qt_metacall (this=0xa952dc8, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbfaa18cc) at /build/buildd/kdepim-4.2.0/obj-i486-linux-gnu/korganizer/koeventeditor.moc:69 #13 0xb5d21a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #14 0xb5d227e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #15 0xb5d25873 in QSignalMapper::mapped () from /usr/lib/libQtCore.so.4 #16 0xb5d260fd in QSignalMapper::map () from /usr/lib/libQtCore.so.4 #17 0xb5d262ee in QSignalMapper::map () from /usr/lib/libQtCore.so.4 #18 0xb5d26bbb in QSignalMapper::qt_metacall () from /usr/lib/libQtCore.so.4 #19 0xb5d21a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #20 0xb5d21e60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #21 0xb67ace61 in QAbstractButton::clicked () from /usr/lib/libQtGui.so.4 #22 0xb6500199 in ?? () from /usr/lib/libQtGui.so.4 #23 0xb6501d94 in ?? () from /usr/lib/libQtGui.so.4 #24 0xb6502026 in QAbstractButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4 #25 0xb6216962 in QWidget::event () from /usr/lib/libQtGui.so.4 #26 0xb650003e in QAbstractButton::event () from /usr/lib/libQtGui.so.4 #27 0xb65a6910 in QPushButton::event () from /usr/lib/libQtGui.so.4 #28 0xb61be8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #29 0xb61c70e1 in QApplication::notify () from /usr/lib/libQtGui.so.4 #30 0xb6cd7fed in KApplication::notify (this=0xbfaa28f8, receiver=0xa96cd28, event=0xbfaa2028) at /build/buildd/kde4libs-4.2.0/kdeui/kernel/kapplication.cpp:307 #31 0xb5d0ce61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #32 0xb61c636e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #33 0xb6230656 in ?? () from /usr/lib/libQtGui.so.4 #34 0xb622f9e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #35 0xb62597aa in ?? () from /usr/lib/libQtGui.so.4 #36 0xb4fe76f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #37 0xb4feada3 in ?? () from /usr/lib/libglib-2.0.so.0 #38 0xb4feaf61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #39 0xb5d37478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #40 0xb6258ea5 in ?? () from /usr/lib/libQtGui.so.4 #41 0xb5d0b52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #42 0xb5d0b6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #43 0xb5d0dda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #44 0xb61be767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #45 0x0804c072 in main (argc=1, argv=0xbfaa2bf4) at /build/buildd/kdepim-4.2.0/kontact/src/main.cpp:218
I've seen something like this but for journals, can you get a valgrind report? 1. Install valgring 2. run: valgrind korganizer --nofork &> report.txt 3. make it crash 4. attach report.txt here If needed, further information about valgrind is here: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_Valgrind
Created attachment 31567 [details] The requested valgrind report
I'm getting the same report creating journals: korganizer(31804) IncidenceChanger::addIncidence: " "ff" " ==31804== ==31804== Invalid read of size 4 ==31804== at 0x4592367: KCal::ErrorFormat::errorCode() (exceptions.cpp:128) ==31804== by 0x485C545: KOJournalEditor::processInput() (kojournaleditor.cpp:168) ==31804== by 0x4855641: KOIncidenceEditor::slotButtonClicked(int) (koincidenceeditor.cpp:98) ==31804== by 0x4157694: KDialog::qt_metacall(QMetaObject::Call, int, void**) (kdialog.moc:182) ==31804== by 0x422A0AF: KPageDialog::qt_metacall(QMetaObject::Call, int, void**) (kpagedialog.moc:64) ==31804== by 0x4855929: KOIncidenceEditor::qt_metacall(QMetaObject::Call, int, void**) (koincidenceeditor.moc:106) ==31804== by 0x485BE19: KOJournalEditor::qt_metacall(QMetaObject::Call, int, void**) (kojournaleditor.moc:63) ==31804== by 0x544732F: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3061) ==31804== by 0x54477B8: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3136) ==31804== by 0x544D037: QSignalMapper::mapped(int) (moc_qsignalmapper.cpp:95) ==31804== by 0x544D11A: QSignalMapper::map(QObject*) (qsignalmapper.cpp:261) ==31804== by 0x544D21B: QSignalMapper::map() (qsignalmapper.cpp:252) ==31804== Address 0xc is not stack'd, malloc'd or (recently) free'd I will debug this Wednesday
SVN commit 931231 by smartins: Don't crash when stdcal->exception() is null. CCBUG: 185314 M +2 -1 incidencechanger.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=931231
The crash is fixed, you should have got a "Can't save event" warning. But we still don't know why you can't save the event, do you have space? Check the file's permissions.
Changing the bug status since we didn't get feedback.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!