Mir

Activity log for bug #1661508

Date Who What changed Old value New value Message
2017-02-03 07:03:53 Daniel van Vugt bug added bug
2017-02-03 07:04:05 Daniel van Vugt mir: importance Undecided Critical
2017-02-03 07:04:08 Daniel van Vugt mir: milestone 1.0.0
2017-02-03 07:06:23 Daniel van Vugt summary Fullscreen clients of nested servers crash on start-up [<ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer) ... std::exception::what: broken_promise] Nested server segfaults when a fullscreen client starts
2017-02-03 07:06:28 Daniel van Vugt tags nested
2017-02-03 07:07:12 Daniel van Vugt description Fullscreen clients of nested servers crash on start-up. Using Mir 0.26.0 (zesty release): [2017-02-03 15:01:28.185340] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase<T>::break_promise() [with T = std::shared_ptr<mir::client::MirBuffer>] Dynamic exception type: boost::exception_detail::error_info_injector<std::runtime_error> std::exception::what: broken_promise Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase<T>::break_promise() [with T = std::shared_ptr<mir::client::MirBuffer>] Dynamic exception type: boost::exception_detail::error_info_injector<std::runtime_error> std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped)
2017-02-03 07:08:12 Daniel van Vugt description Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase<T>::break_promise() [with T = std::shared_ptr<mir::client::MirBuffer>] Dynamic exception type: boost::exception_detail::error_info_injector<std::runtime_error> std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase<T>::break_promise() [with T = std::shared_ptr<mir::client::MirBuffer>] Dynamic exception type: boost::exception_detail::error_info_injector<std::runtime_error> std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) WORKAROUND: Start your nested server with --nested-passthrough=OFF
2017-02-03 07:09:43 Daniel van Vugt description Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase<T>::break_promise() [with T = std::shared_ptr<mir::client::MirBuffer>] Dynamic exception type: boost::exception_detail::error_info_injector<std::runtime_error> std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) WORKAROUND: Start your nested server with --nested-passthrough=OFF Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase<T>::break_promise() [with T = std::shared_ptr<mir::client::MirBuffer>] Dynamic exception type: boost::exception_detail::error_info_injector<std::runtime_error> std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x00007fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x00007fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x00007fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x00007fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x00007fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x00007fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x00007fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x00007fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x00007fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 WORKAROUND: Start your nested server with --nested-passthrough=OFF
2017-02-03 07:32:25 Daniel van Vugt summary Nested server segfaults when a fullscreen client starts Nested server segfaults or rapidly logs exceptions in mir_presentation_chain_set_dropping_mode() when a fullscreen client starts
2017-02-03 07:44:39 Daniel van Vugt nominated for series mir/0.26
2017-02-03 07:44:39 Daniel van Vugt bug task added mir/0.26
2017-02-03 07:44:44 Daniel van Vugt mir/0.26: milestone 0.26.1
2017-02-03 07:44:53 Daniel van Vugt mir/0.26: importance Undecided Critical
2017-02-03 07:52:52 Daniel van Vugt summary Nested server segfaults or rapidly logs exceptions in mir_presentation_chain_set_dropping_mode() when a fullscreen client starts Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted]
2017-02-03 08:29:32 Daniel van Vugt bug task added mir (Ubuntu)
2017-02-03 08:29:38 Daniel van Vugt mir (Ubuntu): importance Undecided Critical
2017-02-03 08:39:36 Daniel van Vugt summary Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted]
2017-02-03 08:39:42 Daniel van Vugt tags nested nested regression
2017-02-03 08:54:55 Daniel van Vugt mir: status New Triaged
2017-02-03 08:55:00 Daniel van Vugt mir/0.26: status New Triaged
2017-02-03 08:55:04 Daniel van Vugt mir (Ubuntu): status New Triaged
2017-02-03 08:56:25 Daniel van Vugt description Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase<T>::break_promise() [with T = std::shared_ptr<mir::client::MirBuffer>] Dynamic exception type: boost::exception_detail::error_info_injector<std::runtime_error> std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x00007fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x00007fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x00007fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x00007fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x00007fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x00007fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x00007fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x00007fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x00007fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 WORKAROUND: Start your nested server with --nested-passthrough=OFF Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase<T>::break_promise() [with T = std::shared_ptr<mir::client::MirBuffer>] Dynamic exception type: boost::exception_detail::error_info_injector<std::runtime_error> std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x00007fcceb7b4003 in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x00007fcceb7d1961 in mir_presentation_chain_set_dropping_mode ()    from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x00007fccec0e3a7a in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x00007fccec09fd2d in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x00007fccec09f018 in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x00007fccec0e2c79 in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x00007fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x00007fcce95326ca in start_thread (arg=0x7fccde2b4700)     at pthread_create.c:333 #9 0x00007fccec4710ff in clone ()     at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] <ERROR> mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] <ERROR> mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] <ERROR> mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] <ERROR> mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted WORKAROUND: Start your nested server with --nested-passthrough=OFF
2017-02-03 09:03:28 Daniel van Vugt description Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase<T>::break_promise() [with T = std::shared_ptr<mir::client::MirBuffer>] Dynamic exception type: boost::exception_detail::error_info_injector<std::runtime_error> std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x00007fcceb7b4003 in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x00007fcceb7d1961 in mir_presentation_chain_set_dropping_mode ()    from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x00007fccec0e3a7a in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x00007fccec09fd2d in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x00007fccec09f018 in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x00007fccec0e2c79 in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x00007fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x00007fcce95326ca in start_thread (arg=0x7fccde2b4700)     at pthread_create.c:333 #9 0x00007fccec4710ff in clone ()     at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] <ERROR> mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] <ERROR> mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] <ERROR> mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] <ERROR> mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted WORKAROUND: Start your nested server with --nested-passthrough=OFF Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] <ERROR> Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase<T>::break_promise() [with T = std::shared_ptr<mir::client::MirBuffer>] Dynamic exception type: boost::exception_detail::error_info_injector<std::runtime_error> std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x00007fcceb7b4003 in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x00007fcceb7d1961 in mir_presentation_chain_set_dropping_mode ()    from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x00007fccec0e3a7a in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x00007fccec09fd2d in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x00007fccec09f018 in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x00007fccec0e2c79 in ?? ()    from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x00007fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x00007fcce95326ca in start_thread (arg=0x7fccde2b4700)     at pthread_create.c:333 #9 0x00007fccec4710ff in clone ()     at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] <ERROR> mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] <ERROR> mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] <ERROR> mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] <ERROR> mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521.
2017-02-03 15:10:39 Kevin DuBois mir/0.26: assignee Kevin DuBois (kdub)
2017-02-03 15:10:46 Kevin DuBois mir/0.26: status Triaged In Progress
2017-02-03 15:11:37 Kevin DuBois branch linked lp:~kdub/mir/fix-1661508
2017-02-03 17:02:53 Launchpad Janitor branch linked lp:mir/0.26
2017-02-03 17:46:57 Mir CI Bot mir: status Triaged Fix Committed
2017-02-03 20:17:41 Launchpad Janitor branch linked lp:~ci-train-bot/mir/mir-ubuntu-zesty-2435
2017-02-04 02:46:19 Daniel van Vugt mir: assignee Kevin DuBois (kdub)
2017-02-04 02:58:39 Daniel van Vugt mir/0.26: status In Progress Fix Committed
2017-02-16 17:08:05 Launchpad Janitor mir (Ubuntu): status Triaged Fix Released
2017-02-17 02:16:39 Daniel van Vugt mir/0.26: status Fix Committed Fix Released
2017-04-04 02:28:44 Launchpad Janitor branch linked lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683
2017-06-05 11:01:50 Launchpad Janitor branch linked lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736
2017-06-05 11:02:25 Launchpad Janitor branch linked lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1
2017-06-05 13:46:31 Launchpad Janitor branch linked lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783
2017-06-08 09:43:53 Launchpad Janitor branch linked lp:~ci-train-bot/mir/mir-ubuntu-artful-2806
2017-06-15 13:55:23 Launchpad Janitor branch linked lp:~ci-train-bot/mir/mir-ubuntu-zesty-2818
2017-07-11 04:10:30 Daniel van Vugt mir: status Fix Committed Fix Released