KDE-Forum.org

First, please report bug 'n crash reports to http://bugs.kde.org, that's the place where the Kontact developers gather.

Second, how did you install Kontact?

Could you try to reinstall Kontact + all it's dependencies?

I have the same issue:

KDE3 build server update 3.5.6 release 25.2

updated KDE after clean install of Suse 10.2.

Anyone got a workaround?

Thanks

Hi,

if you have installed basket, start it at first.


p.s. sorry for my bad english

I have a similar, possibly/probably related problem. This is also under Mandriva Spring. Kontact crashed when I was adding a calendar - kde resources in kcontrol show that it wasn't actually added. Since then I have been unable to use kontact on this box.

The difference is that kmail and kabc both run as stand-alone apps, but korganizer will not launch. It heavily uses resources then crashes. The feedback I have seen in konsole is

kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated
action. ##Lots of these, then
WeaverThreadLogger: thread (ID: 1) suspended.
WeaverThreadLogger: thread (ID: 2) suspended.
WeaverThreadLogger: thread (ID: 3) suspended.
WeaverThreadLogger: thread (ID: 4) suspended.
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
*** KMail got signal 6 (Crashing)
ERROR: Communication problem with kontact, it probably crashed.

[1]+ Exit 255 kontact

and, when calling korganizer direct

terminate called after throwing an instance of std::bad_alloc'
what(): St9bad_alloc
KCrash: application korganizer crashing
ERROR: communication problem with korganizer, it probably crashed.

Anne

There is another thread here that seems to be related. See "Kontact does not start". There is a solution posted in there.

In short, one of the respondents there seems to have found that deleting the std.ics and backup works. I was able to replicate the workaround. I was also able to open the old calendar file in Korganizer and export. Then I was able to load that exported file back into Kontact. Restored everything.

Kudos to the person who suggested the workaround.

This was not the cause in my case. I did try the solution, but it didn't help. Also, the .ics worked on my laptop. I could not find any problem by inspecting all the configuration files I could find, but renaming ~/.kde and re-launching allowed everything to work again. I simply copied back everything from the old folder except the korganizer part of ~/.kde/share/apps and ~/.kde/share/config, but pointing it to the original .ics file. It has worked ever since.

Whatever went wrong, the attempt to add a second .ics was a red herring, a total coincidence. Checking in kcontrol showed that it had never been added. I have added it since then, and everything is fine.

Thanks for trying to help. I hope my report helps someone else.

Anne