← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1672955] Re: 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()

 

Hello errors.ubuntu.com, or anyone else affected,

Accepted mir into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.04.20170510-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: mir (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: unity-system-compositor (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: unity-system-compositor (Ubuntu Xenial)
       Status: New => Invalid

** Changed in: mir (Ubuntu Xenial)
       Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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 Committed
Status in Mir 0.26 series:
  Fix Committed
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Committed
Status in unity-system-compositor source package in Xenial:
  Invalid

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