I'm very suspicious of my laptop running yakkety - even with "proposed" purged it is now crashing every few minutes (which makes keeping track of things a PITA).
The root cause is probably a failure in protobuf to re-initalise static data when clients call google::protobuf::ShutdownProtobufLibrary(). This leads to a failure when if the whole .so isn't unloaded before the next "GOOGLE_PROTOBUF_VERIFY_VERSION;"
Which is why the change I picked up looks relevant.
The "hack" mentioned above did appear to workaround the problem for Mir (i.e. the test passes). (But it will probably recur with other Qt plugins that use protobuf.)
I'm very suspicious of my laptop running yakkety - even with "proposed" purged it is now crashing every few minutes (which makes keeping track of things a PITA).
The root cause is probably a failure in protobuf to re-initalise static data when clients call google: :protobuf: :ShutdownProtob ufLibrary( ). This leads to a failure when if the whole .so isn't unloaded before the next "GOOGLE_ PROTOBUF_ VERIFY_ VERSION; "
Which is why the change I picked up looks relevant.
The "hack" mentioned above did appear to workaround the problem for Mir (i.e. the test passes). (But it will probably recur with other Qt plugins that use protobuf.)
So I'm going to reinstall and start over.