** Description changed:
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/.
+ 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.
** Changed in: mir
Status: New => Triaged
** Changed in: mir
Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672955
Title:
unity-system-compositor crashed with SIGSEV in
libinput_device_config_accel_is_available() from
libinput_device_config_accel_set_speed() from
mir::input::evdev::LibInputDevice::apply_settings()
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
