Alan, I think it's likely in the future (if not already) that the Mir server/shell will be a separate snap to any app snaps. And certainly it's difficult to make anything completely foolproof, because fools are so ingenious. But we can build things that are more robust in the face of potential future mistakes. So if those future mistakes include bringing your own libmir* then it would be nice if that worked more often. Even if we don't like the idea, it's better than dealing with high severity bug reports.
-- 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
