This bug was fixed in the package mir - 0.7.0+14.10.20140829-0ubuntu1 --------------- mir (0.7.0+14.10.20140829-0ubuntu1) utopic; urgency=medium
[ Daniel van Vugt ] * New upstream release 0.7.0 (https://launchpad.net/mir/+milestone/0.7.0) - Enhancements: . Test suite: Reworked mechanism to override Mir client functions . Demo shell: Detect custom rendering (decorations) to make it compatible with overlay optimizations . Make sure to preserve fd resources until the end of the sending of the message . Add test cases and script for tracking changes to the new ABIs: libmircommon, libmirplatform . Symbols file for libmirplatform . Symbols file for libmircommon . Symbols file for libmirserver . Various improvements to the SessionMediator test . Various build related improvements . Print testcase output during package build . Abort test when InProcessServer startup fails . Link the integration and unit tests against the server objects . Add a document detailing the useful tests to run and the useful logs to collect when troubleshooting a new android chipset . Enable motion event resampling and prediction for a more responsive touch experience. - ABI summary: Servers need rebuilding, but clients do not . Mirclient ABI unchanged at 8 . Mircommon ABI bumped to 1 . Mirplatform ABI bumped to 2 . Mirserver ABI bumped to 25 - API changes . Deleted function - frontend::Shell::create_surface_for(). If you have the std::shared_ptr<frontend::Session> session, you can just do session->create_surface(params) instead to get a SurfaceId - Bug fixes: . Ensure we process lifecycle events before the nested server is torn down (LP: #1353465) . Fix race in InputTestingServerConfiguration (LP: #1354446) . Fix fd leaks in prompt session frontend code and tests (LP: #1353461) . Detect the additional things the demo shell draws on the renderable list and avoid calling the optimized post function if they are being drawn (LP: #1348330) . Client: Fix SIGTERM dispatch in our default lifecycle event handler (LP: #1353867) . DemoRenderer: Don't try to create a texture of width zero. (LP: #1358210) . Fix CI failures (LP: #1358698) . Fix build failure: "variable ‘rc’ set but not used" which happens in release mode when NDEBUG is set (LP: #1358625) . Only enumerate exposed input surfaces to avoid delivering events to occluded surfaces (LP: #1359264) . Android: do not post driver cancelled buffers (LP: #1359406) . Client: Ensure our platform library stays loaded for as long as it is needed by other objects (LP: #1358191) . Examples: Register the DemoCompositor with the Scene to properly process visibility events (LP: #1359487) . Mir_demo_client_basic: Don't assert on user errors like failing to connect to a Mir server (LP: #1331958) . Tests: Explicitly depend on GMock target to avoid build races (LP: #1362646) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release <ps-jenk...@lists.canonical.com> Fri, 29 Aug 2014 16:12:54 +0000 ** Changed in: mir (Ubuntu) Status: Triaged => Fix Released -- 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/1353867 Title: [regression] Mir clients get caught in an infinite exception loop when the server goes away ("Caught exception at Mir/EGL driver boundary") Status in Mir: Fix Committed Status in Mir 0.6 series: Won't Fix Status in Mir 0.7 series: Fix Committed Status in “mir” package in Ubuntu: Fix Released Bug description: Nexus4: Mir client gets caught in an infinite exception loop if the server crashes ("Caught exception at Mir/EGL driver boundary") Test case: 1. mir_demo_server_shell 2. mir_demo_client_egltriangle 3. Press the power button to sleep 4. Press the power button again to wake up Expected: Rendering continues on screen after wakeup Observed: Caught exception at Mir/EGL driver boundary: /home/dan/bzr/mir/dev/src/client/rpc/stream_socket_transport.cpp(280): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_data(const std::vector<unsigned char>&) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN12_GLOBAL__N_112socket_errorEEEEE std::exception::what: Failed to send message to server: Bad file descriptor 9, "Bad file descriptor" Caught exception at Mir/EGL driver boundary: /home/dan/bzr/mir/dev/src/client/rpc/stream_socket_transport.cpp(280): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_data(const std::vector<unsigned char>&) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN12_GLOBAL__N_112socket_errorEEEEE std::exception::what: Failed to send message to server: Bad file descriptor 9, "Bad file descriptor" Caught exception at Mir/EGL driver boundary: /home/dan/bzr/mir/dev/src/client/rpc/stream_socket_transport.cpp(280): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_data(const std::vector<unsigned char>&) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN12_GLOBAL__N_112socket_errorEEEEE std::exception::what: Failed to send message to server: Bad file descriptor 9, "Bad file descriptor" ..... To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1353867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
