Can't reproduce this.

Did you uncheck/check your resource before creating the new event?

What kind of resource are you using?

The backtrace looks related to bug 172446

What exactly is a resource in KOrganizer?

Here's what I always do: When KOrganizer starts, it has an empty calender. So I click File > Open... and pick my saved kalender.ics file (created some years ago, in case that matters). Then I close the empty calender.

If I recall correctly, the crash happened after the computer resumed from disk.

As I said, I cannot reproduce this.

While I cannot reproduce this at will, it happened again. Same stack trace. I double clicked a day to add an event and KOrganizer crashed while I was entering the new event's title.

BTW, this happened with KOrganizer Version 4.2 rc1 Using KDE 4.2.00 (KDE 4.2.0)

*** Bug 172446 has been marked as a duplicate of this bug. ***

(In reply to comment #6)
> *** Bug 172446 has been marked as a duplicate of this bug. ***

In answer to your question posed in Bug 172446, I am please to say that I can't duplicate this bug under KDE4.2 on fedora 10.

Created attachment 36078 [details]
crash description

Pasting the updated backtrace:

Application that crashed: korganizer
Version of the application: 4.3.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-rc5 x86_64

 -- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fbb2d75b2f8 in FreeBusy (this=<value optimized out>, calendar=<value optimized out>, start=<value optimized out>, end=@0x7fff14518d90)
    at /usr/local/tmp/portage/kde-base/kdepimlibs-4.3.0/work/kdepimlibs-4.3.0/kcal/freebusy.cpp:107
#6  0x00007fbb2d11b5d3 in FreeBusyManager::ownerFreeBusy (this=0xaf5080) at /usr/local/tmp/portage/kde-base/korganizer-4.3.0/work/korganizer-4.3.0/korganizer/freebusymanager.cpp:131
#7  0x00007fbb2d11c1f5 in FreeBusyManager::retrieveFreeBusy (this=0xaf5080, email=@0x7fff14518ea0, forceDownload=false)
    at /usr/local/tmp/portage/kde-base/korganizer-4.3.0/work/korganizer-4.3.0/korganizer/freebusymanager.cpp:357
#8  0x00007fbb2d0e8719 in FreeBusyItem::startDownload (this=0xe878f0, forceDownload=false)
    at /usr/local/tmp/portage/kde-base/korganizer-4.3.0/work/korganizer-4.3.0/korganizer/koeditorfreebusy.cpp:110
#9  0x00007fbb2d0e5b00 in KOEditorFreeBusy::timerEvent (this=0xe10c70, event=0x7fff14519670)
    at /usr/local/tmp/portage/kde-base/korganizer-4.3.0/work/korganizer-4.3.0/korganizer/koeditorfreebusy.cpp:505
#10 0x00007fbb2c191553 in QObject::event (this=0xe10c70, e=0x7fff14518d90) at kernel/qobject.cpp:1066
#11 0x00007fbb2b779048 in QWidget::event (this=0xe10c70, event=0x7fff14519670) at kernel/qwidget.cpp:7946
#12 0x00007fbb2b72badc in QApplicationPrivate::notify_helper (this=0x63bac0, receiver=0xe10c70, e=0x7fff14519670) at kernel/qapplication.cpp:4056
#13 0x00007fbb2b731388 in QApplication::notify (this=0x7fff14519970, receiver=0xe10c70, e=0x7fff14519670) at kernel/qapplication.cpp:4021
#14 0x00007fbb2de83d26 in KApplication::notify (this=0x7fff14519970, receiver=0xe10c70, event=0x7fff14519670)
    at /usr/local/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302
#15 0x00007fbb2c18332b in QCoreApplication::notifyInternal (this=0x7fff14519970, receiver=0xe10c70, event=0x7fff14519670) at kernel/qcoreapplication.cpp:606
#16 0x00007fbb2c1aa8ba in QTimerInfoList::activateTimers (this=0x63e0a0) at kernel/qcoreapplication.h:213
#17 0x00007fbb2c1a82ed in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#18 0x00007fbb2527c1fd in IA__g_main_context_dispatch (context=0x63dc40) at gmain.c:1824
#19 0x00007fbb2527fa48 in g_main_context_iterate (context=0x63dc40, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2455
#20 0x00007fbb2527fb90 in IA__g_main_context_iteration (context=0x63dc40, may_block=1) at gmain.c:2518
#21 0x00007fbb2c1a8236 in QEventDispatcherGlib::processEvents (this=0x612ba0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#22 0x00007fbb2b7b0a6e in QGuiEventDispatcherGlib::processEvents (this=0x7fff14518c80, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007fbb2c181ce2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#24 0x00007fbb2c181e7d in QEventLoop::exec (this=0x7fff14519910, flags=) at kernel/qeventloop.cpp:197
#25 0x00007fbb2c183d69 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x0000000000408ce6 in main (argc=3, argv=0x7fff14519b38) at /usr/local/tmp/portage/kde-base/korganizer-4.3.0/work/korganizer-4.3.0/korganizer/main.cpp:61

Happens to me too just when opening the dialog, only happens every time in a reproducible manner (for me this is an regression after 4.2.4).

I'll perhaps recompile later without optimizations and gdb it, if you want some further info.

(meanwhile could someone tell which libs need recompiling)

Created attachment 36079 [details]
Appropriate ical file to reproduce the bug

The bug is not reproducible on arbitary ical file, however this file seems to reproduce the problem.

The file is fully created using korganizer though seems to contain quite a lot of metadata for an empty calendar...

SVN commit 1013809 by winterz:

don't crash if the calendar passed to the FreeBusy is zero.
BUG: 186597
MERGE: 4.3


 M  +4 -1      freebusy.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1013809

SVN commit 1013810 by winterz:

Backport r1013809 by winterz from trunk to the 4.3 branch:

don't crash if the calendar passed to the FreeBusy is zero.
CCBUG: 186597
MERGE: 4.3



 M  +4 -1      freebusy.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1013810