(In reply to comment #0)
> 	4)	I’m removing testpeer2  - pim-manager.ini contains two lines: 
> 			active = pim-manager-testpeer1
> 			sort = pim-manager-testpeer1

The bug was that "sort" was set instead of "active" in this particular code
path (= removing a peer while some address books are active). I've fixed that
and added a test case.

That SyncEvolution did not start after that bug broke pim-manager.ini points
towards a second problem: how are corrupted files handled? This is essentially
undefined at the moment (= we haven't discussed the desired outcome).

However, in this particular case it is clearly undesirable that PIM Manager no
longer starts, because the clients have no way of detecting and fixing the
problem. It is much better to just ignore the invalid "sort" value and fall
back to the default sorting. I've implemented that (again, with with test).