Hi, from https://bugs.kde.org/show_bug.cgi?id=365944 >--- Comment #2 from Laurent Montel <mon...@kde.org> --- > Git commit 88c31eb55116297e8faf248c81122e3d0af6e97b by Montel Laurent. > Committed on 22/07/2016 at 05:50. > Pushed by mlaurent into branch 'Applications/16.08'. > > Fix Bug 365944 - KAddressbook crashes on startup with configured CardDav > > Apply patch from comment in this BR. > I can't reproduce bug but value() will not assert as at(...) > FIXED-IN: 5.3.0 > > M +1 -1 src/core/models/tagmodel_p.cpp > > http://commits.kde.org/akonadi/88c31eb55116297e8faf248c81122e3d0af6e97b So I look forward to 16.08.
Meanwhile I removed the birthday agent within akonadiconsole, stopped akonadi removed all akonadi cache files in .local/share/ and restarted again. I had to adjust all my folder settings for my accounts and filters but now I'm able to access my owncloud address book. BTW: I'm looking for more information starting with such tests. Is there any faq/file/help on the structure of (for instance) akonadi / baloo files, so one can do some behavioral tests on the systems? And furthermore exists some kind of central information on somewhat like a "project schedule" for kde / kdepim? It would be a charm to know, wether experiments are worthwhile (or wether the next update is coming soon :-). I found the page https://pkg-kde.alioth.debian.org, but latest news are from August 2013? Thanks a lot for your work. Greetings Volker Am Donnerstag, 21. Juli 2016, 13:59:42 CEST schrieb Maximiliano Curia: > ¡Hola Volker! > > El 2016-07-21 a las 11:03 +0200, Volker Groll escribió: > > Holla Maximiliano, > > > >> It seems to me that the bug is the same as: > >> https://bugs.kde.org/show_bug.cgi?id=358696 > > > > Hm, not sure, but there is mentioned the crash occurs, when the > > birthday calendar is enabled, mine is disabled. > > Well, it seems to be the same underlying issue. > > >> Could you please provide additional information in the bug upstream? > >> Currently it seems to require confirmation that this bug is only > >> reproduceable in 32 bits systems. > > > > I have local address books and two on an owncloud server. > > Changing the owncloud resource to offline with akonadiconsole > > changes nothing (crash persists). I get also a crash from akonadiconsole > > when I try to switch to Browser tab. > > > >> Also, a full backtrace would be useful, for that you would need to > >> install > >> the kaddressbook-dbgsym package (and probably the dbg/dbgsym packages > >> from > >> a couple of kaddressbook dependencies) from the debug archive (that needs > >> to be added in the sources.list as: deb > >> http://deb.debian.org/debian-debug > >> unstable-debug main) > > > > Most threads are in g_mutex_unlock (), __kernel_vsyscall () > > Installing libglib2.0-0-dbg will give only 0xffffffff in output, > > so I purged this debug package again. > > If possible please keep the full backtrace. > > > The output of the last thread is: > > Thread 1 (Thread 0xed0a6ac0 (LWP 5109)): > > [KCrash Handler] > > Shouldn't there be information of 6 more frames? > > > #7 0xf4ff1cb6 in Akonadi::Tag::isValid (this=0xff8b137c) at > > /build/akonadi- uzW5jU/akonadi-16.04.3/src/core/tag.cpp:239 > > #8 0xf5097577 in Akonadi::TagModel::data (this=0x9b1c098, index=..., > > role=258) at /build/akonadi-uzW5jU/akonadi-16.04.3/src/core/models/ > > tagmodel.cpp:95 > > Looking at the code, my bet is that changing akonadi's > src/core/models/tagmodel_p.cpp the function Tag > TagModelPrivate::tagForIndex line 106: > return children.at(index.row()); > for: > return children.value(index.row()); > > would make the issue to go away (by creating a new instance whenever an > invalid index is accessed), but the real issue is to be hitting this > function with invalid index values (the previous fix only takes care of > negative values, btw). That would need someone that actually understands the > code. > > Please, if possible, add the information to the upstream bug with the full > backtrace. > > Happy hacking,
