Bug 262266 - akonadi_davgroupware_resource crashes on contact updating
Summary: akonadi_davgroupware_resource crashes on contact updating
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: DAV Resource (show other bugs)
Version: 4.6
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Grégory Oestreicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-06 02:42 UTC by Aitor
Modified: 2011-02-22 09:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aitor 2011-01-06 02:42:23 UTC
Version:           4.6 (using KDE 4.5.90) 
OS:                Linux

Every time akonadi tries to update contacts information from my GroupDAV resource, akonadi_davgroupware_resource crashes. It doesn't mater if it's done automatically or through Kontact's "Update Address Book Folder" option. It happens either if I use http or https.
I use eGroupware 1.8.001 as my GroupDAV server.
I store 508 contacts, some of them with images and non English characters.


Reproducible: Always

Steps to Reproduce:
Try to update the Address Book

Actual Results:  
akonadi_davgroupware_resource crashes

Expected Results:  
The Address Book should be updated
Comment 1 Grégory Oestreicher 2011-01-06 09:02:32 UTC
Hi,

Thanks for you report. I'll try to reproduce this bug but need some more informations :
- which Kontact version are you using?
- have you tried using the CardDav protocol in the resource and if so do you have the same crash?
- can you get a backtrace from DrKonqui, preferably using packages with debugging symbols? I'll can get one once I manage to reproduce the crash, but not before some days. Having this at hand could speed up the debugging.

Cheers,
Grégory
Comment 2 Aitor 2011-01-06 18:58:13 UTC
I'm using KDE 4.6rc2.
Kontact: 1.1
KAddressBook: 4.6.beta3 
Akonadi: 1.4.90

The CardDAV protocol seems to work without correctly, I've created a new akonadi resource that uses it and works fine.

The only backtrace info that DrKonqui shows is:

Application: Akonadi Resource (akonadi_davgroupware_resource), signal: Segmentation fault
[KCrash Handler]
#6  0x000000000041bfc9 in _start ()

Thank you!!
Comment 3 Grégory Oestreicher 2011-01-06 23:30:35 UTC
Hi,

I managed to install egw 1.8 and created a test address book with three (hem) contacts, with images and non-ASCII characters, but the crash never happened… with KDE trunk. I'll setup a VM with KDE 4.6rc2 and see what's happening.

Just to be as close as possible of your setup, which distribution are you using, and which repo did you pulled your packages from?

Cheers,
Grégory
Comment 4 Aitor 2011-01-08 19:50:26 UTC
I'm using Arch linux (x86_64) with kde-unstable repositories.

I removed the resource and after created it again no more crashes happened. I'll keep an eye on it.

Cheers,
Aitor
Comment 5 Aitor 2011-01-09 03:35:52 UTC
After rebooting, no data is loaded for any of the egroupware resources (address book, tasks and calendar). On akonadi console nothing is shown under those resources.
Any suggestion?
Comment 6 Grégory Oestreicher 2011-01-11 20:51:17 UTC
Hi,

I've spent a good part of the week-end trying to reproduce these issues to no avail at the moment, though this was not using Arch Linux. This is the moment to discover this distro I guess :)

I'll update this bug once I finally get a definitive view on what's happening.

Cheers,
Grégory
Comment 7 Grégory Oestreicher 2011-01-15 22:00:13 UTC
Hi,

I've finally installed an Arch Linux VM to test this with eGoupware, but the only bugs I can see are coming from the groupdav server, and are timezone-related.

This worked for sure with branch 1.6.x, can you try with one of those?

Cheers,
Grégory
Comment 8 Grégory Oestreicher 2011-02-06 20:39:18 UTC
Hi,

Can you try to apply the changes mentioned in bug #265096 (https://bugs.kde.org/show_bug.cgi?id=265096) and see if that changes anything?

Cheers,
Grégory
Comment 9 Aitor 2011-02-06 22:11:12 UTC
After applying such change it seems to work fine. I'll inform if something goes wrong.
Thank you very much!!
Comment 10 Grégory Oestreicher 2011-02-22 09:13:58 UTC
No news, seems good :) Closing