Bug 184950 - segfault due to some (corrupted) entry in the akonadi database
Summary: segfault due to some (corrupted) entry in the akonadi database
Status: RESOLVED DOWNSTREAM
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 4.2.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-19 17:11 UTC by Christophe Delaere
Modified: 2009-02-20 00:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Delaere 2009-02-19 17:11:34 UTC
Version:            (using KDE 4.2.0)
Compiler:          gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC) 
OS:                Linux
Installed from:    Fedora RPMs

It all started when I added attachments to an appointment in korganizer (via kontact), after I received a mail related to it.
I added:
- one pdf
- a second pdf
- the mail containing both pdf as attachment.

Then, kontact crashed... and I was unable to restart it. The backtrace indicated that it was crashing when decoding the attachments bith libical... in some toString method.

The only solution I found was to 
- first identify the faulty entry in the database with the akonadi console
- then open the database directly with mysql, and delete the entry by hand.
Even the akonadi console was crashing when trying to read the faulty entry, so I could not delete it directly from there.

The entry removed, I could restart kontact without problem.

(akonadi is configured to use the internal mysql server.)

Sorry, I lost the backtrace, and I really don't want to try to reproduce it... I only have my production system and recovery was tricky.
I made a sql dump, so I can provide by the INSERT statement to put the entry in the akonadi database... since it contains some personal data I will only do it on request by mail.
Comment 1 Sergio Martins 2009-02-19 21:03:30 UTC
That was fixed in libical>=0.42, are you using an older release?
Comment 2 Christophe Delaere 2009-02-19 21:57:23 UTC
Indeed... I am using the version provided by Fedora 10: 
Version    : 0.41
Release    : 2.fc10
Comment 3 Sergio Martins 2009-02-20 00:58:04 UTC
Thanks for the info.

Please ask your distro to update libical or to provide a patched 0.41.

If the issue persists reopen but don't forget the backtrace :)