Akonadi is only started when a program is running that needs it.
But there’s absolutely no difference between 4.11, 4.12, and 4.13 in this regard. (the only change in 4.13 is that knotes now uses Akonadi as well)
4.13 uses Baloo now instead of Nepomuk, so no need to turn Nepomuk off.
You can disable Baloo’s file indexing as well, by either:
I don’t think your problem with Google Chrome had anything to do with the KDE 4.13 update (obviously, because otherwise it shouldn’t work now either), but rather with the update of xorg-x11-server overwriting files of the nvidia driver.
So, do/did you use the nvidia driver?
Again, there was an update to xorg-x11-server on Thursday, at the same day the KDE update entered the repo.
So it was not the KDE update that caused your problem with Chrome, but the update of xorg-x11-server.
You have to reinstall the driver every time there is an update to xorg-x11-server or Mesa-libGL1, I already explained why.
The next time such an update is released the driver will break again, regardless of which KDE version you have installed or how you installed it.
That’s why I always recommend (and prefer myself) to use the driver RPMs from the nvidia repo.
the fist time i had akonadi on the computer and stopped in .config
now with the update to kde413 there was no akonadi so no other search tool installed
But this has absolutely nothing to do with Google Chrome. Chrome did not start because your nvidia driver installation was broken, not because you had Akonadi installed.
And btw, Akonadi is no search tool. Akonadi is a PIM management/storage system.
Baloo (or Nepomuk upto 4.12) is what is used for file indexing, mail indexing, and searching.