This bug was fixed in the package mir - 0.23.0+16.10.20160602.1-0ubuntu1 --------------- mir (0.23.0+16.10.20160602.1-0ubuntu1) yakkety; urgency=medium
[ Kevin DuBois ] * New upstream release 0.23.0 (https://launchpad.net/mir/+milestone/0.23.0) - ABI summary: . mirclient ABI unchanged at 9 . mirserver ABI bumped to 40 . mircommon ABI bumped at 6 . mirplatform ABI unchanged at 11 . mirprotobuf ABI unchanged at 3 . mirplatformgraphics ABI unchanged at 9 . mirclientplatform ABI unchanged at 5 . mirinputplatform ABI unchanged at 5 - Enhancements: . Enable internal usage of more flexible graphics buffer submission, precursing client API additions. - Bug fixes: . Potential NBS performance loss after resize (LP: #1579076) . Performance loss with NBS and overlays on (LP: #1578159) . Mir crashes with useless backtrace when mg::Platform methods throw (LP: #1553549) . Virtual output is not removed when screencast client disappears (LP: #1573572) . Can't VT switch from mir_demo_server (any more) (LP: #1576260) . mir_demo_server(_minimal): Window movement/resizing stops responding when the cursor leaves the surface, and can lead to windows 1px wide and unrecoverable. (LP: #1447886) . Virtual display output configuration is set to LVDS (LP: #1573782) . Mir-on-X11 doesn't pass Alt+primary button drag to Mir (LP: #1575765) . Mir-on-X11 breaks mir_proving_server resize logic (LP: #1575192) . Resizing can crash mir_demo_server (LP: #1575211) . [regression] Cursor stops at phantom edge on M10 and N7 (LP: #1580774) . [regression] MIR_CLIENT_PERF_REPORT is showing bogus render times and buffer lag (LP: #1581368) . Test failures in ClientLogging.reports_performance due to the above fix. (LP: #1583970, LP: #1584603, LP: #1584605) . Do not throw when creating some objects under HWC 1.5 (LP: #1583086) . Correct black frame issue under Xmir (LP: #1584784) [ Tarmac, Kevin DuBois <[email protected]>, Daniel van Vugt <[email protected]>, Andreas Pokorny <[email protected]>, Alberto Aguirre ] * 0.23.0 Mir release -- Kevin DuBois <[email protected]> Thu, 02 Jun 2016 13:18:03 +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/1553549 Title: Mir crashes with useless backtrace when mg::Platform methods throw Status in Mir: Fix Released Status in Unity System Compositor: Invalid Status in mir package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Invalid Bug description: So, the problem that causes unity-system-compositor to crash (rather than fail to start with a helpful error message) is that when methods on mg::Platform throw we unload the platform DSO before exception processing is completed, so libstdc++ goes merrily along trying to execute code that is longer mapped. Original report below: unity-system-co[5574]: segfault at 7f8056ee2490 ip 00007f805c592c3b sp 00007fffd6b871a0 error 4 in libstdc++.so.6.0.21[7f805c506000+172000] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-system-compositor 0.4.2+16.04.20160219.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sat Mar 5 19:03:39 2016 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1455894356 GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor Integrated Graphics Controller [1462:1102] Subsystem: Micro-Star International Co., Ltd. [MSI] GM204M [GeForce GTX 970M] [1462:1102] InstallationDate: Installed on 2015-02-25 (374 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/lightdm-mir-0 --from-dm-fd 11 --to-dm-fd 20 --vt 8 ProcCwd: / ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f805c592c3b: mov (%rsi),%rax PC (0x7f805c592c3b) ok source "(%rsi)" (0x7f8056ee2490) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity-system-compositor StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __gxx_personality_v0 () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 _Unwind_RaiseException () from /lib/x86_64-linux-gnu/libgcc_s.so.1 _Unwind_Resume_or_Rethrow () from /lib/x86_64-linux-gnu/libgcc_s.so.1 __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0() UpgradeStatus: Upgraded to xenial on 2015-11-03 (122 days ago) UserGroups: version.libdrm: libdrm2 2.4.67-1 version.lightdm: lightdm 1.17.5-0ubuntu2 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1553549/+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
