This is an issue with SDL2. As with SDL2 it needs to load the OpenGL
drivers to check if 3d acceleration is enabled. Once it checks it
unloads the library. Then the app starts which needs to load the library
again ad seg fault.
--
You received this bug notification because you are a member of
The trivial one-line workaround proposed in comments #3/#4 might work. I
think I've used it before as a workaround on other Unixes too.
** Changed in: mir
Status: Confirmed => Triaged
** Changed in: mir (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification be
Analysis
The core of the problem is that it's not safe to reuse libprotobuf after
calling google::protobuf::ShutdownProtobufLibrary() without unloading and
reloading the library first. Note that libraries/executables that use protobuf
(e.g. libmirprotobuf) use libprotobuf code also during
Packages (for 2.6.1, vivid) with an _experimental_ patch that allows
protobuf to re-initialize properly after
google::protobuf::ShutdownProtobufLibrary() is called:
https://launchpad.net/~afrantzis/+archive/ubuntu/staging/+packages
--
You received this bug notification because you are a member o
I have started experimenting with an alternative solution which is much
simpler than what I originally proposed. The solution is to ensure
libprotobuf exposes only the symbols it has to (i.e. google protobuf
related), to avoid binding to libstdc++, and thus working around the
problem.
I have pushe
