Hi! If you can reproduce the crash, you should install the debug enabled packages and provide a new backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!

This may be related/duplicate of bug 159532 (bug 159247).

Yes, it could.

@Thomas: did you attached some files on your calendar?

@FiNeX

ok, the gdb was installed long ago, so you probably mean Valgrind?! What I've found out too was I made a not so good bug report (too many "no debugging symbols found" - ok).

@FiNeX +Dario

Don't know if it's related, maybe but I should have had one or at most two events with binary attachments when I started to play around with Korganizer in the early beginning.

What I'm thinking about is that I've used the possibility of "advanced reminders" - among other things - to provide sounds via audio files in *.ogg from my music list to get reminded in an audible manner like being used from office by that unspeakable proprietary system :-)

Well it never worked, but I copied those similar events very frequently without having their "audible attachments" in mind.

What is really curious via Valgrind korganizer starts up normally, useable for working and closing flawlessly. In contrast with gdb the kde crash handler bubbles up.

Thanks a lot for your prompt replies considering it's Christmas time.

Thomas

@Thomas: I don't mean gdb, I mean that you have to install the debug enabled packages, if you read the guide I've linked before you can understand all :-)

Thanks againg for your feedback

@FiNeX: ok, installed the now hopefully right ones (kdelibs-dbg kdepim-dbg and their dependencies qt-x11-free-dbg, didn't find something like korganizer-dbg) from debian repos and got an alternate error:

[Thread debugging using libthread_db enabled]
[New Thread 0xb5f526c0 (LWP 14995)]
[KCrash handler]
#6  0xb7b8b443 in strlen () from /lib/i686/cmov/libc.so.6
#7  0xb7118c96 in QString::fromUtf8 (
    utf8=0xb5558008 <Address 0xb5558008 out of bounds>, len=-1)
    at tools/qstring.cpp:5804
#8  0xb7a39af5 in Attachment (this=0x92504f0, 
    base64=0xb5558008 <Address 0xb5558008 out of bounds>, mime=@0xb72ae500)
    at /tmp/buildd/kdepim-3.5.9/./libkcal/attachment.cpp:47
#9  0xb7a704cf in KCal::ICalFormatImpl::readAttachment (this=0x90d1268, 
    attach=0x917ad60)
    at /tmp/buildd/kdepim-3.5.9/./libkcal/icalformatimpl.cpp:1246
#10 0xb7a76197 in KCal::ICalFormatImpl::readIncidence (this=0x90d1268, 
    parent=0x9178cf0, tz=0x0, incidence=0x9250138)
    at /tmp/buildd/kdepim-3.5.9/./libkcal/icalformatimpl.cpp:1409
#11 0xb7a7651f in KCal::ICalFormatImpl::readEvent (this=0x90d1268, 
    vevent=0x9178cf0, vtimezone=0x0)
    at /tmp/buildd/kdepim-3.5.9/./libkcal/icalformatimpl.cpp:976
#12 0xb7a7b73e in KCal::ICalFormatImpl::populate (this=0x90d1268, 
    cal=0x903ea40, calendar=0x906b128)
    at /tmp/buildd/kdepim-3.5.9/./libkcal/icalformatimpl.cpp:2040
#13 0xb7a69e4c in KCal::ICalFormat::fromRawString (this=0xbfb3d4ac, 
    cal=0x903ea40, text=@0xbfb3d43c)
    at /tmp/buildd/kdepim-3.5.9/./libkcal/icalformat.cpp:184
#14 0xb7a6a2a3 in KCal::ICalFormat::load (this=0xbfb3d4ac, 
    calendar=0x903ea40, fileName=@0xbfb3d510)
    at /tmp/buildd/kdepim-3.5.9/./libkcal/icalformat.cpp:98
#15 0xb7a9de59 in KCal::FileStorage::load (this=0xbfb3d504)
    at /tmp/buildd/kdepim-3.5.9/./libkcal/filestorage.cpp:97
#16 0xb7a56dc4 in KCal::CalendarLocal::load (this=0x903ea40, 
    fileName=@0xbfb3d550, format=0x0)
    at /tmp/buildd/kdepim-3.5.9/./libkcal/calendarlocal.cpp:66
#17 0xb7aa2f5b in KCal::ResourceLocal::doLoad (this=0x903ea08)
    at /tmp/buildd/kdepim-3.5.9/./libkcal/resourcelocal.cpp:154
#18 0xb7aa141a in KCal::ResourceCalendar::load (this=0x903ea08)
    at /tmp/buildd/kdepim-3.5.9/./libkcal/resourcecalendar.cpp:122
#19 0xb7ab0d0e in KCal::CalendarResources::load (this=0x902b6a0)
    at /tmp/buildd/kdepim-3.5.9/./libkcal/calendarresources.cpp:143
#20 0x08052135 in KOrganizerApp::processCalendar (this=0xbfb3dec8, 
    url=@0xbfb3d834) at /tmp/buildd/kdepim-3.5.9/./korganizer/koapp.cpp:143
#21 0x080526bc in KOrganizerApp::newInstance (this=0xbfb3dec8)
    at /tmp/buildd/kdepim-3.5.9/./korganizer/koapp.cpp:89
#22 0xb74b63ea in KUniqueApplication::processDelayed (this=0xbfb3dec8)
    at /build/buildd/kdelibs-3.5.10.dfsg.1/./kdecore/kuniqueapplication.cpp:444
#23 0xb74bc803 in KUniqueApplication::qt_invoke (this=0xbfb3dec8, _id=19, 
    _o=0xbfb3d9e4) at ./kuniqueapplication.moc:86
#24 0xb6e4ff6d in QObject::activate_signal (this=0x8ee1d48, clist=0x8ee3680, 
    o=0xbfb3d9e4) at kernel/qobject.cpp:2359
#25 0xb717a05e in QSignal::signal (this=0x8ee1d48, t0=@0x8ee1d70)
    at .moc/release-shared-mt/moc_qsignal.cpp:100
#26 0xb6e6b8c7 in QSignal::activate (this=0x8ee1d48) at kernel/qsignal.cpp:215
#27 0xb6e72993 in QSingleShotTimer::event (this=0x8ee1d20)
    at kernel/qtimer.cpp:289
#28 0xb6df218a in QApplication::internalNotify (this=0xbfb3dec8, 
    receiver=0x8ee1d20, e=0xbfb3dce4) at kernel/qapplication.cpp:2638
#29 0xb6df2f76 in QApplication::notify (this=0xbfb3dec8, receiver=0x8ee1d20, 
    e=0xbfb3dce4) at kernel/qapplication.cpp:2361
#30 0xb74a2b82 in KApplication::notify (this=0xbfb3dec8, receiver=0x8ee1d20, 
    event=0xbfb3dce4)
    at /build/buildd/kdelibs-3.5.10.dfsg.1/./kdecore/kapplication.cpp:550
#31 0xb6de756e in QEventLoop::activateTimers (this=0x8ed0b50)
    at kernel/qapplication.h:523
#32 0xb6da1348 in QEventLoop::processEvents (this=0x8ed0b50, flags=4)
    at kernel/qeventloop_x11.cpp:392
#33 0xb6e08b80 in QEventLoop::enterLoop (this=0x8ed0b50)
    at kernel/qeventloop.cpp:201
#34 0xb6e08a16 in QEventLoop::exec (this=0x8ed0b50)
    at kernel/qeventloop.cpp:148
#35 0xb6df1cff in QApplication::exec (this=0xbfb3dec8)
    at kernel/qapplication.cpp:2761
#36 0x080507d8 in main (argc=)
    at /tmp/buildd/kdepim-3.5.9/./korganizer/main.cpp:58

Hope it's sufficient - thx again

this bug is fixed in KDE 4.2 and some distros using KDE 4.1.

the fix requires the new external libical dependency.

if you cannot upgrade to a newer KDE, the fix is to remove calendar attachments.  One way to do this is to load up your calendar in SunBird.  SunBird does not support calendar attachments and strips them for you.

@Allen: as Sidux is a rolling release, I've to wait for current Debian Testing getting stable next few weeks, so I hope. After that the new Kde 4.1 or hopefully 4.2 is going to transist from experimental to Sid.

Nethertheless it seems to work satiesfying by calling korganizer with valgrind via console as specified on your sites.

Thanks very much to all devs and involved persons for helping to resolve said matter.

Wish you a happy new year!

Thomas