kdepim-runtime4 4.12.5 with kdepimlibs4 4.13.3 .. and baloo

["René J.V. Bertin"]

In the end, to get back into kontact/kmail, I

- reactivated akonadi 1.12.1
- reactivated nepomuk* 4.12.5
- reactivated kdepim* 4.12.5 built against the older versions of the above ports
- deactivated baloo and baloo-widgets

In short, I went back to all the versions of the PIM frameworks from KDE 4.12.5 .
akonadi_nepomuk_feeder kept crashing until I did a `pkill -1 -f -i kde` before restarting the akonadi bundle.
That's something to check when kdepim4 and kdepim4-runtime will have seen their updates to 4.13.3 .
I'll have to dig up backups of the port dirs of the above ports in order to protect them against unwanted/unattended upgrades ...

I seem to recall that Nicolas said something about issues with baloo. I did notice a crash in baloo_file_extractor, with the curious backtrace

baloo_file_extractor(48576,0x7fff70affcc0) malloc: *** error for object 0x7fff70a65500: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
[New Thread 0x2907 of process 48576]

Breakpoint 1, 0x00007fff85fd5499 in ?? () from /usr/lib/libSystem.B.dylib
(gdb) bt
#0  0x00007fff85fd5499 in ?? () from /usr/lib/libSystem.B.dylib
#1  0x00007fff85eff183 in CourierBoldOblique_Entries () from /usr/lib/libSystem.B.dylib
#2  0x00000001197cd5ae in KFileMetaData::Exiv2Extractor::extract(KFileMetaData::ExtractionResult*) ()
   from /Volumes/Debian/MP6/lib/kde4/kfilemetadata_exiv2extractor.so
#3  0x0000000100008459 in Baloo::App::processNextUrl (this=0x7fff5fbfe338)
    at /Volumes/Debian/MP6/var/macports/build/_Volumes_Debian_MP6_site-ports_kde_baloo/baloo/work/baloo-4.13.3/src/file/extractor/app.cpp:165

I won't be debugging that one as I thought because of baloo's deactivation for the time being, but I can take a peek at KFileMetaData.

Cheers,
R.

On Oct 10, 2014, at 00:41, René J.V. Bertin wrote:

> Hello,
> 
> I'm having some trouble port:kdepim-runtime4 (currently still at 4.12.5) against port:kdepimlibs4 and kdepimlibs4-kioslaves (currently at 4.13.3) when port:libkgapi is also installed, and the akonadi_google_calendar is thus built. This *could* be an issue with clang-3.0 (sadly I forgot which compiler I used last time I built kdepim4-runtime, but clang-3.0 clearly breaks on libgkapi-2.2.1).
> 
> Has this combination been tested - in fact, has building of the KDE 4.13.3 suite been tested on 10.6.8 at all?
> 
> Also, do the kdepim4 applications (kmail, kontact etc) v4.12.5 function correctly with kdepimlibs 4.13.3? Any ETA on kdepim4 and kdepim4-runtime v4.13.3?
> 
> R.