unity-settings-daemon crashed with SIGSEGV in _gdk_device_xi2_reset_scroll_valuators()

[Haw Loeung]

See attached

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity-settings-daemon 14.04.0+14.10.20141010-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
ApportVersion: 2.14.7-0ubuntu6
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 14 10:34:04 2014
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
ExecutableTimestamp: 1412929386
InstallationDate: Installed on 2014-04-24 (172 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
ProcCwd: /home/hloeung
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_AU:en
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: unity-settings-daemon
StacktraceTop:
 _gdk_device_xi2_reset_scroll_valuators (device=0x1c47310) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdevice-xi2.c:875
 handle_device_changed (ev=<optimized out>, device_manager=<optimized out>) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdevicemanager-xi2.c:775
 gdk_x11_device_manager_xi2_translate_event (translator=0x1c47310, display=0x1c1a6c0, event=0x1c5cd20, xevent=0x7fffbcce9260) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdevicemanager-xi2.c:1168
 _gdk_x11_event_translator_translate (translator=0x1c1c2d0, display=0x1c36090, xevent=xevent@entry=0x7fffbcce9260) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkeventtranslator.c:51
 gdk_event_source_translate_event (xevent=0x7fffbcce9260, event_source=0x1c37480) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkeventsource.c:240
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1380278, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.