kontact crashed with SIGSEGV in KCal::CalendarResources::resourceManager()

Bug #318879 reported by Kaltsi
8
Affects Status Importance Assigned to Milestone
KDE PIM
Invalid
High
kdepimlibs (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kdepim

Description: Ubuntu jaunty (development branch)
Release: 9.04

apt-cache policy kdepim
kdepim:
  Installed: (none)
  Candidate: 4:4.1.96-0ubuntu2
  Version table:
     4:4.1.96-0ubuntu2 0
        500 http://archive.ubuntu.com jaunty/main Packages

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/kontact
Package: kontact 4:4.1.96-0ubuntu2
ProcCmdline: /usr/bin/kontact
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdepim
StacktraceTop:
 KCal::CalendarResources::resourceManager ()
 ?? () from /usr/lib/kde4/kontact_specialdatesplugin.so
 ?? () from /usr/lib/kde4/kontact_specialdatesplugin.so
 QMetaObject::activate () from /usr/lib/libQtCore.so.4
 QMetaObject::activate () from /usr/lib/libQtCore.so.4
Title: kontact crashed with SIGSEGV in KCal::CalendarResources::resourceManager()
Uname: Linux 2.6.28-4-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Kaltsi (kaltsi) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:SDSummaryWidget::updateView (this=0x89ae808)
SDSummaryWidget::qt_metacall (this=0x89ae808,
QMetaObject::activate () from /usr/lib/libQtCore.so.4
QMetaObject::activate () from /usr/lib/libQtCore.so.4
KABC::AddressBook::addressBookChanged (this=0x8db6228,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in kdepim:
importance: Undecided → Medium
Connor Imes (ckimes)
Changed in kdepim:
status: New → Triaged
Revision history for this message
Connor Imes (ckimes) wrote :

Kaltsi,
Can you please explain what you were doing when this crash occurred? How did it happen? Can you reproduce it? Thanks.

Revision history for this message
Steve Stalcup (vorian) wrote :

does this still happen? We are now at 4.2.0

Changed in kdepim:
status: Unknown → Confirmed
Revision history for this message
Harald Sitter (apachelogger) wrote :

Closing due to lack of feedback.

Changed in kdepim (Ubuntu):
status: Triaged → Invalid
affects: kdepim (Ubuntu) → kdepimlibs (Ubuntu)
Changed in kdepim:
status: Confirmed → Unknown
Changed in kdepim:
status: Unknown → Invalid
Changed in kdepim:
importance: Unknown → High
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.