The initial problem is resolved (by itself). Today I tried f-spot in the terminal and f-spot starts normally again.
I guess there has probably been an update of one of the depencies for f-spot lately.