This bug was fixed in the package mir - 0.26.3+17.04.20170605-0ubuntu1 --------------- mir (0.26.3+17.04.20170605-0ubuntu1) zesty; urgency=medium
[ Daniel van Vugt ] * New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3) - Enhancements: . Make deprecations optional (and default to off for builds on 16.04 LTS) . Added support for building on Ubuntu 17.10 artful. - Bugs fixed: . Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186) . unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955) . Please transition to Boost 1.62 (LP: #1675138) . Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while) (LP: #1675357) . mir_demo_standalone_render_overlays fails to link (LP: #1677239) -- Michał Sawicz <michal.saw...@canonical.com> Mon, 05 Jun 2017 11:04:47 +0000 -- 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/1672955 Title: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() Status in Canonical System Image: Fix Committed Status in Mir: Fix Released Status in Mir 0.26 series: 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 Status in mir source package in Xenial: Fix Released Status in unity-system-compositor source package in Xenial: Invalid Status in mir source package in Yakkety: Fix Released Status in mir source package in Zesty: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with package version 0.9.1+17.04.20170216-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. It seems that the configuration change is requested just a moment before the device gets removed. The change actions are serialized, depending on where there memory of mir::input::DefaultDevice is allocated the segfault either occurs inside the lambda or inside underlying mir::input::LibInputDevice in the platform. The activities on input dispatch device removal and reconfiguration are serialized inside the input thread, so we just need to clean the action queue (or have multiple queues) before removing the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+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
