Comment 2 for bug 1297878

Revno 1514 in devel fixes this...the cause is hard to understand.

Its true that this onStateChanged was never being fired. This was because sessionCreatedSurface and surfaceCreatedFor were being called for different addresses to the same surface, presumably this had to do with the BasicSurface/SurfaceImpl hierarchy and the inheritance there...but its not clear how it could happen as there is no casting in the code paths and unity-mir always sees msh::Surface pointer...

anyway...revno 1514!