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

[Chris Johnston]

Crashed while using the system.

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 17:10:16 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2014-06-29 (107 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f48a7e313c0: andb $0xfe,0x1(%rax)
 PC (0x7f48a7e313c0) ok
 source "$0xfe" ok
 destination "0x1(%rax)" (0x7f48a8a790d1) in non-writable VMA region: 0x7f48a898c000-0x7f48a8a98000 r-xp /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.0
SegvReason: writing VMA /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.0
Signal: 11
SourcePackage: unity-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: unity-settings-daemon crashed with SIGSEGV in gdk_display_get_event()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

[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.