korganizer crashed with SIGSEGV in KCal::IncidenceBase::uid()

Bug #425758 reported by Luis Silva
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdepim (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: kdepim

Crash happening when dealing with TODO's with SubTODO's. My calendar is stored on an imap folder via kmail. I am using the akonadi compatibility ressource.

ProblemType: Crash
Architecture: i386
Date: Mon Sep 7 16:52:22 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/korganizer
Package: korganizer 4:4.3.1-0ubuntu1
ProcCmdline: /usr/bin/korganizer
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SegvAnalysis:
 Segfault happened at: 0x57a0e1 <_ZNK4KCal13IncidenceBase3uidEv+17>: lock incl (%edx)
 PC (0x0057a0e1) ok
 source "(%edx)" (0x00000000) not located in a known VMA region (needed readable region)!
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdepim
StacktraceTop:
 KCal::IncidenceBase::uid() const ()
 KCal::Calendar::removeRelations(KCal::Incidence*) ()
 KCal::CalendarLocal::deleteTodo(KCal::Todo*) ()
 ?? () from /usr/lib/kde4/kcal_akonadi.so
 KCal::CalendarResources::deleteTodo(KCal::Todo*) ()
Title: korganizer crashed with SIGSEGV in KCal::IncidenceBase::uid()
Uname: Linux 2.6.31-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Luis Silva (lacsilva) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:KCal::IncidenceBase::uid (this=0xb5c5cc78)
KCal::Calendar::removeRelations (this=0x96b09c4,
KCal::CalendarLocal::deleteTodo (this=0x96b09c4,
KCal::ResourceAkonadi::deleteTodo (this=0x9574f00,
KCal::CalendarResources::deleteTodo (this=0x95181a0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdepim (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This is the same crash as bug 384983, albeit triggered differently.

visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.