Summary: | Korganizer crashed when trying to add a new event. | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Luis Silva <lacsilva> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | allanmills2009, barth.kde, bugs.kde.com, emmanuel, frank.sperer, kdenis, mikebooth76, prozac, reb, socialklaus, wallace.maxted |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.2.3 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
VCard used to reproduce crash
Backtrace during crash of kaddressbook |
Description
Luis Silva
2015-09-29 16:50:34 UTC
Incidentally, I am getting very similar backtraces for a systematic crash at kaddressbook's start and a series of other crashes in kdepim. Created attachment 95377 [details]
VCard used to reproduce crash
I was able to reproduce this crash on an empty kaddressbook. I've imported the attached VCard and directly after, kaddressbook crashed (will attach backtrace). It kept on crashing directly after each restart. Also KOrganizer crashes if I try to add a new event.
System information:
Kubuntu Wily Werewolf
KDE FW 5.15.0
Qt 5.4.2
Created attachment 95378 [details]
Backtrace during crash of kaddressbook
This still happens with korganizer and kaddresssbook, both version 15.12.1. KDE-5.18 Qt-5.5.1 After importing new *.vcf files: Korganizer crashes when trying to add a new event or after I click on the 'To-Do List' view; Kaddressbook crashes immediately after startup. Does kaddressbook still crash when the vCard (a few postings above this one) is imported _after_ first removing the "BDAY" line in the vCard-file (and maybe also other lines with a date)? There are similar reports about synchronizing/importing contacts from different sources or adding a new contact manually that results in a crash. See for example my bug report: https://bugs.kde.org/show_bug.cgi?id=358696 *** Bug 353797 has been marked as a duplicate of this bug. *** *** Bug 355158 has been marked as a duplicate of this bug. *** *** Bug 354728 has been marked as a duplicate of this bug. *** *** Bug 353482 has been marked as a duplicate of this bug. *** *** Bug 359610 has been marked as a duplicate of this bug. *** This bug was fixed along with Bug 365944, with the patch mentioned in Bug 365944, Comment 2, i.e., in version 5.3.0 or later. *** Bug 354193 has been marked as a duplicate of this bug. *** *** Bug 361180 has been marked as a duplicate of this bug. *** *** Bug 378617 has been marked as a duplicate of this bug. *** |