The "matching" you mention may not happen in the snappy case. So there is a problem.
In the pure snappy case, an app brings its own libmirclient and potentially its own libmirprotobuf and libmir*. So it is not a binary "match" for the server in question. And the app may be using Mir binaries that are newer (most likely) or older (e.g. this bug) than that of the server. The only commonality is the protocol and negotiation needs to happen there. It's not related to libraries and ABIs at all. Unless..... We could mitigate the problem by: (a) Never bumping the client ABI again; and (b) Ensuring app snaps don't bring their own libmir*, so do use the system copy. However that only works for as long as we can ensure both (a) and (b) are true. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title: [regression] OTA7 broke previously working app Status in Canonical System Image: Confirmed Status in Mir: Won't Fix Status in Mir 0.16 series: Won't Fix Status in Mir 0.17 series: Won't Fix Status in mir package in Ubuntu: Won't Fix Bug description: OTA7 broke previously working app after OTA7 update on Meizu MX4, glmark2 stopped working https://uappexplorer.com/app/glmark2.sturmflut system updates should not break apps ~/.cache/upstart$ cat application-click-glmark2.sturmflut_glmark2_0.4.1.log libust[24877/24879]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:958) libust[24877/24879]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:958) libust[24877/24878]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958) libust[24877/24878]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958) Error: Couldn't connect to the Mir display server Error: main: Could not initialize canvas [1445336019.182277] <ERROR> MirConnectionAPI: Caught exception at client library boundary (in release): /build/buildd/mir-0.13.3+15.04.20150617/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorEEEEE std::exception::what: Failed to send message to server: Broken pipe 32, "Broken pipe" libust[24922/24923]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958) libust[24922/24923]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958) libust[24922/24924]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:958) libust[24922/24924]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:958) Error: Couldn't connect to the Mir display server Error: main: Could not initialize canvas [1445336029.784398] <ERROR> MirConnectionAPI: Caught exception at client library boundary (in release): /build/buildd/mir-0.13.3+15.04.20150617/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorEEEEE std::exception::what: Failed to send message to server: Broken pipe 32, "Broken pipe" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
