akonadi_kcal_resource crashed with SIGSEGV in KCal::ResourceCalendar::save()

[Pelado]

Binary package hint: kdepim-runtime

a

ProblemType: Crash
Architecture: i386
Date: Wed Oct 14 11:37:19 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/akonadi_kcal_resource
Package: kdepim-runtime 4:4.3.2-0ubuntu1
ProcCmdline: /usr/bin/akonadi_kcal_resource --identifier akonadi_kcal_resource_1
ProcEnviron:
 LANGUAGE=es_ES:es:en_GB:en
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0x6e4387 <_ZN4KCal16ResourceCalendar4saveEPNS_9IncidenceE+23>: mov 0xc(%esi),%eax
 PC (0x006e4387) ok
 source "0xc(%esi)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdepim-runtime
Stacktrace:
 #0 0x006e4387 in KCal::ResourceCalendar::save(KCal::Incidence*) ()
    from /usr/lib/libkcal.so.4
 No symbol table info available.
 #1 0x0804f792 in _start ()
 No symbol table info available.
StacktraceTop:
 KCal::ResourceCalendar::save(KCal::Incidence*) ()
 _start ()
Title: akonadi_kcal_resource crashed with SIGSEGV in KCal::ResourceCalendar::save()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:2323): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

StacktraceTop:KCal::ResourceCalendar::save (this=0x0, incidence=0x0)
KCalResource::aboutToQuit (this=0x9cd5340)
Akonadi::AgentBase::quit (this=0x9cd5340)
ControlAdaptor::qt_metacall (this=0x9d08560,
QDBusConnectionPrivate::deliverCall (this=0x9c42568,

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!