[Kde-pim] How to pinpoint issues with KMail + Akonadi in order to make bug reports more actionable

[Martin Steigerwald]

Am Donnerstag, 12. März 2015, 17:37:54 schrieb Sandro Knauß:
> Hey,

Hey Sandro,

> > Heck, I am willing to put answers into the wiki in some structured
> > way. So please give some hints. Up so far I didn´t found any
> > comprehense page on this. Just hints here and there and trying to
> > fiddle around myself with Akonadiconsole myself without understanding
> > half of what I have been doing?
> 
> +1
> 
> I started already writing it down how to get usefull informations from
> kdepim+akonadi[1]. Maybe you can take this as stating point.

Thank you for your detailed description.

I didn´t yet manage to have a closer look at the wiki page.

But, as an early finding,

> Mostly for a noresponing akonadi<->kmail the interessting tabs in
> akonadiconsole are debugger and job tracker. Both must be activate
> before akonadi get in the "nonresponing" state.

now also compiled kdepimlibs, kdepim-runtime and kmail to most recent 4.14 
branch and well, I didn´t see a loosing connection thing since then.

So *maybe* something is fixed in there. I will observe this for a bit 
longer and if it is really gone, close the bug report as works for me.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/