I experienced the same error you received. I suppose it is because of some incompatibility between SEBLOD (3.1.5) and new Joomla 3.2
That said, the authors of SEBLOD did promised a version compatible with 3.2 (SEBLOD 3.2 will be available for Joomla! 3.2 by the end of this week.), so I expect the problems to be solved.
Since there is a new MVC structure in Joomla, and also the Akeeba FoF, I expect the works on a new version are a bit tricky, but hopefully that will bring some improvements to performance and maybe even new features.