KDE-Forum.org

Any useful errors on the console? If not, try to reinstall the kdepim package (including all it's dependencies). It seems to have worked for others.

If the calendar does not contain sensitive information, I'd like to see it (as a KOrganizer dev )

I have had the exact same problem with Kontact. For some reason the app just wont load any longer. I have tried adding and removing the service. I upgraded to KDE 3.5. Nothing helped.

Upon reading the earlier posts I went in and changed my std.ics to std.ics.old and the app loads just fine now. Of course I have lost all my calendar entries now. Any ideas on why that file is corrupt or how to fix a corrupted file?

I am happy to submit my file for review if that helps.

Thanks
Sean

Last few days i noticed that kontact took too long to start. With the help of this site that finally i found through google i noticed that the file in ~/.kde/share/apps/korganizer/std.ics has a size of 160MB!! causing trouble as i saw in ram and swap files.
I opened the std.ics with kate and noticed that in my case was in alarm sections a file from media/windows directory!!. I do not know either from wine or the windows partition.
Anyway i deleted that section from beginalarm to endalarm, i copied everything else and pasted in new file, deleted the std.ics and save the new file with the std.ics name in the same location i founded it.
Know the std.ics has 9.5KB, i have my data and everything is ok.

Hello folks. I've been having similar problems. Launching Kontact causes an error "The application Kontact (kontact) crashed and caused the signal 11 (SIGSEGV)." I tried your idea about deleting the std.ics and its backup. It worked. I'm not sure why.

Deleting the std.ics allows me to open Kontact. If I try to import the file back in it fails. The file size was only 404.6KB and doesn't contain any alarms (that I'm aware of). All of the component apps seem to work fine including Korganizer. The problem seems to be isolated to Kontact. Below is the backtrace if it is helpful to anyone.

Could this have been a bug introduced in version -37.1? has anyone tied reverting back to -41?

System is latest OpenSUSE 10.2 with KDE 3.5 (kdebase3 3.5.7-64.1). kdepim is 3.5.7-37.1


Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1241684272 (LWP 7646)]
[New Thread -1284641904 (LWP 7650)]
[New Thread -1276249200 (LWP 7649)]
[New Thread -1267856496 (LWP 764]
[New Thread -1259463792 (LWP 7647)]
[KCrash handler]
#9 0xb6ed6edd in QString::QString () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb668df5e in KCal::Incidence::relatedToUid ()
from /opt/kde3/lib/libkcal.so.2
#11 0xb66c6dc1 in KCal::ICalFormatImpl::populate ()
from /opt/kde3/lib/libkcal.so.2
#12 0xb66bf3fa in KCal::ICalFormat::fromRawString ()
from /opt/kde3/lib/libkcal.so.2
#13 0xb66bfa60 in KCal::ICalFormat::load () from /opt/kde3/lib/libkcal.so.2
#14 0xb66e6ba3 in KCal::FileStorage::load () from /opt/kde3/lib/libkcal.so.2
#15 0xb66b0e64 in KCal::CalendarLocal::load () from /opt/kde3/lib/libkcal.so.2
#16 0xb66ea462 in KCal::ResourceLocal::doLoad ()
from /opt/kde3/lib/libkcal.so.2
#17 0xb66e982a in KCal::ResourceCalendar::load ()
from /opt/kde3/lib/libkcal.so.2
#18 0xb66f58ae in KCal::CalendarResources::load ()
from /opt/kde3/lib/libkcal.so.2
#19 0xb59e873b in SummaryWidget:ummaryWidget ()
from /opt/kde3/lib/kde3/libkontact_korganizerplugin.so
#20 0xb59e1453 in KOrganizerPlugin::createSummaryWidget ()
from /opt/kde3/lib/kde3/libkontact_korganizerplugin.so
#21 0xb55795ea in SummaryViewPart::updateWidgets ()
from /opt/kde3/lib/kde3/libkontact_summaryplugin.so
#22 0xb557a528 in SummaryViewPart::initGUI ()
from /opt/kde3/lib/kde3/libkontact_summaryplugin.so
#23 0xb557ab8b in SummaryViewPart:ummaryViewPart ()
from /opt/kde3/lib/kde3/libkontact_summaryplugin.so
#24 0xb5576c81 in SummaryView::createPart ()
from /opt/kde3/lib/kde3/libkontact_summaryplugin.so
#25 0xb7daa0a2 in Kontact:lugin::part ()
from /opt/kde3/lib/libkpinterfaces.so.1
#26 0x0805bf10 in Kontact::MainWindow::selectPlugin ()
#27 0x0805a7d1 in Kontact::MainWindow::activatePluginModule ()
#28 0x08058709 in KontactApp::newInstance ()
#29 0xb71fcdbd in KUniqueApplication::processDelayed ()
from /opt/kde3/lib/libkdecore.so.4
#30 0xb722d078 in KUniqueApplication::qt_invoke ()
from /opt/kde3/lib/libkdecore.so.4
#31 0xb6c04f1d in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0xb6f400ae in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0xb6c20ff7 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0xb6c28383 in QSingleShotTimer::event ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0xb6ba59c7 in QApplication::internalNotify ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0xb6ba6791 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#37 0xb725d8d2 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#38 0xb6b9abd3 in QEventLoop::activateTimers ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#39 0xb6b54c40 in QEventLoop::processEvents ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#40 0xb6bbc7f0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#41 0xb6bbc686 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#42 0xb6ba557f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#43 0x08058c59 in main ()

In my case i managed to isolate what in std.ics caused the problem. I had tried to attach a windows sound in some events. In your case should be something else. I deleted that part of this file only. You might have to look more carefull the std.ics file so as to recognize what causes the problem. I dont know the commands that that file uses. I only recognize the section structure that it has (begin ... end). i am afraid i cannt be more helpfull. good luck